When accepting fiat payments via Bridge, it’s essential to track and reconcile deposits using standardized identifiers. These identifiers vary by payment rail and are surfaced in both APIS & webhooks. This guide outlines the fields to expect, how to match them programmatically, and how to display them to users.

​
🚧 Make sure customers include deposit messages

For Transfers and Static Memos, it’s critical that customers include the source deposit message (e.g. memo, SEPA reference, or wire message) so Bridge can automatically match incoming funds to the intended transfer. Virtual Accounts and Liquidation Addresses do not require deposit messages — the unique address itself is enough to match the payment.

​
Identifiers by Payment Rail

​
⛓️ Crypto

FieldDescription
transaction hashUnique hash of the on-chain transaction.
memoOptional field required by some blockchains (e.g. Tron, Stellar) to route payments correctly.

​
🇺🇸 ACH

FieldDescription
trace numberUnique identifier used to track ACH payments through the U.S. banking system.
ach referenceOptional statement descriptor that may appear on the customer’s bank statement. Useful for reconciliation.

​
🇺🇸 Wire

FieldDescription
imadUnique identifier to track wire payments.
wire messageOptional free-form field containing sender-provided text.
uetrA globally unique transaction reference (UUID format) included in ISO 20022-compliant wires. Supported by most modern banks.

​
🇪🇺 SEPA

FieldDescription
sepa referenceFreeform message provided by the sender. Strongly recommended to use a UUID for automated matching.

⚠️ When initiating SEPA payments with Bridge, always include a UUID in the reference field.

​
🇲🇽 SPEI

FieldDescription
tracking numberUnique identifier or tracing SPEI payments through the Mexican payment system.
spei referenceOptional reference field provided by the sender. Often used to describe or label the transaction.