Why this tracker exists
Over years on a correspondent banking desk you see the same scene again and again: a counterparty produces a crisp SWIFT copy, the amount is right, the letterhead is right, and the funds never arrive. Verifying it meant a different bank portal for every route, credentials nobody outside the bank has, and a phone call to an operations team in another timezone. There was no single, neutral place to take one reference and ask a simple question — does this payment exist?
That is all this site does. It takes the one field on a payment document that cannot be forged in a PDF editor — the UETR — sweeps it across the networks a real payment must touch, and tells you plainly what came back. It is independent of every institution it queries, keeps no record of what you type, and exists so that a fabricated confirmation stops costing people their goods.
How to track a UETR in three steps
- 01
Paste the reference
Take the 36-character UETR straight off the SWIFT copy, MT103 or payment confirmation you were handed.
- 02
We sweep everywhere
One submission is checked across the settlement network, the correspondent banks on the route and the independent reference registries.
- 03
Decide with evidence
You get a plain verdict, the full status, amounts and the movement history — enough to tell a real payment from a convincing forgery.
Five signs the payment copy is fake
The reference returns nothing at all, yet the sender insists the funds left days ago.
The amount or currency on the paper copy does not match the amount on the network.
The beneficiary name or bank on the copy differs from the one carrying the reference.
The value date on the document is in the past but no institution has ever reported the payment.
The sender pressures you to release goods before the credit lands, offering a fresh 'copy' each time.
Read the full real vs fake payment guide with a side-by-side comparison, or learn how UETR verification works.
Frequently asked questions
What is a UETR?
The Unique End-to-end Transaction Reference is a 36-character UUID attached to every SWIFT payment at the moment it is created. Every institution that touches the payment reports against that same reference, which is why it is the only field on a payment copy that cannot be quietly edited in a PDF.
How does this tell me a SWIFT copy is fake?
A genuine payment exists on the network within minutes of being sent. If the reference on the document returns no record at all, or returns amounts and parties that differ from the paper, the document does not describe a real transfer.
Where does the tracker check?
Everywhere a reference can legitimately surface: the settlement and messaging layer that carries SWIFT instructions, the correspondent banks along the route, and the independent registries that log end-to-end references. You paste once and the whole sweep runs.
Is this UETR tracker free?
Yes. No account, no sign-up, no charge. Your lookup history is kept in your own browser and never on our servers.
Why was this built?
Because after years of reading SWIFT copies across a correspondent banking desk, there was still no single place to confirm one reference. Every check meant a different portal, a different login, and a phone call. This is that single place.