Payjoin

Definition: Payjoin is a collaborative Bitcoin payment protocol in which the receiver contributes one or more inputs to a transaction that the sender began. The result is still an ordinary Bitcoin transaction, but its inputs do not all come from the payer; this can weaken a common heuristic used to guess that inputs in one transaction share an owner. Payjoin uses Bitcoin transaction data and PSBTs rather than creating a separate coin or network.1 3

Key dates BIP 78 was assigned May 1, 2019 and is marked Deployed. BIP 77 was assigned August 8, 2023 and is marked Draft in the BIP repository.1 2
Protocol specifications BIP 78 BIP 77
Directories Bitcoin Directory

What Payjoin changes

In a typical payment, the sender’s wallet selects inputs it controls and creates an output for the recipient. With Payjoin, the receiver can add an input they control, and the parties negotiate the final transaction before it is broadcast. The sender’s payment is combined with the receiver’s contribution in one transaction. This makes the simple assumption that every input belongs to one person less dependable, though it does not hide the transaction from Bitcoin’s public ledger.1

The participants exchange a Partially Signed Bitcoin Transaction (PSBT). A PSBT carries transaction details and signature data while a transaction is being assembled; it is not itself a completed payment or a custody service. The receiver may add inputs and adjust permitted transaction details, after which the sender’s wallet checks the proposal and signs it. If negotiation fails, compatible implementations can fall back to the original payment transaction.1 2 3

How the exchange works

  1. The receiver creates a Bitcoin payment request that advertises Payjoin support.
  2. The sender’s compatible wallet builds a fallback transaction and shares an original PSBT through the protocol’s coordination channel.
  3. The receiver checks the proposal, adds its own input or other permitted data, and returns a proposal PSBT.
  4. The sender’s wallet verifies that the proposal still pays the intended amount and follows its safety rules. The sender signs and broadcasts the resulting transaction, or uses the fallback if the negotiation is rejected or times out.1 2

BIP 78 and BIP 77

BIP 78, Payjoin v1, coordinates the exchange through an HTTP endpoint supplied by the receiver. The receiver’s service must be reachable while the negotiation takes place, so deployment can require server setup and both parties to be online at the same time. BIP 78 is marked Deployed in the BIP repository; that status does not mean every wallet supports it.1

BIP 77, Payjoin v2, proposes asynchronous coordination through a Payjoin Directory that stores and forwards encrypted messages, so the receiver does not need to host the same public endpoint. The specification uses Oblivious HTTP (OHTTP) to reduce the directory’s ability to associate requests with client network information. The BIP repository still labels BIP 77 Draft, while Payjoin’s own documentation recommends v2 as its current approach; these describe the BIP’s formal status and the project’s implementation guidance, respectively.2 4

Privacy, fees, and limitations

Payjoin is a privacy technique, not an anonymity guarantee. Amounts and transaction timing remain public, and address reuse, later spending patterns, exchange records, or other off-chain information can still connect activity. A Payjoin transaction can make one common-input ownership heuristic less reliable, but analysts may use other clues. OHTTP and encrypted messages protect parts of the coordination flow; they do not conceal the final Bitcoin transaction.1 2

The transaction’s size and fee depend on its inputs, outputs, fee rate, and wallet policy. Combining a payment with a receiver contribution can be more efficient than making separate transactions in some circumstances, but Payjoin does not guarantee a lower fee for every payment. Payjoin also depends on compatible wallet software, reliable message delivery, and careful verification of the proposed transaction. BIP 78 identifies risks such as probing a sender’s available UTXOs; users should follow their wallet’s checks and avoid approving a proposal they do not understand.1

In August 2026, the Payjoin project announced version 1.0.0 of its core Rust library for BIP 77 and BIP 78. The announcement described pilot integrations and explicitly noted that some accompanying tools, including the command-line reference client and server, were not yet stable. A library release is evidence of development progress, not proof that Payjoin is available in every wallet or payment service.5

History

  • 2019: BIP 78 was assigned on May 1, setting out the first deployed Payjoin protocol proposal.1
  • 2023: BIP 77 was assigned on August 8 and proposed an asynchronous, backward-compatible version using a directory and encrypted messages.2
  • 2026: Payjoin announced release 1.0.0 of the core Payjoin Dev Kit Rust library; the BIP 77 specification remained marked Draft in the BIP repository at the time reviewed here.2 5

Last updated: 2026-11-10.

Related Terms

Related Articles

CryptoGloss does not yet have an article focused on Payjoin. These four articles provide broader Bitcoin context:

See Also

Sources

  1. Nicolas Dorier, “BIP 78: A Simple Payjoin Proposal,” Bitcoin Improvement Proposals, assigned May 1, 2019, accessed November 10, 2026, https://github.com/bitcoin/bips/blob/master/bip-0078.mediawiki.
  2. Dan Gould and Yuval Kogman, “BIP 77: Async Payjoin,” Bitcoin Improvement Proposals, version 0.2.0, July 8, 2025, accessed November 10, 2026, https://github.com/bitcoin/bips/blob/master/bip-0077.md.
  3. Ava Chow, “BIP 174: Partially Signed Bitcoin Transaction Format,” Bitcoin Improvement Proposals, version 1.4.4, accessed November 10, 2026, https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki.
  4. Payjoin, “Async Payjoin (BIP 77, V2),” Payjoin Documentation, accessed November 10, 2026, https://github.com/payjoin/payjoin.org/blob/master/docs/how-it-works/payjoin-v2-bip-77.md.
  5. Payjoin, “Announcing Payjoin 1.0,” August 12, 2026, accessed November 10, 2026, https://github.com/payjoin/payjoin.org/blob/master/blog/2026-08-12-announcing-payjoin-1-0.md.