A bank wire confirmation typically contains four or five different reference numbers. Each one means something different, serves a different purpose, and is useful to a different party. Knowing which number to use for tracking — and which to ignore — saves hours of frustration.
The most important number: the UETR. This is the 36-character UUID in the format 8-4-4-4-12 hexadecimal digits with hyphens (example: 3c4de12a-7f9e-4b01-9d3a-1a2b3c4d5e6f). The UETR is the only identifier that tracks the payment end-to-end across the entire SWIFT network, through every correspondent bank. It appears on bank confirmations as "GPI reference", "Unique end-to-end reference", "tracking ID", or "field 121 UETR". This is what you enter on Ohmyfin.
The sender's reference (TRN / field 20): this is typically a shorter alphanumeric code — 8 to 16 characters — that the originating bank assigns for their own internal records. On a wire confirmation, it may be labelled "Payment reference", "Transaction reference", "Reference number", or "Debit reference". It is useful for chasing the payment within the sender bank but cannot be used for GPI tracking. Example format: REF20260522A01.
The bank's internal transaction ID: many banks also stamp a proprietary internal ID on the confirmation — typically a purely numeric string like 78342156201. This is the bank's core-banking record ID and is only meaningful to that bank's agents. It is not a SWIFT reference and cannot be used externally.
The IBAN and BIC: these are not tracking numbers — they are destination identifiers. The IBAN identifies the beneficiary's account; the BIC identifies the bank routing target. Both appear on the confirmation for record-keeping but do not change after the payment is sent.
The value date: on the confirmation, the value date is when the funds are expected to settle. It is not a reference number but a date — typically shown as DD/MM/YYYY or YYMMDD in SWIFT field 32A format (e.g. 260701 = 1 July 2026).
How to find the UETR if it is not on the confirmation: (a) Log in to online banking and view the transaction detail — most banks show the UETR there even if they omit it from the PDF confirmation. (b) Call the international payments desk and ask for "the UETR in field 121 of the MT103". (c) Ask the recipient — the beneficiary bank can see the UETR on the incoming message even if the sender did not share it.
When does a confirmation number indicate fraud? A "confirmation number" received from a third party (not your own bank) that is not a real UETR should be treated with extreme suspicion. SWIFT confirmation PDFs are trivially easy to forge. The only way to verify a UETR is to paste it on Ohmyfin — if it does not return any GPI data from a legitimate bank, treat the document as potentially fraudulent.
No. A 16-character alphanumeric reference is the sender's TRN (field 20). A UETR is always exactly 36 characters with four hyphens. Ask your bank to provide the "UETR in MT103 field 121".
Many banks do not print the UETR on the confirmation PDF, even though it always exists in their system. This is a gap in bank UX. The UETR is always available in the online banking transaction detail or by calling the international payments desk.
This is a major red flag. A UETR that returns no GPI data either belongs to a non-GPI bank (rare for major senders), is fabricated, or has been typed incorrectly. Ask for the original confirmation directly from the sending bank — not from the third party.
Not on GPI-based trackers like Ohmyfin. However, your own sender bank can look up the UETR by TRN instantly — ask them to do the mapping and give you the UETR.