Skip to main content

​
What is Vero?

Vero is an open protocol that enables merchants to send encrypted, itemized receipts directly to customers’ banking apps during transactions. Like OAuth standardized authentication and HTTP standardized web communication, Vero 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 Vero Solves

Current digital receipt systems store user 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

​
Frequently Asked Questions

Existing solutions store receipts on merchant or third-party servers—you’re granted access, not ownership. Vero uses client-side encryption where your private key never leaves your device. Merchants, banks, and even Vero cannot decrypt your receipts.
No. Vero is an open-source protocol, like HTTP or OAuth. There’s no vendor lock-in, no transaction fees, and no licensing costs. The protocol is being submitted for W3C standardization.
You can use an open-source reference wallet app to receive and store receipts independently. Once your bank integrates Vero, you can migrate your receipt history since you control the private keys.
Vero includes retroactive encryption capability. When issuers integrate Vero, they can encrypt existing receipt data from transaction history and deliver it to users.
Receipts are portable. Export your encrypted receipt history in JSON-LD format and import it into your new banking app. True ownership means your data travels with you.