Last reviewed: · Curated by Ohmyfin Organisation editorial.
Every SWIFT rejection (status RJCT) carries an ISO 20022 ExternalReturnReason code: AC01 (wrong account), AC04 (closed account), AC06 (blocked), BE01 (name mismatch), BE05 (originator unknown), CH09 (charges issue), FF01 (format error), RR01–04 (missing data), RR04 (regulatory), and ~20 others. Look up the code at /reject-codes for an explanation and fix.
Step-by-step:
1. Get the reason code from your bank or from the pacs.002 / MT103-STP rejection message.
2. Look up the code at /reject-codes/{code} on Ohmyfin for plain-English meaning and fix.
3. Fix the underlying issue (e.g. correct the IBAN for AC01, get a new account for AC04, add purpose code for FF07).
4. Re-issue the payment with a NEW UETR — never reuse the rejected UETR (triggers AM05 Duplication).
5. Track the new UETR on Ohmyfin to confirm successful settlement.
Quick facts:
Every SWIFT rejection (status RJCT) carries an ISO 20022 ExternalReturnReason code: AC01 (wrong account), AC04 (closed account), AC06 (blocked), BE01 (name mismatch), BE05 (originator unknown), CH09 (charges issue), FF01 (format error), RR01–04 (missing data), RR04 (regulatory), and ~20 others. Look up the code at /reject-codes for an explanation and fix.
Yes. Public UETR tracking on Ohmyfin is free, with 10 free scans per IP per day for individuals worldwide and 100 free credits when you sign up.
No. Ohmyfin looks up the SWIFT payment status with just the UETR — no bank login or account required.
No card needed. Free for ordinary users — 5 IP-based lookups per day, plus 100 credits instantly when you sign up with email. Use them on any international wire across 11,000+ banks.
Sign up free — get 100 credits Or try the tracker now →