Transaction Hash

Overview

A transaction hash identifies a record, not a customer

A transaction hash, sometimes called a transaction ID or txid, is a compact identifier derived from a transaction's data according to the blockchain protocol. People copy it into a block explorer to look up the transaction. It is useful like a tracking number for a parcel: it points to a record for further inspection. By itself, however, a string of hexadecimal characters does not establish that a merchant received the right token, that the right invoice was paid, or that the transfer has reached the required confidence level.

How the underlying system works

The rules for producing a transaction identifier vary by chain and transaction format. Bitcoin uses a transaction ID derived from serialized transaction data, while Ethereum transactions are identified by a hash of their signed transaction representation. A hash should always be interpreted together with the chain, because it is not a universal payment identifier across unrelated networks.

For merchant reconciliation, record the transaction hash plus the network, relevant address, asset, amount and invoice reference. Some transactions can include multiple outputs or smart-contract token events, so the hash alone may be insufficient to link one specific transfer to one order. Check inclusion, execution status and confirmation or finality policy before treating the payment as accepted.

How to investigate a claimed transfer

A customer says they paid and shares a txid. The merchant first determines the intended chain; a hash is meaningful only in the context of the relevant network and protocol. Next it finds the transaction and checks whether it succeeded or is included in a block. For a Bitcoin transaction, inspect the relevant output and destination. For an ERC-20 payment, inspect the successful transaction and token transfer events from the expected contract. Then match the recipient, amount, asset and tracking record with the invoice. Finally, assess the appropriate confirmation/finality policy. The txid helps find evidence; it is not the entire evidence.

What can make a hash confusing

A transaction can be visible while still pending. A smart-contract call can have an identifiable hash even when execution reverts and no intended token payment occurs. One transaction may carry multiple token transfers or outputs, so crediting an invoice solely because a hash appears can be wrong. The same textual hash should never be considered a cross-chain identifier without specifying the network. Keep stable references linking the order, invoice and relevant on-chain transfer details. Customer support can use a txid to investigate, but should never accept it as a substitute for verified receipt.

Further reading and related concepts

Reference documents: Bitcoin Developer — Transactions, Ethereum.org — Transactions.

Related glossary topics: Confirmation, Blockchain Payment Monitoring, Transaction Reconciliation.