What is a UETR?
A UETR is a 36-character code, formatted as a UUID, that gets assigned to a SWIFT payment the moment it is created and never changes. UETR stands for Unique End-to-End Transaction Reference. Think of it as a tracking number for an international wire. No matter how many banks the payment passes through on its way to the recipient, the UETR stays exactly the same. That consistency is what lets every bank in the chain confirm the status of one specific payment.
SWIFT made the UETR mandatory for all members in November 2018, not just banks signed up to its gpi tracking service. Every SWIFT payment created since then has one.
What does a UETR look like?
A UETR follows the UUID version 4 format. It is 36 characters long, made up of hexadecimal digits split into five groups by hyphens. An example looks like this:
eb6305c4-3e7a-4b29-9a1f-8d2ce5a71b30
In an MT103 message, the older SWIFT format, the UETR sits in Field 121 of the message header. In the newer ISO 20022 format, pacs.008, it appears as its own dedicated UETR field inside the payment identification block.
How is a UETR different from a transaction reference number?
This is the most common source of confusion. The two look similar but serve different purposes.
A TRN is generated by the sending bank and lives in Field 20 of the MT103. As the payment moves through intermediary banks, this reference can change or disappear entirely. The UETR does not. It is the one constant identifier that every bank involved can recognize.
How do you use a UETR to track a payment?
The UETR works alongside the SWIFT gpi Tracker, a system that collects status updates from every bank that touches a payment. Each participating bank confirms when it receives and forwards the payment, building a timeline tied to that one UETR.
Full access to the gpi Tracker is generally limited to SWIFT gpi member banks. As an individual or a business, you typically cannot log in and check it yourself. In practice, this means:
- Ask your bank for the UETR, usually found on a payment confirmation or wire advice
- Provide the UETR to your bank's international payments team if a transfer seems delayed
- Your bank queries the gpi Tracker on your behalf and reports back the current status
Some banks now surface this data directly inside their own online banking portals, but adoption is uneven across institutions.
What is the difference between a UETR and other payment reference numbers?
Cross-border payments involve more than one type of reference number, and they operate at different layers.
The UETR governs the payment itself, the business-level journey from sender to recipient. MIR and MOR (Message Input/Output Reference) are different identifiers that operate one layer down, at the SWIFT FIN network's message transport layer, tracking the technical delivery of the message itself rather than the underlying payment.
US domestic wires carry their own separate references entirely. Fedwire uses IMAD and OMAD numbers, which have no relationship to UETR or the SWIFT network. A UETR only applies to payments sent over SWIFT.
Why UETRs matter for payment operations
For platforms and businesses sending or receiving cross-border payments, the UETR is the single reliable hook for resolving a delayed or disputed wire. Before UETRs existed, tracing a payment across several correspondent banks meant a chain of phone calls and emails, each bank using its own internal reference.
A UETR removes that friction. It also supports payment reconciliation, since a consistent end-to-end reference makes it easier to match an outgoing SWIFT payment to its confirmed settlement, rather than relying on amount and date alone. For high-volume originators routing payments through correspondent banking chains as part of an interbank settlement process, capturing and storing the UETR for every outbound wire is a practical way to reduce the time spent investigating exceptions.
