An open standard for programmable receipt flows between merchants, payment processors, and consumers.
DRP is open-source and community-designed. Add features to the spec, integrate it into your systems, or build on top of our reference implementations.
Client-side encryption means that only the consumer who owns that encrypted receipt can ever read it. Financial institutions maintain only encrypted copies they cannot read.
DRP supports flexible and configurable data structures—line items, enabling granular dispute prevention, new financial products, and auditable transaction data.
Implement the DRP specification to generate encrypted receipt objects, so that any compatible wallet or application can securely render and display purchase data.
Experience the complete API flow for generating cryptographically secure digital receipts.
No API calls yet
Click 'Next' to start the flowThe card issuer generates a key pair and stores the private key in the consumer's secure enclave (iOS) or keychain (Android). The public key is registered with the protocol.
The merchant POS creates the payment and encrypts the receipt with the user's public key. Only the consumer's private key can decrypt it.
The consumer's private key decrypts the receipt locally on their device. The private key never leaves the secure enclave.
Take true ownership of your digital receipts with cryptographic security. Access itemized transaction history across all your cards without merchant silos or privacy compromises.
View the docs →Any merchant, payment processor, or wallet application can implement the DRP spec to participate in providing portable, verifiable receipts to consumers across purchases, delivery, and returns.
Any wallet or application can implement DRP. Visit the spec to review its structure, or use one of the reference implementations provided there.
No. The DRP spec is a secure format for receipt transmission. Recipients—typically financial institutions—need to explicitly integrate to ingest your receipts. Alternatively, use hosted-provider platforms which need to apply or configure access.
Yes. DRP can integrate with any payment API. The protocol is designed to work alongside existing payment networks without requiring processor changes.
Upon onboarding, a wallet developer can query participant metadata that marks merchants as DRP-enabled, allowing simple discovery between certified wallets and participating merchants.
The private key is stored exclusively in the consumer's device secure enclave (iOS) or keychain (Android) and never leaves the device. Only the consumer can use their private key to decrypt receipts—merchants, card issuers, and the protocol itself cannot access it.
As transactions move from paper to digital, the ecosystem needs a new set of standards for open, portable, and privacy-first digital receipt infrastructure. The Digital Receipt Protocol defines a common language for how merchants, financial institutions, and consumers transact—including generating capsules and securely sharing receipt credentials. DRP is a collaborative, open-source standard and we'd love for you to help improve it.
Become a contributor →