Skip to main content

Integration Paths

Choose your integration path based on your role in the receipt ecosystem.

For Developers

Step 1: Choose Your Integration Type

Timeline: 2-4 weeks for full native integrationWhat you need:
  • iOS/Android banking app
  • Backend webhook receiver
  • Public key distribution infrastructure
Get started:
  1. Review the Card Issuers guide
  2. Download SDKs: Swift, Kotlin
  3. Set up sandbox environment for testing
Timeline: 8-15 hours for plugin installation, 2-4 weeks for custom APIWhat you need:
  • POS system or e-commerce platform
  • Itemized transaction data
  • Key management infrastructure
Get started:
  1. Review the Merchants guide
  2. Check if your POS has a DRP plugin
  3. Or integrate directly with our API
Timeline: 2-4 weeks for full integrationWhat you need:
  • Existing receipt generation capability
  • Plugin/extension infrastructure
  • Merchant key management system
Get started:
  1. Review the POS Systems guide
  2. Download reference implementation
  3. Join developer community forum

Step 2: Technical Resources


Step 3: Testing & Certification

1

Local Development

Set up the DRP SDK in your development environment and test basic receipt generation and encryption flows.
2

Sandbox Testing

Connect to our sandbox environment to test end-to-end receipt transmission with simulated partners.
3

Pilot Program

Launch with 5-10 real partners to validate integration under production conditions.
4

Production Deployment

Roll out to your full merchant or user base with confidence.

Key Concepts

Before diving into integration, familiarize yourself with these core DRP concepts:

Client-Side Encryption

Private keys are generated and stored exclusively on user devices in hardware security modules (iOS Secure Enclave, Android KeyStore). No server ever touches private keys—this ensures true user ownership.

Dual Signatures

Every receipt includes cryptographic signatures from both the merchant and the card issuer, preventing forgery and ensuring authenticity.

JSON-LD Format

Receipts use JSON-LD semantic markup for interoperability across systems and future extensibility.

Retroactive Encryption

When issuers integrate DRP, they can encrypt existing transaction history from their databases, giving users cryptographic ownership of their complete receipt history.

Next Steps

Questions? Contact our developer team at [email protected] or join our community forum.