What Payjoin is
In a normal Bitcoin payment, the sender spends their own coins, the receiver gets one output, and any change goes back to the sender. Anyone looking at the blockchain usually assumes that every coin going into a transaction belongs to the same person. Most of the time that guess is right, and it is the starting point for most chain analysis.
In a Payjoin, the receiver adds one of their own coins to the sender's payment. The transaction then has inputs from two people, and the guess is wrong. It still looks like an ordinary payment from one wallet, so an observer who assumes it is one will link coins that do not belong together and read the wrong amount.
Both sides gain something. The sender's coins are no longer cleanly tied to each other. The receiver tidies up a coin at the same time, and the whole network benefits a little, because the guess becomes less reliable for everyone once enough people use Payjoin.
BIP 78 ↗ · payjoin.org: privacy ↗
What it does not hide
Payjoin makes a payment harder to read. It does not make it unreadable. payjoin.org's own analysis from March 2026 lists the tells an analyst looks for:
- An input that was not needed. If one input alone could have paid, the second probably belongs to the receiver.
- Wallet fingerprints. Two different wallets sign and set fees in slightly different ways, which can show whose input is whose.
- Round amounts. A payment of exactly 40,000 sat still stands out.
If an analyst can split the inputs by owner, a Payjoin reads like two ordinary transactions. It also only happens when both wallets support it, and when the receiver already holds a coin of the same address type to add. Otherwise the payment goes through as a normal one.
The two people involved learn a little about each other too. As with any payment, the receiver sees the sender's coins. In a Payjoin, the sender also sees one of the receiver's.
Two versions
Version 1 (BIP 78) needs the receiver to run a web server that is online at the moment of payment, with a hot wallet behind it. In practice that means shops using BTCPay Server. An ordinary person on a phone cannot receive this way.
Version 2 (BIP 77, also called Async Payjoin) removes that. The two wallets leave encrypted messages for each other in a mailbox on a shared server, called a directory, and pass them through relays so the directory does not see anyone's internet address. Neither side has to be online at the same time. This is what lets phone wallets receive Payjoins. payjoin.org now recommends version 2, and the specification is still a draft.
- What the directory sees. With both sides on version 2, it cannot read or change the messages and, through a relay, does not see internet addresses. It can see that a mailbox is used, and when.
- What a relay sees. Your internet address, but not what you send.
- The exception. When a version 1 wallet pays a version 2 receiver, the messages are not encrypted and the directory can read them. In 2025 a misconfigured database on the payjo.in directory may have exposed messages of exactly that kind. Version 2 messages were not affected.
BIP 77 ↗ · payjoin.org: Async Payjoin ↗ · payjo.in incident ↗
Which wallets can do it
Checked 16 November 2026 against each project's own release notes, documentation or code.
| Software | Send | Receive | Notes |
|---|---|---|---|
| Cake Wallet | Yes (v2, falls back to v1) | Yes (v2) | Phone apps only. Off by default: turn it on under Settings > Privacy. Receiving needs some bitcoin already in the wallet. |
| Bull Bitcoin | Yes (v2) | Yes (v2) | On by default for buying, selling and bill payments with the Bull Bitcoin exchange, off by default between people. Will not pay version 1 only receivers. |
| BTCPay Server | Yes (v1) | Yes (v1) | For shops. The store needs a hot wallet and a coin to add. |
| Sparrow | Yes (v1) | No | Pays version 1 receivers such as BTCPay shops. Hardened in 2.5.4 and 2.5.6. |
| BlueWallet | Yes (v1) | No | Pays version 1 receivers. |
| Wasabi | No | No | Sending was removed in 2.8.5 (October 2026) "to reduce code complexity and attack surface". |
| JoinMarket | Do not use | Yes (v1) | The project is archived and warns: "DO NOT USE THIS SOFTWARE TO SEND PAYJOIN PAYMENTS." A flaw lets a malicious receiver take the coins you spend, and it will not be fixed. |
| Electrum, Liana, Bitcoin Core | Not yet | Not yet | Work is in progress, not released. |
Exchanges: Bull Bitcoin says it is the first exchange to offer Payjoin for deposits and withdrawals. I found no other exchange that documents it.
Not every pair works together. Version 1 senders (Sparrow, BlueWallet) pay version 1 receivers (BTCPay shops). Cake Wallet and Bull Bitcoin can pay each other over version 2, and payjoin.org has analysed a real Payjoin between the two.
Using it safely
- If it fails, the payment still happens. The sender signs an ordinary transaction first and hands it over. If the Payjoin is not completed, either side can broadcast that ordinary one instead. Do not pay twice because a Payjoin did not go through: check the blockchain first.
- Fees are a little higher. The extra input makes the transaction bigger.
- Keep your wallet updated. Several wallets shipped Payjoin fixes between September and November 2026, including Sparrow, BTCPay Server and Bull Bitcoin.
- Do not send Payjoins from JoinMarket. See the table.
- Avoid round amounts when privacy is the point. They make the payment easy to spot.
- For shops: someone can start Payjoins and abandon them to learn which coins a shop holds. BTCPay Server and payjoin.org describe how to limit this; payjoin.org reports no known cases.
Try it
The simplest way to see one is between two phone wallets you control:
- In Cake Wallet, turn on Use Payjoin under Settings > Privacy, and make sure the wallet already holds a little bitcoin.
- On the Receive screen, the QR code now shows Payjoin enabled.
- Pay that code from a second wallet that sends version 2 Payjoins, such as Bull Bitcoin or another Cake Wallet.
- Look the transaction up on a block explorer. You will see inputs from both wallets.
Payjoin pairs well with silent payments on the receiving side and coin control on the sending side. Bitcoin privacy puts all three in context.
Sources & further reading
Researched 16 November 2026. Software and services change: check the current documents before you act.
- BIP 78: a simple Payjoin proposal ↗
- BIP 77: Async Payjoin ↗
- payjoin.org: why Payjoin, privacy ↗
- payjoin.org: Async Payjoin (BIP 77) ↗
- payjoin.org: how wallet fingerprints damage Payjoin privacy ↗
- payjoin.org: payjo.in directory security incident ↗
- BTCPay Server docs: Payjoin ↗
- Cake Wallet docs: Payjoin ↗
- Bull Bitcoin Mobile 6.15.0 release notes ↗
- Sparrow 2.5.6 release notes ↗
- BlueWallet 5.6.1 release notes ↗
- Wasabi 2.8.5 release notes ↗
- JoinMarket: repository notice ↗
- Bitcoin Optech: Payjoin ↗
Your balance is a collection of stories → · Silent Payments → · Cake Wallet → · Make privacy a routine → · Sparrow: build a wallet you can inspect →
