Receipt
Pronunciation: ree-SEET
Also known as: Transaction Receipt Record, Payment Receipt
Definition
A receipt is a record showing that a transaction, payment, or system action was processed and describing its result. In blockchain applications, the word may refer to a protocol transaction receipt, a wallet confirmation, or a merchant document. These are not interchangeable. A useful receipt identifies the transaction, parties or destination, asset, amount, time, status, and evidence source without claiming more than it proves.
Overview
Meaning and scope
A receipt is a record showing that a transaction, payment, or system action was processed and describing its result. In blockchain applications, the word may refer to a protocol transaction receipt, a wallet confirmation, or a merchant document. These are not interchangeable. A useful receipt identifies the transaction, parties or destination, asset, amount, time, status, and evidence source without claiming more than it proves.
Mechanism and operation
A merchant receipt documents a purchase or payment relationship, a wallet receipt summarizes a submitted transfer, and a protocol-level Blockchain Receipt records execution details generated by the blockchain. A user-facing crypto payment receipt can include order ID, amount, asset, network, destination, transaction hash, payment state, timestamps, and merchant information. A protocol receipt proves only the fields committed or reported by the network. Conversely, a merchant PDF can contain business details but may rely on a transaction reference that still needs independent chain verification. Receipts should be immutable in audit history but correctable through versioned records or credit notes when business data changes.
Practical payment example
An EVM indexer inspects a transaction receipt to determine success, gas consumed and emitted logs. It still verifies the receiving contract and transfer event to attribute payment to the correct invoice.
Operational checks
Sensitive information should not be placed on-chain merely to create permanent evidence. Organizations need retention, privacy, and access rules appropriate to the receipt’s purpose. For reconciliation, a receipt should link the business record to the underlying transfer and Payment State. Users should be able to verify the network and transaction without exposing secrets.
Distinctions and limits
It should distinguish detected, confirmed, paid, refunded, and failed conditions rather than presenting an early transaction submission as final settlement. It does not establish the customer’s legal identity, the description of goods, tax treatment, or delivery.
Related reading
Related definitions: Blockchain Receipt, Payment State.
Example
An EVM indexer inspects a transaction receipt to determine success, gas consumed and emitted logs. It still verifies the receiving contract and transfer event to attribute payment to the correct invoice.
Comparison
It should distinguish detected, confirmed, paid, refunded, and failed conditions rather than presenting an early transaction submission as final settlement. It does not establish the customer’s legal identity, the description of goods, tax treatment, or delivery.
Key Takeaway
A receipt is useful only when it states what kind of evidence it contains and distinguishes transaction submission, blockchain execution, payment acceptance, and commercial proof.
Sources
- EIP-658: Embedding Transaction Status Code in Receipts — Ethereum Improvement Proposals (2026-08-02)
- OxaPay Documentation: Payment Status Table — OxaPay (2026-08-02)
- Bitcoin Developer Guide: Payment Processing — Bitcoin Developer Documentation (2026-08-02)