Portability and Sharing - Vero

Receipts belong to the customer, not to the merchant, the bank or Vero. Portability is what makes that real: a customer can take their receipts to another bank, or share them with a brokerage, an expense tool or a tax app, without asking anyone else.

Who can receive receipts

Recipient	Typical use
Card issuers and banks	Show receipts next to transactions in the banking app.
Brokerages and wealth platforms	Itemized spending for budgeting, planning and advice.
Expense and accounting tools	Fill in expense reports and bookkeeping from the receipt.
Tax software and accountants	Itemized proof of deductible purchases.
Merchants and warranty providers	Proof of purchase for returns and claims.

The customer chooses what to share: a single receipt, a date range or a category.
The customer’s device decrypts it with their private key.
The receipt goes to the recipient in the standard JSON-LD format, with its merchant and issuer signatures, so the recipient can check it is genuine.

Nothing is shared unless the customer chooses to share it. The recipient gets only what the customer sends, not the customer’s key or the rest of their history.

Switching banks

Because receipts follow an open format, a customer who moves to another bank or app that supports the protocol can export their receipts and bring them along. The signatures still verify after the move.

Why the format matters

Receipts use JSON-LD, so each field (merchant, line items, quantities, prices, taxes, payment method, time) has a defined meaning. A brokerage or tax app can read a receipt from any merchant without custom parsing for each one.

For platforms that want to receive receipts

If you’re a bank, brokerage or app that wants to receive receipts customers share, or show them in your own product, email hi@veromerchants.com. Card issuers can also start with the card issuer guide.