Concept
What is an onchain receipt?
Onchain receipts are verifiable proof that a payment happened. Learn what they contain, how zkReveal records them on Arbitrum, and why apps and agents rely on them.
An onchain receipt is verifiable proof that a payment happened. When a buyer pays a zkReveal payment link, Arbitrum records the purchase as a structured event — so any app, bot, backend, or agent can confirm the sale directly against the blockchain instead of trusting a private database.
Why payments alone aren't enough
Most crypto checkouts stop at moving money: you get a transfer, but nothing that says what was bought or ties the payment to an order. That gap forces sellers to reconcile transfers by hand and makes it hard for software to react automatically. An onchain receipt closes the gap by pairing the settlement with purchase context.
What a receipt contains
- The listing that was purchased and the amount settled in USDC.
- A purchase reference that links the payment back to a specific order.
- Fee routing — the protocol fee and any optional integrator fee.
- The parties involved, so fulfillment and settlement can be verified.
How zkReveal records receipts
Checkout runs through zkReveal's onchain contracts on Arbitrum. The payment and the receipt are written in the same transaction and surfaced as events (for example, a receipt event when a purchase settles and fee events for the protocol and integrator shares). Listing metadata is referenced by an IPFS commitment, so the receipt can be verified against what was advertised without exposing private data.
Why apps and agents rely on them
Because a receipt is public and tamper-proof, software can trust it as a trigger. A backend can unlock an API key, a Telegram bot can grant access, a dashboard can mark an order paid, or an AI agent can proceed to the next step — all by reading a receipt event rather than asking a server whether the payment cleared.
Verify it yourself
Every receipt lives on Arbitrum, so it can be independently checked on a block explorer or indexed by anyone. That's the point: the proof doesn't depend on zkReveal staying online. Next, see how sellers, bots, and agents put receipts to work.
Frequently asked questions
Is an onchain receipt the same as a transaction hash?
Not quite. A transaction hash proves a transfer occurred; a zkReveal receipt is a structured purchase event tied to a specific listing and purchase reference, so an app can tell what was bought, not just that money moved.
Can a receipt be faked or altered?
No. Receipts are recorded on Arbitrum as part of the payment transaction. Anyone can independently verify them against the chain, and they can't be changed after the fact.
Does the receipt expose private buyer data?
Receipts carry settlement context and a purchase reference rather than personal details. Listing metadata is committed by hash, so systems can verify a purchase without publishing sensitive information.
Create your first payment link
Spin up a USDC payment link on Arbitrum in seconds and turn every sale into a verifiable onchain receipt.
Create Payment Link →