A Unique End-to-End Transaction Reference (UETR) is a unique identifier assigned to a qualifying cross-border payment message when the payment is first sent, and carried unchanged by every institution that handles it afterward. Because the same reference travels through the whole chain, the sending bank, any intermediary banks and the beneficiary bank can all recognize the payment as one and the same, and its progress can be tracked from start to finish.
The UETR was introduced on the SWIFT network as the backbone of SWIFT gpi (global payments innovation) and has since become a standard element of cross-border payment messages in both the legacy MT format and ISO 20022.
Format
A UETR is a 36-character string that follows the format of a version 4 universally unique identifier (UUID), as defined in the IETF standard RFC 4122. It consists of 32 hexadecimal characters arranged in five groups separated by hyphens, for example eb6305c9-1f7f-49de-aed0-16487c27b42d. Version 4 UUIDs are generated largely at random, so the chance of two banks producing the same value is negligible, and no central registry is needed to allocate them.
How the UETR works
Before the UETR, each bank in a correspondent chain typically assigned its own transaction reference. When a payment passed through three or four banks, there was no shared key linking the messages, and tracing a delayed or missing payment required each bank to search its own records and send queries along the chain.
With a UETR, the first instructing agent creates the reference and every subsequent bank must pass it on unchanged. In SWIFT MT messages, it is carried in field 121 of the user header block, for example in the MT103 customer credit transfer and the related cover message. In ISO 20022 messages such as the pacs.008 customer credit transfer, it has its own element within the payment identification. When a payment is split into a customer message and a separate cover payment, both messages carry the same UETR, which helps banks match the two.
SWIFT made the UETR mandatory on the main payment messages carried on its network in November 2018, extending its use beyond banks that had signed up to gpi.
Role in tracking and investigations
The UETR is the key used by the SWIFT gpi Tracker, a central database that records status updates from each bank as the payment moves: received, forwarded, credited to the beneficiary, or rejected, along with fees deducted and exchange rates applied. A bank or its customer can query the status of a payment using its UETR.
The reference is equally important when something goes wrong. A payment trace, a payment investigation or a payment recall request can quote the UETR, letting every bank in the chain locate the right transaction immediately rather than matching on amount, date and names. Customers who want to trace their own SWIFT wire are often asked for the UETR, which many banks now print on payment confirmations.
Example
A company in Canada sends USD 25,000 to a supplier in Kenya. Its bank generates a UETR and sends an MT103 to a US correspondent, which forwards it to a Kenyan bank. The supplier reports that only USD 24,950 arrived and two days late. Using the UETR, the paying bank can see in the tracker which correspondent took a fee and when each bank processed the payment, explaining both the short-paid amount and the delay without sending a chain of manual queries.
Limitations
The UETR identifies a payment but does not guarantee transparency on its own. Tracking depends on each bank in the chain reporting status updates, and payments that leave the SWIFT network, for example into a domestic system that does not carry the reference, may lose end-to-end visibility. The UETR is also distinct from the end-to-end identification chosen by the paying customer, which is meant for the customer's own reconciliation rather than interbank tracking.