Transaction ID (TxID)

Overview

A blockchain transaction ID allows nodes, explorers, and applications to retrieve the serialized transaction and related status. It is generally unique within the intended network, but the same textual format can appear on testnets or unrelated chains. Internal payment systems often create their own identifiers before an on-chain transaction exists. One payment can have several submission attempts or replacement hashes while keeping one internal transaction ID. Conversely, one blockchain transaction can contain several transfers mapped to multiple business records. APIs should expose both identifiers when needed. The internal ID supports stable workflow and permissions, while the on-chain ID supports independent verification. Renaming one as the other causes support and reconciliation errors.

Identifiers should be immutable after creation. If a transaction is replaced, the system should link the new blockchain ID to the same intent rather than overwrite history. Refunds and reversals need their own IDs linked to the original transaction. Users sharing a transaction ID should also specify the network. A valid ID may not appear in the selected explorer if it belongs to another chain or provider.

The term transaction ID is convenient but ambiguous. Documentation should define its source, scope, format, and relationship to blockchain hashes and business records. Data models should avoid using a mutable external hash as the primary key for the whole business workflow. A stable internal ID can remain constant through replacement, cancellation, or multi-stage settlement, while linked on-chain IDs record each attempt. API clients should receive both when relevant. This design improves retries and reporting without hiding the exact blockchain evidence behind the final result.