MT103 (SWIFT Customer Credit Transfer)
MT103 is the SWIFT message type for a single customer credit transfer between two banks. It is the format used for almost every traditional cross-border wire transfer initiated by an individual or corporate customer. Draft a valid MT103 now → · Verify an MT103 UETR free →
Details
An MT103 is structured into five blocks. Block 1 (basic header) and Block 2 (application header) identify the sender and receiver bank and message type. Block 3 (user header) contains the UETR in field 121 — the globally unique tracking ID that travels unchanged through every correspondent bank. Block 4 (text block) contains the payment data. Block 5 (trailer) is the authentication and checksum.
The most important fields in Block 4 are: field 20 (sender's reference / TRN — up to 16 chars), field 23B (bank operation code — typically CRED), field 32A (value date, currency, amount), field 50A/F/K (ordering customer — the sender), field 52A (ordering institution — sender's bank), field 53A/B (sender's correspondent), field 56A (intermediary bank), field 57A (account with institution — beneficiary bank), field 59 (beneficiary — account number and name), field 70 (remittance information — up to 4×35 chars), field 71A (charges bearer: OUR, SHA or BEN), and field 121 (UETR). Full reference at /swift-fields.
The MT103 is gradually being replaced by ISO 20022 pacs.008 as part of the SWIFT global MT/MX migration, with the coexistence period ending November 2025. After that date, customer credit transfers on the SWIFT network must be sent natively as pacs.008. For now, both formats coexist on the network and carry the same UETR — Ohmyfin tracks both interchangeably.
Receiving an MT103 PDF from a counter-party is not by itself proof of payment. MT103 documents are routinely forged by scammers as "proof" that a payment has been sent. The only reliable verification is to look up the UETR (field 121) on a live SWIFT GPI tracker like Ohmyfin, or to wait for your bank to confirm the incoming credit. If an MT103 PDF's UETR cannot be found, the document is almost certainly fraudulent.
MT103 STP (Straight-Through Processing) is a variant where the payment contains all the information needed for automatic processing at every bank without manual intervention. STP-eligible payments typically clear faster and have lower correspondent fees. To qualify for STP your MT103 must have complete, correctly formatted beneficiary data, a full BIC in field 57A, and no missing mandatory fields.
For commonly delayed or rejected MT103 payments, the main reasons are: (1) missing or incorrect BIC in field 57A — the correspondent cannot route the payment; (2) incomplete beneficiary name/address in field 59 — fails sanctions screening; (3) unclear purpose in field 70 — compliance hold; (4) wrong charges code in field 71A — amount arrives short. See /compare/mt103-vs-pacs008 for how the ISO 20022 successor solves these data quality problems.
Key facts
- SWIFT message type for one-off customer credit transfers
- Five blocks: basic header / application header / user header / text / trailer
- Key fields: 20 (TRN), 32A (value/currency/amount), 50 (sender), 57A (beneficiary bank), 59 (beneficiary), 71A (charges), 121 (UETR)
- UETR in field 121 — the mandatory GPI tracking ID (since Nov 2018)
- Being replaced by ISO 20022 pacs.008 — coexistence ends Nov 2025
- MT103 PDFs can be forged — always verify the UETR on Ohmyfin
Frequently asked questions
How can I tell if an MT103 is real?
Verify the UETR (field 121) on Ohmyfin at ohmyfin.org. If Ohmyfin cannot locate the UETR in the SWIFT network, treat the document as fraudulent and do not release goods or services. A genuine MT103 will always return a real-time SWIFT GPI status.
How long does an MT103 take?
On SWIFT GPI, most MT103 payments settle within minutes to a few hours for major corridors. Sanctions screening holds, missing beneficiary data, cut-off time misses and public holidays can extend it to 1–3 business days. See /how-long for corridor-specific timing guides.
What are the mandatory fields on an MT103?
Mandatory fields are: 20 (sender reference), 23B (bank operation code), 32A (value date / currency / amount), 50A/F/K (ordering customer), 59 (beneficiary account and name), 71A (charges bearer), and 121 (UETR). Fields 52A through 57A for bank routing are conditional-mandatory depending on the routing chain.
Can an MT103 be recalled after it has been sent?
Yes — a bank can send an MT192 cancellation request, but once funds have been credited to the beneficiary's account the beneficiary bank must consent to return them. On SWIFT GPI there is also a Stop-and-Recall feature. Recalls are not guaranteed to succeed and typically take 1–10 business days.
What is the MT103 STP variant?
MT103 STP (Straight-Through Processing) is a subset of MT103 with stricter formatting rules so the payment can be processed automatically at every correspondent bank without human intervention. STP payments clear faster and are cheaper. To qualify, every field must be correctly formatted with a full BIC in field 57A and complete, unambiguous beneficiary data.
Related guides
Related — more from payments glossary and beyond
Get 100 free credits — track unlimited SWIFT payments
No card needed. Free for ordinary users — 10 free trackings per day per IP, no signup required. Track any international wire across 11,000+ banks.
Track a payment now — completely free Or try the tracker now →