What is a UETR number?
The 36-character SWIFT identifier explained.
A UETR (Unique End-to-end Transaction Reference) is the 36-character tracking code SWIFT has required on every international customer transfer since 18 November 2018. Every bank that handles the transfer keeps the same UETR, and the banks that report file a status against it, so one code lets you follow what they reported.
Think of a help-desk ticket passed between teams: each team records its update against the same ticket number, and the whole history stays in one place. The UETR does the same job for your transfer, and SWIFT's tracker collects the updates banks file into a single timeline.
Trace a SWIFT transfer
AI assistedSee bank reports, and get an email when the payment reaches a new stage.
UETR at a glance
A quick reference for what a UETR looks like, how long it is, and where it lives in a SWIFT message.
UETR Structure
UETR Validator
Paste a UETR and see if it parses as a valid RFC 4122 UUID v4.
This UETR is a well-formed RFC 4122 UUID version 4, the format SWIFT requires in field 121. Paste it into uetr.ai to check public bank trackers.
What does UETR mean?
UETR means Unique End-to-end Transaction Reference. It is the 36-character code SWIFT has required on every international payment since 18 November 2018. The sending bank generates it, and it stays unchanged as the payment moves between banks, so any bank in the chain can identify and report on that exact transfer.
What is a UETR code?
A UETR code is the same thing as a UETR number or a UETR reference. Banks, corporate portals, and payment confirmations use the three labels interchangeably, and all of them name one identifier: the 36-character Unique End-to-end Transaction Reference that SWIFT attaches to an international transfer.
There is no separate "code" with a different format. Whatever your bank calls it, a genuine UETR is 32 hexadecimal characters plus 4 hyphens in the pattern 8-4-4-4-12 (lowercase in its canonical form; a copy in capitals is the same reference), with the third group starting with 4 and the fourth starting with 8, 9, a, or b. Some banks print the same 32 digits without the hyphens (CommBank calls it a 32-character payment tracking reference); that is the UETR in compact form, and uetr.ai restores the hyphens. If a reference matches neither shape, it is an internal bank reference, not a UETR.
If your bank gave you one of those instead, see how to track an international wire transfer by reference number: it covers the Fed reference, provider references, and the steps a receiver can take without the UETR.
6f8d3a2b-1c44-4f8e-9b21-7d2c9f0a1b22
How do I check a UETR status?
Three steps. Every UETR check at uetr.ai is free. While the transfer is still in progress, uetr.ai re-checks it once every 24 hours for up to 30 days and emails you when the payment reaches a further stage. Paid plans re-check it every few minutes instead.
Copy the UETR
Take the 36-character UETR from your transfer confirmation or banking portal. On an MT103-format advice it is field 121. On a pacs.008-format document it is the UETR element inside PmtId.
Paste it into the tracker
Paste the UETR into uetr.ai. The tracker validates the format, then checks publicly reachable SWIFT gpi sources for status events tied to that UETR.
Read the latest status
ACSP means in transit, ACSC means a settlement leg has completed, ACCC means credited to the account, RJCT means rejected. The free check shows the plain-language status and how many banks have reported. Paid plans open the bank-by-bank reports with bank names and exact status codes.
UETR vs TRN vs BIC vs IBAN
People often confuse UETRs with the other identifiers on a payment. They are very different.
Scroll the table sideways to reach the Mandated since column.
| Identifier | What it identifies | Length & format | Scope | Mandated since |
|---|---|---|---|---|
| UETR | A single payment, end-to-end | 36 chars · UUID v4 · 8-4-4-4-12 | Across every SWIFT step | 18 Nov 2018 |
| TRN / sender's reference (field 20) | The sending bank's reference for an MT103 payment message | Up to 16 characters · 16x | Per message, not a shared end-to-end reference | Required in MT103 |
| BIC (SWIFT code) | A bank, branch, or financial institution | 8 or 11 chars · ISO 9362 (e.g. CHASUS33) | Routing within SWIFT | Bank identifier · stable |
| IBAN | A specific bank account | ≤34 chars · country + check + BBAN | EU / UK / GCC domestic accounts | Account identifier · stable |
Why does the UETR matter?
Before SWIFT introduced UETRs in 2018, there was no shared identifier that stayed with a transfer from start to finish. Once your bank sent the payment, even your own bank could not see what was happening to it. To find out, they had to send a separate free-text inquiry message (called an MT199) to the next bank, wait for a reply, then send another message to the bank after that, and so on along the chain.
Two consequences: customers received vague answers such as "it has left our system, please wait", and a single inquiry could take days because every bank in the chain responded on its own schedule.
The UETR replaced that with a shared identifier. Every bank that handles the transfer is now required to keep the UETR unchanged, and the banks that report publish a structured status update tied to it. SWIFT's tracker collects those updates as they arrive. That central Tracker is open only to eligible institutions, but a public lookup with the UETR reads the sources those banks publish.
The practical result: a delayed transfer is no longer invisible. The UETR tells you what the banks last reported: in transit, arrived at the beneficiary's bank, credited to the beneficiary account, held in compliance review, or rejected, which refuses the instruction rather than sending the money back. It also names the bank that filed that report, which is the one to ask, so you can tell a normal journey from one that is taking longer than an international transfer should.
The UETR in under a minute
What a UETR is, where it lives in MT103 and pacs.008 documents, and how it follows a transfer across the chain.
What does a UETR number look like?
The 36-character format at a glance: 8-4-4-4-12 lowercase hex, with the UUID v4 version and variant digits called out.
How does a UETR work?
What it looks like, where your bank stores it, how it travels with the transfer, and how to recognise a fake.
01/ What a UETR looks like
A UETR is 36 characters total: 32 letters and numbers (using only 0-9 and a-f, all lowercase) plus 4 hyphens that split it into five groups in the pattern 8-4-4-4-12. The third group always starts with the digit 4. The fourth group always starts with 8, 9, a, or b.
Technically it is a UUID version 4, a standard random-identifier format (defined in IETF RFC 4122) used across software. Your bank generates the UETR automatically when you send the transfer; you do not choose it.
02/ Where the UETR sits in the bank's document
On an MT103-format advice, the UETR appears in field 121 of Block 3, the user header. It may be printed as {121:6f8d3a2b-1c44-4f8e-9b21-7d2c9f0a1b22}. On a pacs.008-format document, look inside PaymentIdentification for the UETR element. Its compact ISO 20022 path is CdtTrfTxInf > PmtId > UETR.
In November 2025 the CBPR+ coexistence period for cross-border payment instructions between financial institutions ended. Banks now exchange the ISO 20022 pacs.008 instruction for that leg. A bank may still issue an MT103-format customer confirmation. The UETR value is unchanged between the two layouts. More about MT103 here.
03/ How the UETR travels
When your bank sends the transfer, every bank in the chain, that is the sending bank, any go-between banks, and the beneficiary's bank, is required to keep the UETR unchanged. The banks that report also file a quick status update against that UETR back to the SWIFT network: "I have it", "I passed it on", "It has been credited".
This is what makes the UETR end-to-end: it identifies the same payment from the moment your bank creates it until the money arrives. See what each status update means →
04/ How to recognise a fake or wrong UETR
If a "UETR" you have been given is not exactly 36 characters (or the same 32 hexadecimal digits without hyphens, which is the compact form some banks print), contains letters outside a-f, or the third group does not start with 4, it is not a valid UETR. Capital letters are the same reference written in uppercase: the canonical form is lowercase, and uetr.ai lowercases them before checking.
A common confusion: some banks share an internal transaction reference (often called the "customer reference" or just "transaction ID") that looks short and simple. That is not the UETR. If your reference does not pass the validator above, ask your bank for the UETR from their SWIFT gpi tracker.
The same UETR stays with the payment from the first bank to the last, and the banks that report file their status against it to the SWIFT gpi Tracker.
Where do I find my UETR number?
Your bank generates the UETR when it sends the transfer. Where you see it depends on which bank you are with and whether you use retail or business banking.
Look on the transfer confirmation
When your bank confirms an outgoing transfer, look for a line labelled 'UETR', 'End-to-end ID', or 'gpi reference'. On an MT103-format advice it is field 121. On a pacs.008-format document it is the UETR element inside PmtId.
Check your business banking portal
If you bank through a business or treasury portal, for example HSBCnet, CitiDirect, J.P. Morgan Access, Deutsche Bank Autobahn, BNY Mellon NEXEN, Santander Cash Nexus, or Standard Chartered Straight2Bank, the UETR is in the payment-status detail page. Each portal calls it something slightly different.
Simply ask your bank
If you bank online as a regular customer, the UETR is often not shown. Send a secure message or call the branch and ask for 'the UETR for my SWIFT transfer sent on [date]'. They can retrieve it from their internal SWIFT gpi tracker in seconds.
Check it at uetr.ai, then leave the monitor running
Enter the 36-character UETR in the form at uetr.ai with the amount, currency and payment date. It is free, with no account and no bank login. uetr.ai checks multiple international banks on the SWIFT network for that reference, not only the sending bank. While the transfer is in progress, free tracking re-checks every 24 hours for up to 30 days from submission. Emails follow further payment stages, at most once a day.
Find your UETR by bank
Bank-specific guides covering where the UETR appears in each major bank's customer portal.
FAQ
Frequently asked questions about UETR numbers
What is a UETR number?
A UETR number is a 36-character UUID v4 identifier that SWIFT has required on every customer credit transfer routed over the FIN network since 18 November 2018. It is generated by the sending bank's payment system and preserved across every correspondent and intermediary bank in the chain. On an MT103-format advice it is field 121; in pacs.008 it is the UETR element inside CdtTrfTxInf/PmtId.
What does UETR mean?
UETR means Unique End-to-end Transaction Reference. It is the 36-character code SWIFT has required on every international payment since 18 November 2018. The sending bank generates it, and it stays unchanged as the payment moves between banks, so any bank in the chain can identify and report on that exact transfer.
What does UETR stand for?
UETR stands for Unique End-to-end Transaction Reference. The 'end-to-end' part is what makes it useful. The same UETR identifies the payment from the moment the sending bank creates it until the beneficiary bank credits the funds, even across multiple correspondent banks.
What is a UETR code?
A UETR code is the same thing as a UETR number or a UETR reference: banks use the three labels interchangeably for one identifier, the 36-character Unique End-to-end Transaction Reference. It is 32 hexadecimal characters plus 4 hyphens in the pattern 8-4-4-4-12, for example 6f8d3a2b-1c44-4f8e-9b21-7d2c9f0a1b22; the canonical form is lowercase, a copy in capitals is the same reference, and the same 32 digits printed without hyphens are the UETR in compact form. There is no separate 'code' with a different format.
What is a UETR number in banking?
In banking, a UETR number is the tracking identifier SWIFT uses to follow a payment across the correspondent chain. It is mandatory on the FIN payment messages that carry it since 18 November 2018: the MT103 customer credit transfer, and the MT202, MT202COV, MT205 and MT205COV financial-institution transfers. The banks that report send a status update to the SWIFT gpi Tracker, keyed against the UETR.
What is UETR in SWIFT?
In SWIFT, the UETR is the unique reference that lets banks and customers trace a payment across the correspondent chain. It is carried in field 121 of the SWIFT MT user header (Block 3) and in the UETR element inside CdtTrfTxInf/PmtId of an ISO 20022 pacs.008 message. The SWIFT gpi Tracker uses the UETR as its primary key.
What does a UETR number look like?
A UETR looks like 6f8d3a2b-1c44-4f8e-9b21-7d2c9f0a1b22. It is 32 lowercase hexadecimal digits split into 5 groups of 8-4-4-4-12 by hyphens. The third group always starts with the digit 4 (the UUID version), and the fourth group starts with 8, 9, a, or b (the UUID variant). The canonical form is lowercase; a copy written in capitals is the same reference, and uetr.ai lowercases it before checking.
How long is a UETR number?
Exactly 36 characters: 32 hexadecimal digits and 4 hyphens. There is no other punctuation. If your bank shows you the same 32 digits without the hyphens, or split by spaces into groups, that is the UETR in compact form; uetr.ai removes formatting spaces and restores the hyphens; anything shorter, or with letters outside a-f, is not a UETR.
How many digits is a UETR number?
A UETR has 32 hexadecimal digits (0-9 and a-f) plus 4 hyphens, for a total of 36 characters. The digits-only count is 32.
Is the UETR the same as the MT103?
No. The MT103 is the legacy SWIFT FIN format for a customer credit transfer, while the UETR is the 36-character identifier that follows the payment. An MT103-format advice carries it in field 121. The current CBPR+ pacs.008 instruction carries the same UETR inside CdtTrfTxInf/PmtId. See our MT103 and pacs.008 guides for the full breakdown.
Is the UETR the same as a SWIFT code (BIC)?
No. A SWIFT code (also called a BIC) is an 8- or 11-character ISO 9362 identifier for a financial institution, for example CHASUS33. A UETR is a 36-character identifier for a single payment. One identifies a bank; the other identifies a transaction.
What is a UETR reference number?
'UETR reference number' is just a longer way of saying UETR. Some banks and corporate banking portals call it the 'end-to-end reference', the 'gpi reference', or the 'tracking reference'. All of those refer to the same 36-character identifier.
Where can I find my UETR number?
Your UETR appears on the payment confirmation your sending bank issues. On an MT103-format advice it is field 121. On a pacs.008-format document it is the UETR element inside PmtId. In corporate banking portals it may be shown as 'UETR', 'End-to-end ID', or 'gpi reference'. If it is not shown, ask your bank to retrieve the UETR.
What is the UETR number in MT103?
In an MT103 message, the UETR sits in field 121 of the user header (Block 3). On a printed MT103 advice you will see it as '{121:6f8d3a2b-1c44-4f8e-9b21-7d2c9f0a1b22}'. Field 121 was introduced in 2017 for SWIFT gpi and made mandatory for all FIN customer credit transfers from 18 November 2018.
Is UETR mandatory?
Yes. SWIFT made UETR mandatory for all FIN customer credit transfer messages (MT103, MT202, MT202COV, MT205, MT205COV) from 18 November 2018. Payments without a valid UETR are rejected (NAK) by the SWIFT network.
How do I track a UETR number?
Enter the UETR into uetr.ai to check public SWIFT gpi trackers. The tracker returns status events (ACSP for in transit, ACSC for settlement completed, ACCC for credited to the beneficiary account, PDNG for pending review, RJCT for rejected) tied to that UETR from the banks that reported. Your sending bank's own gpi viewer is the official source.
How do I check a UETR status?
Copy the 36-character UETR from your payment confirmation. On an MT103-format advice it is field 121. On a pacs.008-format document it is the UETR element inside PmtId. Paste it into the tracker at uetr.ai and read the latest SWIFT gpi status event: ACSP means in transit, ACSC means settled, ACCC means credited, and RJCT means rejected. Every UETR check at uetr.ai is free. While the transfer is still in progress, uetr.ai re-checks it once every 24 hours for up to 30 days and emails you when the payment reaches a further stage; paid plans re-check it every few minutes instead.
How is a UETR generated?
The UETR is generated by the sending bank's payment system at the moment the payment instruction is created. It is a UUID v4, a random identifier, produced according to RFC 4122. Customers do not generate UETRs themselves; if you do not have one, ask your sending bank to provide it from their gpi viewer.
Do SEPA payments have a UETR?
Standard SEPA Credit Transfer (SCT) and SEPA Instant payments use a domestic end-to-end identifier (the EndToEndId), not a SWIFT UETR. Cross-border euro payments routed through SWIFT correspondent banking, outside the SEPA scheme, will carry a UETR.
Is the UETR the same as a SWIFT tracking number?
Yes. 'SWIFT tracking number', 'wire tracking number', 'gpi reference', and 'end-to-end reference' are all informal names for the UETR, the 36-character code SWIFT uses to track a payment across banks. There is no separate SWIFT tracking number to ask for: ask the sending bank for the UETR.
How do I verify a UETR is valid?
Check the format first. A valid UETR is exactly 36 characters: 32 lowercase hexadecimal digits (0-9 and a-f) in 8-4-4-4-12 groups separated by hyphens, with the digit 4 starting the third group and 8, 9, a, or b starting the fourth, for example 6f8d3a2b-1c44-4f8e-9b21-7d2c9f0a1b22. Anything with characters beyond a-f, or a different count of hexadecimal digits, is not a UETR, with one exception: the same 32 digits printed without hyphens, or split by spaces into groups, are the UETR in compact form, and uetr.ai removes formatting spaces and restores the hyphens before checking. Capital letters are the same reference written in uppercase; uetr.ai lowercases them before checking. Pasting it into uetr.ai validates the format and then checks public trackers; a correctly formatted UETR that returns nothing usually means no public tracker data is available yet, not that the code is wrong.
Can anyone use UETR tracking to look up someone else's payment?
Only if they already hold that payment's UETR. The UETR is not public or guessable: it is a random 36-character UUID v4 generated by the sending bank, so there is no directory that lets you find a transfer by name, account number, or amount. uetr.ai reads only public SWIFT gpi tracker data for the exact UETR you paste, shows no personal account details, and never moves or accesses funds. In practice the sender, the beneficiary, and the banks in the chain are the parties who have the UETR.
Related guides
What to do with the UETR once you have it, and the concepts around it.
What is pacs.008?
The ISO 20022 successor of the MT103, and where the UETR sits inside it.
How to track a SWIFT payment
The step-by-step guide: find the UETR, run a free check, and read the result.
Track an international wire transfer
Every way to follow a cross-border wire, from bank portals to the UETR itself.
What is MT103?
The legacy SWIFT FIN format, and where field 121 carries the UETR.
SWIFT status codes
ACSP, ACSC, ACCC, PDNG, RJCT: what each status means and whether to wait or act.
How long does an international wire take?
Realistic timelines by scenario, and what to do when a transfer runs late.
ACH vs wire transfer
Why only an international SWIFT wire carries a UETR you can track.
Regulatory Disclosure
uetr.ai is an independent information service. We are strictly a read-only payment-monitoring tool. We never hold, move, custody, send, or process money. We are not a money transmitter or payment processor. Always consult your sending bank for the official record of any bank transfer.