LOCATE THE ORIGINAL REFERENCE

Find Your UETR Number: Bank Portals, MT103 and pacs.008

You need the reference attached to your payment—not a new code that happens to have the right shape.

Sources checked 22 October 2026 · Editorial policy

Start with the individual payment

Sign in through your bank’s usual app or website. Open the specific outgoing payment and look for its details, confirmation or downloadable advice. Labels vary: the reference may be described as UETR, tracking reference or Unique End-to-end Transaction Reference.

Do not assume the first number on the page is the UETR. An order ID, receipt number and bank reference can appear alongside it. Match the date, currency and beneficiary before copying anything. Some banks expose the reference only in a document or through support.

Search the original confirmation

In a searchable PDF, look for “UETR” or “121”. Copy the full value, including its hyphens, and compare it with the displayed text. Copying from a scanned image can turn a zero into a letter or introduce spaces.

If the receipt contains only a local payment ID, keep that ID for the bank enquiry. Not every payment uses Swift, and a customer-facing receipt does not necessarily show an interbank reference. Read what a confirmation establishes before treating it as evidence of receipt.

In an MT103, look in block 3

On a raw MT103 copy, the UETR is carried in field 121 in the user-header block. An illustrative fragment is {3:{121:3f2a91c7-5b4e-4d18-9c6f-2ae70b8d1f43}}. The braces and field label are not part of the reference.

Field 20 is the sender’s reference and serves a different purpose. A formatted bank advice may print the UETR elsewhere instead of showing raw blocks. Use the MT103 field guide for the rest of the message.

In pacs.008, find payment identification

Look for the UETR element inside the transaction’s payment-identification block: CdtTrfTxInf / PmtId / UETR. Namespace prefixes and document wrappers may differ. The neighbouring EndToEndId and InstrId elements are separate references.

Ask for the element associated with your transaction, not the message’s overall ID. Swift’s ISO 20022 message-mapping material illustrates these identifiers. Our pacs.008 guide explains the surrounding structure.

When the reference is not visible

Ask the sender or sending bank: “Please provide the original UETR for this payment, together with its message date. My bank payment reference is [reference].” Supply account information only through the bank’s secure channel.

Do not replace a missing reference with a generated UUID. A format check can identify some copying errors, but cannot determine whether the value belongs to your payment. Keep the original document and message date with the copied value. For definitions rather than document locations, see the reference glossary.

A USEFUL NEXT STEP

Find the right record or explanation

Track your transaction

Transaction tracking

Find your record and get an email when a new status is recorded.

The 36-character reference on your generated message. Confirm your email to receive recorded transaction updates. Amount and currency come from your transaction.

No bank login. Public lookup excludes personal account details. Eligible verified participants can access full details.