Last reviewed: · Curated by Ohmyfin Organisation editorial.
A UETR (Unique End-to-end Transaction Reference) is a 36-character identifier attached to every SWIFT payment to allow the sender, beneficiary and every intermediary bank to track it in real time across the SWIFT correspondent banking network. Draft an MT103 with a fresh UETR → · Track any UETR free →
The UETR is generated by the originating bank when the payment is created and travels with the payment through every correspondent bank in the chain. It is mandatory on every SWIFT MT message since November 2018 as part of the SWIFT GPI (Global Payments Innovation) standard. Before GPI, there was no universal end-to-end tracking ID — banks had to call each other manually to locate a missing wire.
The format is 36 characters in 5 hexadecimal groups: 8-4-4-4-12, separated by dashes. Example: 12345678-1234-4abc-9def-1234567890ab. The third group always begins with the digit "4", making it a UUID v4 (universally unique identifier, version 4). This format was chosen because UUID v4 is already a well-established standard with excellent collision-resistance — the probability of two banks accidentally generating the same UETR is astronomically small.
On an MT103 SWIFT message the UETR appears in field 121 inside block 3 (the user header block). The exact tag format is {121:xxxxxxxx-xxxx-4xxx-xxxx-xxxxxxxxxxxx}. On ISO 20022 pacs.008 messages it appears in the <UETR> XML element inside the GrpHdr (GroupHeader) / PmtInf / CdtTrfTxInf block.
SWIFT GPI-member banks are required to update the UETR tracking record every time the payment passes through them, adding their status update within minutes of processing. This gives everyone in the payment chain — including the original sender — a real-time view of exactly where the money is and what status code was applied at each hop.
You can use the UETR to look up the latest available status on Ohmyfin. The tracker queries the SWIFT GPI network and returns the payment status (ACSP, ACWP, ACCC, RJCT, etc.), the current holding bank, the fees applied at each hop, and the expected credit time. This service is completely free for individuals — see /how-long for typical settlement times by corridor.
Common mistakes when working with UETRs: (1) confusing the UETR with the TRN (transaction reference number, field 20) — the TRN is bank-specific and changes at each hop, while the UETR is global and constant; (2) truncating the UETR by removing the dashes — the full 36-character form including dashes is required; (3) confusing the UETR with a tracking number from a fintech app — not all payment apps use SWIFT, and some use internal IDs that are not UETRs.
If your bank does not show the UETR on the payment receipt, ask them specifically for "field 121 from the SWIFT GPI MT103 confirmation". All GPI member banks — which covers practically every international bank in the world — are required to provide this on request. If your bank refuses, escalate to their payments investigations team and quote the SWIFT GPI Rulebook obligation.
Ask your sending bank for the SWIFT GPI payment confirmation. The UETR is in field 121 of the MT103 — a 36-character code in the format xxxxxxxx-xxxx-4xxx-xxxx-xxxxxxxxxxxx. Many online banking platforms now display the UETR on the payment receipt page. If your bank does not show it, quote the SWIFT GPI Rulebook obligation and ask their payments team.
A UETR looks like this: a1b2c3d4-5e6f-4a7b-8c9d-0e1f2a3b4c5d. It is always exactly 36 characters, split into five groups by dashes (8-4-4-4-12), and the first character of the third group is always the digit 4. It uses only hexadecimal characters (0–9 and a–f).
The originating bank generates the UETR when the payment instruction is first created, before the MT103 or pacs.008 message is sent into the SWIFT network. The UETR is then passed unchanged through every correspondent bank in the chain until it reaches the beneficiary bank.
Yes — Ohmyfin can also look up payments by bank reference (MT103 field 20, also called the TRN). However, a UETR gives far more precise live status because it is unique globally, whereas a TRN is unique only within the issuing bank.
A UETR contains no personal data — it is just a random UUID. It is safe to share with the beneficiary, their bank, or a trusted tracking service like Ohmyfin so they can check the payment status.
No. Each UETR is generated once and must be globally unique. SWIFT GPI banks are required to reject any payment that carries a UETR they have already seen — this prevents replay attacks. UUID v4 generation makes accidental duplication virtually impossible.
No card needed. Free for ordinary users — completely free for individuals — no daily limit, no card required. Track any international wire across 11,000+ banks.
Track a payment now — completely free Or try the tracker now →