A phone on a desk stand beside everyday belongings in a sunlit coastal setting, editorial illustration
BIP 78 / PAYMENTS

A payment made together.

Payjoin lets sender and receiver negotiate a transaction that includes contributions from both parties.

Read the explanation
← All standards

Why it exists

BIP 78 defines an interactive Payjoin payment between sender and receiver. The receiver contributes transaction inputs as well as receiving value, making the common assumption that every input belongs to one person less reliable. The final result is an ordinary Bitcoin transaction.

How it works

The receiver advertises a Payjoin endpoint through the pj parameter in a payment URI. The sender builds a broadcastable original payment as a PSBT and submits it over an authenticated, encrypted connection. Unneeded wallet metadata should be removed before sharing.

The receiver returns a modified proposal with its contributions signed. The sender validates the changes, including preserved sender outputs, input constraints and the allowed fee contribution, before signing its own inputs again and broadcasting. The original payment provides a fallback if negotiation cannot complete.

PUT IT IN CONTEXT

A practical example

Ignoring fees to make the arithmetic clear, a customer could contribute a 100,000-sat input for a 30,000-sat purchase. If the merchant adds a 50,000-sat input, a resulting transaction can return 70,000 sats to the customer and 80,000 sats to the merchant. Real transactions must also allocate the mining fee.

What to keep in mind

Both parties need compatible software and suitable coins. Negotiation reveals information to the counterparty, and network metadata or later spending can still link activity. Payjoin is not a guarantee of anonymity, and a modified PSBT must never be signed without validation.

Status & implementation

BIP 78 is Deployed as an application protocol. It uses BIP 174 PSBTs and ordinary transaction validity rules, requiring no new consensus activation. Endpoint compatibility and sender/receiver capabilities determine whether a particular payment can use it.

Specification status: Deployed · Sources checked 13 November 2026

Read the sources

Put the standard in context.

Explore the practical guide

Find your next answer.

Search the complete field guide · Esc to close