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

# Digital Receipts

> Encrypted, itemized receipts in your customers' banking apps, to help reduce chargebacks

### What are Vero digital receipts?

Digital receipts are a supplemental offering included with Vero Merchants. When you connect your POS, Vero sends an encrypted, itemized copy of each receipt to your customer's banking app.

**Why it matters for merchants:** when customers can see exactly what they bought next to the charge, they recognize it. That means fewer "I don't recognize this charge" disputes, fewer chargebacks and less friendly fraud, with nothing to change at checkout.

Under the hood is an open protocol. Like OAuth standardized authentication and HTTP standardized web communication, it provides a standard layer for receipt data ownership.

**Technical foundation:**

* Client-side encryption with RSA-2048 (private keys never leave user devices)
* Hardware security module integration (iOS Secure Enclave, Android KeyStore)
* Dual signatures from merchants and issuers for verification
* JSON-LD for semantic interoperability
* Open-source protocol with no vendor lock-in

***

### The Problem Digital Receipts Solve

For merchants, a charge the customer doesn't recognize turns into a dispute, and disputes cost fees, lost revenue and staff time. For customers, current digital receipt systems store their data on merchant or third-party servers. Users don't truly own their transaction history—they're granted access to corporate databases. This creates friction for expense reporting, disputes, returns, and data portability.

Vero provides cryptographic ownership: users hold the only key to decrypt their receipts. Receipts are verified, itemized, and portable without compromising privacy or security.

***

### How It Works

#### Four-Step Flow

1. **Transaction occurs** - Customer pays at merchant POS
2. **Receipt generated** - Merchant creates itemized receipt, signs with their private key
3. **Encrypted transmission** - Receipt encrypted with user's public key, sent to issuer
4. **User decryption** - Only user can decrypt receipt in their banking app with private key stored in device hardware

<Card title="See the Sequence Diagram" icon="diagram-project" href="/api-reference/sequence-diagram">
  View the full flow from payment intent through receipt viewing
</Card>

***

### Protocol Participants

**Card Issuers:** Integrate SDK to provide receipt viewing in banking apps

**Merchants:** Send cryptographically signed receipts through POS systems

**POS Systems:** Provide plugin or native integration for receipt generation

**End Users:** Receive encrypted receipts with full data ownership

***

## Get Started

<Card title="Quick Start Guide" icon="rocket" horizontal href="/digital-receipts/quickstart">
  Follow the integration guide for your role in the ecosystem.
</Card>

## Integration Guides

<Columns cols={2}>
  <Card title="Card Issuers" icon="building-columns" href="/essentials/card-issuers">
    SDK integration for banking apps
  </Card>

  <Card title="End Users" icon="user" href="/essentials/end-user">
    Understanding receipt ownership and portability
  </Card>

  <Card title="Merchants" icon="shop" href="/essentials/merchants">
    Receipt signing and transmission
  </Card>

  <Card title="POS Systems" icon="cash-register" href="/essentials/pos-systems">
    Plugin and native integration options
  </Card>
</Columns>

***

## Interactive Demo

See encrypted receipts in a simulated banking app: the transaction list marks purchases that carry a Vero receipt, and tapping one opens the itemized receipt with merchant, payment and tax details.

<Card title="Open the Interactive Demo" icon="arrow-up-right-from-square" href="https://www.digitalreceiptprotocol.org/#demo" horizontal>
  Launch the full-screen banking app demo in a new tab
</Card>

<CardGroup cols={2}>
  <Card title="Client-Side Decryption" icon="lock">
    Private keys never leave the device. Decryption happens in secure hardware.
  </Card>

  <Card title="Biometric Authentication" icon="fingerprint">
    Face ID or Touch ID is required to open receipts.
  </Card>

  <Card title="End-to-End Encryption" icon="shield-halved">
    Receipts are encrypted before transmission. Only the customer can decrypt them.
  </Card>

  <Card title="Cryptographic Signatures" icon="signature">
    Dual signatures from merchant and issuer prevent tampering.
  </Card>
</CardGroup>

### Use Cases

* **Expense reports:** the receipt is already in the banking app, ready to export with details filled in.
* **Tax preparation:** every receipt in one place, exportable by date or category.
* **Returns and warranties:** a signed receipt is proof of purchase, even when the paper one is lost.
* **Disputes:** an itemized, signed receipt makes chargebacks faster to resolve.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.