Why it exists
BIP 47 creates reusable payment codes for hierarchical deterministic wallets. A person can publish one identifier while compatible counterparties derive fresh on-chain destinations for payments. The code is public information; it is not a seed phrase or a private spending key.
How it works
In the version-1 flow, a sender first sends an on-chain notification that carries blinded payment-code information. The recipient detects and decodes it, establishing the information needed to recognise the sender’s subsequent payment addresses. Later payments use derived destinations rather than repeatedly paying the notification address.
The two wallets use shared-secret calculations and public-key derivation to agree on addresses without publishing the recipient’s entire wallet. Sending in the opposite direction requires the corresponding setup. Recovery must find the notification history and rebuild the relevant address sequences.
A practical example
Imagine a creator publishing a payment code for recurring supporters. A compatible supporter establishes the notification relationship once, then makes several payments to separately derived destinations. The creator’s wallet recognises them without sending a new receive address before each payment.
What to keep in mind
The notification transaction has cost and privacy implications. Its outputs and later change spending can reveal relationships. Publishing a payment code alongside an identity also links that identifier to the person. A conventional seed restore in a wallet without payment-code recovery is insufficient.
Status & implementation
BIP 47 is Deployed and describes compatibility for versions 1 and 2. The specification explicitly places later payment-code developments outside the BIP process. Check the exact version and recovery mechanism supported by both wallets rather than assuming all reusable identifiers interoperate.
Specification status: Deployed · Sources checked 13 November 2026
