SWIFT MTs / Learning brief
SWIFT MT1xx Customer Payment Messages
Your notes
In simple terms / 01
What this means in plain language
SWIFT Financial Application (FIN) Category 1 covers customer payments, where a customer is a party to the transfer. This guide walks the MT101, MT102, MT103, and MT104 messages along two axes: single versus multiple, and push versus pull.
The Society for Worldwide Interbank Financial Telecommunication (SWIFT) organises its Financial Application (FIN) messages into numbered categories. Category 1, the MT1xx range, is for customer payments, meaning at least one end of the payment is a customer rather than a bank acting for itself. Within this range a small set of message types cover the common shapes: requesting a transfer, sending one payment, sending many bundled payments, and collecting a debit. Once you can place a message on two simple axes, single versus multiple and push versus pull, the whole category becomes easy to read. This guide introduces each type and points to its ISO 20022 equivalent.
Complete lesson / 02
Understand the full idea, step by step
When Asha Traders pays a supplier abroad, its treasurer sees an invoice paid and a reference cleared. Between the two banks, something more precise travels: a structured SWIFT message with a number that tells every reader what it is for. Learn to read that number and a whole category of payments falls into place.
MT (Message Type) and Category 1 — SWIFT FIN messages, grouped by their leading digit
SWIFT — the Society for Worldwide Interbank Financial Telecommunication — runs a messaging service called FIN (Financial Application). Its messages are named MTnnn, and the first digit is the category. Category 1 (the MT1xx range) is for customer payments: a customer, a person or a company, is a party to the transfer. That is the line between Category 1 and Category 2, where the named parties are banks moving their own funds.
Two axes read the whole family
The Category 1 set is easy to hold in your head along two axes. Single versus multiple: some messages carry one payment, others bundle many. Push versus pull: most send funds from payer toward payee, but one collects funds by direct debit. Place each message on those two axes and its job is obvious before you read a single field.
| Message | What it does | One or many | Push or pull |
|---|---|---|---|
| MT101 | Request for transfer — a customer asks its bank to pay | One or many | Push |
| MT102 | Multiple customer credit transfer between banks | Many | Push |
| MT103 | Single customer credit transfer between banks | One | Push |
| MT104 | Direct debit / request for debit transfer | One or many | Pull |
SWIFT MT — ILLUSTRATIVE, NON-PRODUCTION
A compact synthetic MT103 travelling bank to bank. :32A: is the value date, currency, and amount; :50K: names the ordering customer, :59: the beneficiary; :71A:SHA sets the charge bearer (the OUR/SHA/BEN choice lives in field 71A). Asha Traders never sees this message — its bank builds and sends it.
You may be wondering: does every payment I make in my banking app produce an MT103?
No. The MT103 is the interbank message two banks exchange; it is not what your tap on a phone directly creates, and many domestic payments never touch SWIFT at all. The MT101 is the customer-facing cousin — a request a corporate like Asha Traders sends to its bank asking it to pay. The bank receives that request, applies its own checks, and only then issues the interbank message. Instruction to the bank and message between banks are two different steps.
From request to interbank message
- INSTRUCTION
Asha Traders asks Bank Alfa to pay the supplier EUR 1,250.00 — by an MT101 request or another channel.
- VALIDATION
Bank Alfa validates and screens: are the parties and account real, is there cover, does anything need a second look before it leaves?
- MESSAGE
Bank Alfa issues an MT103, the single customer credit transfer, toward Nordbank — directly or through a correspondent. Information, not money.
- SETTLEMENT
The two banks settle what they now owe each other separately; the MT103 announces the payment, it does not carry the value.
- NOTIFICATION
Nordbank credits the supplier and reports it. The invoice is paid only once that credit lands.
COMMON CONFUSION
“The MT103 is the money moving from Bank Alfa to Nordbank.”
The MT103 carries only the instruction and its details. Value moves when the banks change balances and settle between themselves — often across a correspondent or a settlement institution. If the MT103 were lost, no money would be lost; the banks would still hold every euro and re-send or investigate.
STRICTLY SPEAKING
Strictly speaking, MT103 has stricter and richer variants — MT103 STP (Straight-Through Processing), a tighter subset that flows without manual repair, and MT103 REMIT, which carries extended remittance information. As banks adopt ISO 20022, these map at a high level to XML equivalents: MT103 to pacs.008, MT101 to pain.001, MT104 to pain.008. The mapping is conceptual, not field-for-field, and the timeline for cross-border migration is set by SWIFT — check the current programme rather than quoting a date.
FOR NOW, REMEMBER
- Category 1 (MT1xx) is for customer payments — a person or company is a party to the transfer.
- Read the family on two axes: single versus multiple, and push versus pull.
- MT103 is the single interbank customer credit transfer; MT101 is the customer's request to its own bank.
- The message announces the payment; value moves only as the banks post entries and settle.
TRY IT YOURSELF
Asha Traders wants Bank Alfa to make forty supplier payments from its account in one instruction, and wants its own bank to act on that instruction. Which message fits?
The MT103 announced a customer payment — but the banks still have to move their own money to settle it. Category 2 is where that bank-to-bank movement lives, cover payments included.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
SWIFT Financial Application (FIN) Category 1 messages are customer payments: a customer is party to the payment, unlike Category 2, where banks are the parties.
- 02
MT103 is the workhorse single customer credit transfer, with MT103 Straight-Through Processing (STP) and MT103 REMIT variants; MT102 is the bulked multiple customer credit transfer; MT101 is a request for transfer, often used to initiate on behalf of a corporate.
- 03
MT104 is a direct debit and request for debit transfer, so it is a pull or collection instruction rather than a push, which places it on the opposite side of the flow from MT101 to MT103.
Practical use cases / 04
Where you would use this
A correspondent banking analyst reading an incoming MT103 confirms it is a single customer credit transfer and checks the ordering and beneficiary customer fields for screening.
A cash management team sets up a corporate to send MT101 requests so payments can be initiated from the corporate's own systems and executed by the bank.
A migration lead mapping legacy flows to ISO 20022 lines up MT103 against the pacs.008 interbank transfer and MT101 against the pain.001 customer initiation at a high level.
Worked example / 05
Put the idea into a real situation
Illustrative example: Blue Harbour Foods, a corporate, sends its bank an MT101 request for transfer to pay a 12,500.00 EUR invoice to a supplier. The bank executes it as an MT103 single customer credit transfer across the correspondent chain. Later the same day Blue Harbour submits an MT102 bundling 40 smaller supplier payments, and separately its landlord's bank sends an MT104 to collect the monthly rent by direct debit. One request, one push, one bundle, one pull, all in Category 1.
Evidence & review / 07
Evidence & review
SWIFT FIN MT standard, Category 1 customer-payment messages; cross-border correspondent context
What this brief simplifies: Treats the MT-to-ISO 20022 mapping as conceptual rather than field-for-field, and shows the interbank message separately from postings and settlement. Real MT103 STP/REMIT rules and the migration timeline are set by SWIFT.
Sources for this brief3
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · FIN Category 1; MT101/102/103/104
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.
- Market practice
ISO 20022 Standards (Swift ISO 20022 adoption programme) ↗ — Swift · MT to ISO 20022 mapping
Programme milestones change over time; the coexistence period for in-scope cross-border payment instructions ended in November 2025. Check swift.com for the current timeline.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal · Asha Traders scenario and two-axis teaching model
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.