MT103: the customer credit transfer
The MT103 carries one customer credit transfer between banks — who pays, who gets paid, how much, and who bears the charges along the way.
L0 Explain simply
An everyday analogy: an MT103 is the banking world's version of a fully filled-in international money transfer form. One form, one payment, one customer being paid. The form has a box for who is sending the money, a box for who should receive it, a box for the amount and the day it is due, and a box answering the awkward question every international delivery raises: who pays the shipping? The form itself is not the money — it is the instruction that makes banks move the money across the accounts they keep with each other. When something goes wrong weeks later, investigators pull out this form first, because every detail of the payment was fixed the moment it was written.
L1 Core concepts
The MT103 is the single customer credit transfer: the MT message one bank sends another to execute one customer payment. It names the ordering customer (the payer) and the beneficiary, and carries the value date, currency, and settlement amount, the payment reference, and a charge option that decides who bears the banks' fees — the sender, the beneficiary, or both sides sharing. The MT103 travels between banks; the customer never sees it directly. Depending on routing, the same MT103 may pass through one or more intermediary banks (serial routing) or go straight to the beneficiary's bank while the money moves separately (cover routing). At each hop, the banks involved settle across the correspondent accounts they hold with one another.
L2 Practitioner view
Operationally, the MT103 is where most cross-border investigation work starts. Field 20, the sender's reference, is the handle a case is opened under, and every later message about the payment should quote it. The charge option matters commercially: OUR means the sender pays the charges, SHA splits them, BEN lets them be deducted from the beneficiary's amount — a frequent cause of "short payment" complaints. Beneficiary details that fail validation at the receiving bank trigger repairs or returns, and how a return travels back varies by market and bilateral practice. Names, addresses, and free-text fields are exactly what sanctions screening engines parse, so a poorly structured ordering-customer field can put an otherwise clean payment into a review queue. Cut-off times at each bank decide whether the stated value date can actually be met.
L3 Technical details
The MT103's business content sits in block 4. :20: sender's reference. :23B: bank operation code, normally CRED for an ordinary credit transfer. :32A: value date (YYMMDD), currency, and interbank settled amount; :33B: the originally instructed currency and amount when different. :50a: ordering customer — option K gives account plus name and address lines, option F structured party details, option A an account and BIC. :52a: ordering institution, :56a: intermediary institution, :57a: account with institution (the beneficiary's bank). :59a: beneficiary, account on the first line. :70: remittance information passed to the beneficiary. :71A: details of charges: OUR, SHA, or BEN. :72: bank-to-bank instructions. In block 3, field 121 carries the UETR used for end-to-end tracking across the chain.
L4 Standards & sources
The governing source is the SWIFT Standards MT documentation for Category 1 (customer payments and cheques), which defines the MT103 field by field: which fields are mandatory, the exact formats and option letters, and the network-validated rules FIN enforces before a message is delivered. That documentation is the authority when a dispute turns on what a field may contain; it is published on swift.com and requires a SWIFT user account, which is why public explanations — including this one — are summaries rather than reproductions. Note also that cross-border payment instructions have been migrating from MT to ISO 20022, with pacs.008 as the MT103's successor, so confirm against current SWIFT guidance which standard applies on the route and market you are studying before relying on MT-era detail.
Sources & standards1
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · Category 1 — MT103 Single Customer Credit Transfer
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login; content here relies on public summaries. Swift ended MT-to-ISO 20022 coexistence for in-scope cross-border payment instructions (for example MT103 and MT202) in November 2025; MT statement messages are being phased out on a separate timeline.
SEE THE PAYMENT MOVE
Read the steps as text
- 02ProcessingBank Alfa validates and screensBank Alfa (ordering bank)
Format and balance checks plus sanctions screening. Cross-border payments face stricter screening because more jurisdictions are involved.
Screening checkpoint: Outbound cross-border screening — Ordering and beneficiary parties, banks, and remittance text are screened before the payment leaves.
- 03PostingThe customer's account is debitedBank Alfa (ordering bank)
Bank Alfa books the debit and, per the charge option, any fees.
- DR Ordering customer's account at Bank Alfa — USD 250,000.00
- 05ProcessingMeridian validates and screens in the middleMeridian Bank (correspondent)
Every bank in the chain screens independently. Meridian also checks that Bank Alfa's account has cover for the debit.
- 06SettlementMoney moves across the books of MeridianMeridian Bank (correspondent)
Both Bank Alfa and Cassia hold USD accounts at Meridian. Settlement here is a book transfer in commercial bank money: Meridian debits one account it holds and credits the other.
No clearing house is involved — the correspondent's ledger is the settlement venue. This is settlement in commercial bank money, not central bank money.
- DR Bank Alfa's USD account at Meridian (vostro) — USD 250,000.00
- CR Cassia's USD account at Meridian (vostro) — USD 250,000.00
- 09ProcessingCassia validates the incoming paymentCassia Bank (beneficiary bank)
Account checks and inbound screening. Only when funds are confirmed on the nostro and checks pass is the beneficiary credited.
- 10PostingThe beneficiary is creditedCassia Bank (beneficiary bank)
Cassia credits its customer, net of any beneficiary-side charges the charge option allows.
- CR Beneficiary's account at Cassia — USD 250,000.00
Read the steps as text
- 02ProcessingGanga Bank checks the declaration before touching the moneyGanga Bank (Indian AD Category-I bank)
As the Authorized Dealer, Ganga Bank is responsible for the declaration it accepts: it checks the purpose code is valid and permitted, confirms the remittance (with the remitter's other transfers this financial year) stays within the Liberalised Remittance Scheme's annual per-person limit, and screens the remitter and beneficiary before any conversion happens.
Screening checkpoint: Outbound remittance screening — Remitter and beneficiary names are screened before Ganga Bank converts or sends anything — the cheapest point to stop a problem.
- 03PostingGanga Bank converts the rupees to dollarsGanga Bank (Indian AD Category-I bank)
Ganga Bank debits the remitter's INR account and converts the proceeds to USD at its own card rate — the rate it offers retail customers, which includes its margin over the interbank rate. The converted USD amount is what actually gets remitted; the INR amount debited is what the remitter pays for it.
- DR Remitter's savings account at Ganga Bank — INR 3,34,000.00
- 05ProcessingLiberty Union validates and screens in the middleLiberty Union Bank (US correspondent)
Every bank in the chain screens independently. Liberty Union also checks that Ganga Bank's nostro account has cover for the debit.
- 06SettlementMoney moves across the books of Liberty UnionLiberty Union Bank (US correspondent)
Both Ganga Bank and Cascade Bank hold USD accounts at Liberty Union. Settlement here is a book transfer in commercial bank money — Liberty Union debits one vostro account it holds and credits the other.
No clearing house is involved — the correspondent's ledger is the settlement venue, in commercial bank money, not central bank money.
- DR Ganga Bank's USD account at Liberty Union (vostro) — USD 4,000.00
- CR Cascade Bank's USD account at Liberty Union (vostro) — USD 4,000.00
- 08ProcessingCascade Bank validates the incoming paymentCascade Bank (beneficiary's US bank)
Account checks and inbound OFAC screening on every incoming international wire. Only when the account is confirmed and checks pass is the beneficiary credited.
- 09PostingThe beneficiary is creditedCascade Bank (beneficiary's US bank)
Cascade Bank credits its customer. The remitter's friend now has USD 4,000.00 — converted from INR 3,34,000.00 at Ganga Bank, minus whatever margin and fees applied along the way.
- CR Beneficiary's account at Cascade Bank — USD 4,000.00
Read the steps as text
- 02ProcessingBank Alfa validates the MT101Bank Alfa (ordering bank)
The bank checks the mandate, message fields, funds, cut-off, routing, and sanctions-screening results. A FIN ACK only confirms network acceptance; pain.002-style business status has no MT equivalent.
- 03PostingBank Alfa debits Asha TradersBank Alfa (ordering bank)
Once it accepts the request for execution, Bank Alfa books the customer debit under the account agreement before it releases the interbank MT103.
- DR Asha Traders USD operating account — USD 125,000.00
- 06ProcessingMeridian validates and screens the MT103Meridian Bank (correspondent)
The correspondent validates FIN fields, checks Bank Alfa's account, screens the parties and narrative data, and decides whether it can book and forward the payment.
- 07SettlementMeridian settles across its booksMeridian Bank (correspondent)
Meridian debits Bank Alfa's USD account and credits Nordbank's USD account. The ledger movement is the settlement; the MT103 is the instruction.
- DR Bank Alfa USD account at Meridian — USD 125,000.00
- CR Nordbank USD account at Meridian — USD 125,000.00
- 10ProcessingNordbank validates and matches the paymentNordbank (beneficiary bank)
Nordbank checks the beneficiary account, screens the payment, and matches the instruction to the credited nostro entry before paying its customer.
- 11PostingNordbank credits the supplierNordbank (beneficiary bank)
Nordbank books the credit to Northstar Components. A later cancellation is now a recovery request; the original credit cannot be erased by sending another message.
- CR Northstar Components USD account — USD 125,000.00
Sources for this topic2
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · Category 1 — MT103 Single Customer Credit Transfer
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login; content here relies on public summaries. Swift ended MT-to-ISO 20022 coexistence for in-scope cross-border payment instructions (for example MT103 and MT202) in November 2025; MT statement messages are being phased out on a separate timeline.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: The linked serial flow uses fictional banks and a single intermediary; it omits liquidity checks, screening queues, and market-specific return conventions, and any charge deductions shown are illustrative. Return practice in particular varies between institutions and markets.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Deepest material on this page: L4 — Standards & sources. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.