Skip to main content
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
source_trx_hash
destination_trx_hash
Unique hash of the on-chain transaction.
blockchain_memoOptional field available for some blockchains (e.g. Tron, Stellar) to route payments correctly.

🇺🇸 ACH (USD)

FieldDescription
trace_numberUnique identifier used to track ACH payments through the U.S. banking system.
ach_referenceOptional free form field that may appear on the customer’s bank statement. Useful for reconciliation.

🇺🇸 Wire (USD)

FieldDescription
imadUnique identifier used to track WIRE payments through the banking system.
wire_messageOptional free form field that may appear on the customer’s bank statement. Useful for reconciliation.

🇪🇺 SEPA (EUR)

FieldDescription
uetrUnique identifier used to track SEPA payment through the banking system. UUID format included in ISO 20022-compliant wires. Supported by most modern banks.
sepa_referenceOptional free form field that may appear on the customer’s bank statement. Useful for reconciliation. Strongly recommended to use a UUID for automated matching.
⚠️ When initiating SEPA payments with Bridge, always include a UUID in the reference field.

🇲🇽 SPEI (MXN)

FieldDescription
tracking_numberUnique identifier or tracing SPEI payments through the Mexican payment system.
spei_referenceOptional free form field that may appear on the customer’s bank statement. Useful for reconciliation.

🇧🇷 PIX (BRL)

FieldDescription
transaction_idUnique E2E (end-to-end) identifier used to track PIX payment through the banking system.
referenceOptional free form field that may appear on the customer’s bank statement. Useful for reconciliation.

🇬🇧 FASTER PAYMENTS (GBP)

FieldDescription
transaction_idUnique identifier used to track FPS payments through the banking system.
referenceOptional free form field that may appear on the customer’s bank statement. Useful for reconciliation.

🇪🇨 Bre-B & Bank Transfers (COP)

FieldDescription
transaction_idUnique identifier used to track COP Bre-B and Bank Transfer payments through the banking system.
referenceOptional free form field that may appear on the customer’s bank statement. Useful for reconciliation.