Skip to main content

​
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

See the Sequence Diagram

View the full flow from payment intent through receipt viewing

​
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

Quick Start Guide

Follow the integration guide for your role in the ecosystem.

​
Integration Guides

Card Issuers

SDK integration for banking apps

End Users

Understanding receipt ownership and portability

Merchants

Receipt signing and transmission

POS Systems

Plugin and native integration options

​
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.

Open the Interactive Demo

Launch the full-screen banking app demo in a new tab

Client-Side Decryption

Private keys never leave the device. Decryption happens in secure hardware.

Biometric Authentication

Face ID or Touch ID is required to open receipts.

End-to-End Encryption

Receipts are encrypted before transmission. Only the customer can decrypt them.

Cryptographic Signatures

Dual signatures from merchant and issuer prevent tampering.

​
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.