Last reviewed: · Curated by Ohmyfin Organisation editorial.
Need to verify a SWIFT reference? Ohmyfin checks the SWIFT correspondent banking network for any reference type — UETR (field 121), sender reference (field 20), or ISO 20022 EndToEndId.
How it works — 3 steps
Step 1 · PasteDrop your UETR, MT103 reference or pacs.008 EndToEndId into the form above.
Step 2 · ScanOhmyfin queries the SWIFT correspondent network and decodes the latest status in 2-6 seconds.
Step 3 · ReadSee the plain-English status, every correspondent bank, value date, currency and per-hop fees.
What you get
Universal lookup — UETR, MT103 field 20, EndToEndId
Detects forged or fake SWIFT confirmations
Free for the first 10 searches per day
No account required
At-a-glance
SWIFT Reference Tracker — at-a-glance specifications
Tracker type
Universal SWIFT reference
Inputs accepted
UETR, field 20, EndToEndId
Forgery detection
Yes — flags absent payments
Speed
2-6 seconds
Price for individuals
Free worldwide
Frequently asked questions
How is this different from the UETR tracker?
The SWIFT reference tracker is a superset — it accepts UETRs and any other identifier your bank gave you.
Does Ohmyfin store my reference?
Yes, briefly — verified results are cached for one year so repeat lookups are instant. We never share references with third parties.
Can I bulk-check references?
Individuals are capped at 15 lookups/day. For bulk or programmatic access, financial-institution customers can request our paid API at /for-banks.
What if the reference contains spaces or dashes?
Ohmyfin strips whitespace and dashes automatically before matching, so pasting a formatted UETR or grouped reference still works.
Are SWIFT-style references case-sensitive?
UETRs are hexadecimal and case-insensitive. Bank references are usually case-insensitive too, but Ohmyfin tries both forms to maximise the chance of a match.