> ## Documentation Index
> Fetch the complete documentation index at: https://docs.digitalreceiptprotocol.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Quick Start Guide

> Get started with DRP integration in minutes

## Integration Paths

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

<CardGroup cols={2}>
  <Card title="Card Issuers" icon="building-columns" href="/essentials/card-issuers">
    Integrate DRP into your banking app to reduce chargebacks and enhance customer experience.
  </Card>

  <Card title="Merchants" icon="shop" href="/essentials/merchants">
    Send cryptographically signed receipts to prevent disputes and build customer loyalty.
  </Card>

  <Card title="POS Systems" icon="cash-register" href="/essentials/pos-systems">
    Enable all your merchants to send encrypted receipts with a single integration.
  </Card>

  <Card title="End Users" icon="user" href="/essentials/end-user">
    Learn how to access and manage your encrypted receipt history.
  </Card>
</CardGroup>

***

## For Developers

### Step 1: Choose Your Integration Type

<AccordionGroup>
  <Accordion icon="building-columns" title="Card Issuer Integration">
    **Timeline:** 2-4 weeks for full native integration

    **What you need:**

    * iOS/Android banking app
    * Backend webhook receiver
    * Public key distribution infrastructure

    **Get started:**

    1. Review the [Card Issuers guide](/essentials/card-issuers)
    2. Download SDKs: [Swift](https://github.com/drp/ios-sdk), [Kotlin](https://github.com/drp/android-sdk)
    3. Set up sandbox environment for testing
  </Accordion>

  <Accordion icon="shop" title="Merchant Integration">
    **Timeline:** 8-15 hours for plugin installation, 2-4 weeks for custom API

    **What you need:**

    * POS system or e-commerce platform
    * Itemized transaction data
    * Key management infrastructure

    **Get started:**

    1. Review the [Merchants guide](/essentials/merchants)
    2. Check if your POS has a DRP plugin
    3. Or integrate directly with our API
  </Accordion>

  <Accordion icon="cash-register" title="POS System Integration">
    **Timeline:** 2-4 weeks for full integration

    **What you need:**

    * Existing receipt generation capability
    * Plugin/extension infrastructure
    * Merchant key management system

    **Get started:**

    1. Review the [POS Systems guide](/essentials/pos-systems)
    2. Download reference implementation
    3. Join developer community forum
  </Accordion>
</AccordionGroup>

***

### Step 2: Technical Resources

<CardGroup cols={2}>
  <Card title="Protocol Specification" icon="file-lines" href="/api-reference/introduction">
    Complete technical documentation of the DRP protocol
  </Card>

  <Card title="GitHub Repositories" icon="github" href="https://github.com/digitalreceiptprotocol">
    Open-source SDKs and reference implementations
  </Card>

  <Card title="Try the Demo" icon="flask" href="/demo/overview">
    Test DRP with our interactive banking demo
  </Card>

  <Card title="Developer Support" icon="comments" href="mailto:support@digitalreceiptprotocol.org">
    Get help from our engineering team
  </Card>
</CardGroup>

***

### Step 3: Testing & Certification

<Steps>
  <Step title="Local Development">
    Set up the DRP SDK in your development environment and test basic receipt generation and encryption flows.
  </Step>

  <Step title="Sandbox Testing">
    Connect to our sandbox environment to test end-to-end receipt transmission with simulated partners.
  </Step>

  <Step title="Pilot Program">
    Launch with 5-10 real partners to validate integration under production conditions.
  </Step>

  <Step title="Production Deployment">
    Roll out to your full merchant or user base with confidence.
  </Step>
</Steps>

***

## 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

<CardGroup cols={2}>
  <Card title="Read the Spec" icon="book" href="/api-reference/introduction">
    Understand the complete protocol specification
  </Card>

  <Card title="Join Community" icon="users" href="https://github.com/digitalreceiptprotocol">
    Connect with other developers implementing DRP
  </Card>

  <Card title="Request Consultation" icon="handshake" href="mailto:support@digitalreceiptprotocol.org">
    Schedule a technical consultation with our team
  </Card>

  <Card title="View Examples" icon="code" href="/sdks/examples">
    Browse working code examples and reference implementations
  </Card>
</CardGroup>

<Note>
  **Questions?** Contact our developer team at [support@digitalreceiptprotocol.org](mailto:support@digitalreceiptprotocol.org) or join our community forum.
</Note>