Real vs fake payment
How to tell a genuine SWIFT payment from a forged confirmation
After years on a correspondent banking desk, one lesson stands out: the document is never the evidence. A forged MT103 or SWIFT copy can carry perfect formatting, the right logos and a correctly shaped reference — and still describe a payment that was never sent. The only proof is the transaction itself, and the UETR is the thread that leads to it.
The five signs a payment copy is fake
01The reference returns nothing
You paste the UETR and no institution anywhere holds a record — yet the sender insists the funds left days ago. A genuine payment appears on the network within minutes and is never purged. Silence is the loudest alarm there is.
02The amounts do not match
The paper copy says one figure; the network says another. Fraudsters lift a real reference from an unrelated payment and hope you never compare the amount or currency.
03The parties do not match
The beneficiary name or bank on the document differs from the ones actually carrying the reference. A borrowed reference always betrays its real owner.
04The value date is in the past, with no trace
The document claims the payment was valued weeks ago, but no institution has ever reported it. Time does not erase real payments — it only exposes invented ones.
05Pressure arrives with every new 'copy'
Each message brings a fresh confirmation and a fresh reason you should release goods or funds before the credit lands. Urgency plus paperwork is the oldest trick on a trade desk.
Real payment vs fake confirmation, side by side
| Check | Real payment | Fake confirmation |
|---|---|---|
| UETR on the network | A transaction under the exact reference exists and is visible within minutes of sending. | No record anywhere, or a record belonging to a different payment entirely. |
| Amount and currency | Identical on the document and on the network record. | Document inflates the figure; the network shows the true, usually smaller, one. |
| Sender and beneficiary banks | The institutions on the copy are the ones reporting against the reference. | The copy names banks that have never touched the reference. |
| Event history | A chain of status updates builds as the payment moves between institutions. | A static 'copy' is offered instead of a traceable history. |
| Behaviour of the sender | Comfortable with you verifying; the reference survives scrutiny. | Pushes urgency, supplies new documents, discourages independent checks. |
Check the reference before you act on the paper
Paste the UETR from the document into the tracker. A verified result shows the live status, amounts and event history — anything short of that is a reason to stop, not to ship.
Verify a UETR nowFrequently asked questions
Can a fake SWIFT copy pass a visual inspection?
Yes. Modern forgeries reproduce layouts, logos, reference formats and even plausible bank officer signatures. Visual inspection proves nothing — only the existence of a matching transaction on the network proves the payment.
Why can't fraudsters just invent a UETR?
They can invent the format — 36 characters is easy to type. What they cannot do is create the transaction behind it. A UETR is only a label; verification checks the payment the label is attached to.
The UETR exists but the details differ. Is it real?
No. A reference borrowed from an unrelated genuine payment is still a fake confirmation. The amounts, currency, and sending and receiving institutions must match the document exactly.
What should I do if a payment turns out to be fake?
Do not release goods or funds, keep every document and message, and report it to your bank's fraud team. If goods or money have already moved, involve your bank and the relevant authorities immediately.
New to UETRs? Read how UETR verification works or look up the sending institution in the bank directory.