SWIFT / Learning brief
Introduction to SWIFT
Your notes
In simple terms / 01
What this means in plain language
Traces the move from error-prone TELEX instructions to SWIFT's standardized, secure network for exchanging financial messages.
SWIFT provides a secure network and common standards for financial institutions to exchange structured messages. It improved on older manual communication methods by making instructions more consistent, authenticated, traceable, and suitable for automated processing. SWIFT generally carries financial messages; it is not itself the bank account on which every underlying obligation settles. Institutions still use correspondent accounts, market infrastructures, and internal ledgers to move value. Understanding this distinction explains why a network acknowledgement can confirm message delivery without proving that a beneficiary has received funds.
Complete lesson / 02
Understand the full idea, step by step
You have almost certainly seen four letters on an international transfer form: SWIFT. People say a payment "went by SWIFT" as if SWIFT were a pipe that carried the money abroad. It is one of the most useful ideas in this whole course to get right early, because SWIFT does something quieter and more precise than that — and once you see what it actually does, a great deal of cross-border payments stops being mysterious.
What SWIFT is — and is not
- What it is
- A member-owned cooperative that runs a secure financial-messaging network and publishes message standards
- What it moves
- Messages — instructions, confirmations, statements, status
- What it does NOT do
- Hold accounts, clear, or settle payments; no money sits inside SWIFT
- Who owns it
- Its member financial institutions, as a cooperative
- Full name
- Society for Worldwide Interbank Financial Telecommunication
From ambiguous cables to a shared standard
Before a shared standard, banks instructed each other with free-text cables and TELEX — slow, easy to mistype, and hard to authenticate. Was the sender really who they claimed? Did "2.000" mean two or two thousand? Banks agreed to build something better together: one secure network where identified members exchange messages in agreed formats. Two things came out of that. First, a network that authenticates the sender and delivers the message intact. Second, a common language — the message standards — so a bank on the far side of the world can read an instruction the same way its author meant it.
SWIFT — Society for Worldwide Interbank Financial Telecommunication
SWIFT is a cooperative owned by its member institutions. It wears three hats at once: it operates a secure messaging network, it acts as a standards body that defines and maintains message formats, and it provides related services around those. What it is not is a bank, a clearing house, or a settlement system. It never touches an account. Think of it as the trusted post office and the shared grammar of financial messaging — not the treasury.
You may be wondering: if SWIFT does not move the money, then who does?
The banks do, through the account relationships and settlement arrangements you meet later in this course. When Bank Alfa pays Nordbank abroad, SWIFT carries the instruction; the actual value moves as debits and credits across accounts the banks hold with each other or with a correspondent, and is finally squared through a settlement institution. SWIFT is the announcement; the ledgers and settlement are the money. Keeping the two apart is exactly how a practitioner reasons about a stuck payment: a delivered message does not mean a completed payment.
COMMON CONFUSION
“SWIFT is the system that clears and settles international payments.”
SWIFT settles nothing. It transmits the instruction that *asks* for a payment and reports how that message was handled. Whether the beneficiary is credited depends on the receiving bank's checks, its funding, and settlement across accounts elsewhere. A payment can have a perfectly delivered SWIFT message and still be sitting unpaid while a bank finishes a review.
Read the steps as text
- 01MessageThe customer orders a USD transfer abroadOrdering customer → Bank Alfa (ordering bank)
The ordering customer instructs Bank Alfa to pay a supplier banked at Cassia Bank in another country. Bank Alfa has no direct account relationship with Cassia — that is why correspondents exist.
- 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
- 04MessageThe MT103 goes to Bank Alfa's USD correspondentBank Alfa (ordering bank) → Meridian Bank (correspondent) · MT103
In the serial method the payment instruction itself travels through the account chain. Meridian holds Bank Alfa's USD account (Bank Alfa's nostro), so Meridian can debit it.
- 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
- 07MessageCassia is advised its nostro was creditedMeridian Bank (correspondent) → Cassia Bank (beneficiary bank) · MT910
The MT910 credit confirmation lets Cassia's reconciliation match expected funds against its nostro account movement.
- 08MessageThe MT103 continues serially to CassiaMeridian Bank (correspondent) → Cassia Bank (beneficiary bank) · MT103
Meridian forwards the payment instruction to the beneficiary bank with the full ordering and beneficiary details intact.
- 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
STRICTLY SPEAKING
Strictly speaking, "SWIFT" is used loosely in the industry to mean three different things: the cooperative organisation, the network it runs, and the message standards it publishes. They are related but distinct, and the rest of these lessons pull them apart — the network in one lesson, the connectivity in another, the services and standards in their own. When a colleague says "send it over SWIFT", ask which of the three they mean; it usually clarifies the real question.
FOR NOW, REMEMBER
- SWIFT is a member-owned cooperative that runs a secure messaging network and publishes message standards.
- It moves messages — instructions, confirmations, status — never money.
- It is not a clearing or settlement system and holds no accounts.
- A delivered SWIFT message is an announcement; the payment completes only when banks post and settle the value elsewhere.
TRY IT YOURSELF
A customer calls: their SWIFT message shows as delivered to the beneficiary bank two hours ago, but the beneficiary still has no money. What is the most accurate thing to tell them?
If SWIFT is a post office for financial messages, how does that post office actually work — how does it hold a message until the far side is ready, and how does a bank get permission to write to another at all?
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
SWIFT standardizes secure communication between financial institutions.
- 02
Messaging and the underlying settlement of value are distinct.
- 03
Delivery confirmation is not beneficiary-credit confirmation.
Practical use cases / 04
Where you would use this
A new payments employee learns where SWIFT fits in a cross-border transfer.
A support agent explains why a delivered message can still require investigation.
An architect separates network connectivity from ledger and correspondent-account design.
Worked example / 05
Put the idea into a real situation
Illustrative example: Bank A sends a standardized payment message to Bank B through SWIFT and receives a network acknowledgement. That proves the network accepted or delivered the message as indicated; it does not prove Bank B credited the customer. Bank B may still need screening, account validation, funding confirmation, and posting. An investigation therefore checks both message evidence and the correspondent or ledger entries that support the transfer.
Evidence & review / 07
Evidence & review
SWIFT cooperative, network, and standards, in general terms; not tied to a specific product release.
What this brief simplifies: Presents SWIFT's three roles (cooperative, network, standards body) at a conceptual level and uses one illustrative serial cross-border flow; omits governance, oversight, and product detail covered later.
Sources for this brief3
- Market practice
Swift products and services ↗ — Swift · SWIFT as cooperative, messaging network, and standards body
Used for the public overview of product details documented behind swift.com.
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · MT message standards
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
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.