A till that can’t spend
How does a shop take bitcoin without leaving spending keys on its web server? Payment software BTCPay Server answers in its wallet FAQ that by default it “only requires an extended public key,” the xpub, created in a wallet the merchant already uses. It generates a new address for every invoice from that key, so in this setup the keys that could move the money stay off the server.
Desktop wallet Sparrow handles a hardware wallet the same way. Its Coldcard guide says importing the device means importing “the public key details” so the app can display the balance and addresses, and that the Coldcard “will never export your private key.”
Where the setting lives
Each project documents its own route, and we read all four on November 19, 2026.
| Software | How a watch-only wallet is made |
|---|---|
| BTCPay Server | The merchant provides an xpub generated in an existing wallet |
| Bitcoin Core | The createwallet command with disable_private_keys turned on |
| Electrum | File, New/Restore, then “Use public or private keys” with a master public key pasted in |
| Sparrow | A new wallet imports the public key file a hardware wallet exports |
Bitcoin Core’s createwallet reference says that option leaves “only watchonlys” possible. Electrum’s cold storage page ends the setup with a popup about opening “a watching-only wallet,” which then shows the offline wallet’s history.
What changed in Bitcoin Core
Two recent releases changed how this works in the node software. Version 30.0, published on October 10, 2025, removed legacy wallets along with legacy-only commands such as importaddress and importpubkey, and dropped the iswatchonly field from every reply that carried it.
Version 32.1, published on October 27, 2026, added exportwatchonlywallet. It writes a file holding the wallet’s public descriptors, transactions and address book “but no private keys.” The project’s offline signing tutorial now uses it for the online half of the setup described under cold storage.
Payments that seem to be missing
The first surprise for merchants is a balance that looks too low. BTCPay’s FAQ explains that wallets limit how many unused addresses they track, “typically 20.” After 20 unpaid invoices in a row, an outside wallet loaded with the same xpub stops fetching, so payments to the 21st and later invoices don’t show there. The fix is a wallet that lets you raise this gap limit, such as Electrum, Sparrow or Bitcoin Core, or BTCPay’s own wallet.
The second is treating the xpub as harmless. Sparrow says someone with your public key “can see your wallet transactions, but can’t steal your funds,” and its best-practices page warns that a public server you connect to sees your balance too.
BIP 32 adds a sharper caveat. An xpub plus any non-hardened private key derived from it “is equivalent to knowing the parent extended private key,” which is why the specification says extended public keys “must be treated more carefully than regular public keys.”