Guest Articles / Learning brief
SWIFT – A Communication Platform
Your notes
In simple terms / 01
What this means in plain language
Surveys SWIFT's role, connectivity, messaging services, security model, and support for MT and ISO 20022 MX standards.
SWIFT provides a secure communication environment that financial institutions use to exchange standardized financial messages. It does not itself turn every message into settlement or move customer money. Instead, it helps authenticated participants connect, address one another, apply agreed formats, and monitor message delivery. Traditional MT messages and ISO 20022 MX messages can support different business processes on the network. Understanding this separation is important: the message may travel through SWIFT while the related funds settle through correspondent accounts, a market infrastructure, or another arrangement.
Complete lesson / 02
Understand the full idea, step by step
Think of a well-run postal service. You do not need the recipient to be standing at their door when you post a letter; you hand it over, the service holds and routes it, and it lands in the right box when the recipient next looks. SWIFT works on the same principle — and that single design choice explains why banks in opposite time zones can instruct each other without ever being online together.
A platform that holds, then forwards
SWIFT's core service is a communication platform: members address one another and exchange structured messages. The platform authenticates the sender, checks the message against the published format, records what happened, and delivers it. It carries instructions and information — a payment order, a confirmation, a statement, a status. It does not become the account that settles the underlying obligation. A cross-border payment can use SWIFT to communicate while the value moves through correspondent accounts entirely outside the network.
Store-and-forward — accept and hold a message, then deliver it when the receiver is ready
In a store-and-forward service, the sender submits a message; SWIFT accepts it centrally, validates and stores it, and forwards it to the receiver when that institution's connection is available. Sender and receiver need never be online at the same instant — essential for a network spanning every time zone. Each message is individually addressed and acknowledged, so the sender always learns whether the network accepted the instruction. Reliability, not live conversation, is the goal.
One message, end to end
- INSTRUCTION
Bank Alfa's system composes an instruction to Nordbank and formats it to the agreed standard.
- VALIDATION
SWIFT authenticates Bank Alfa as the sender and validates the message against the published format; a malformed message is rejected back to Bank Alfa.
- MESSAGE
SWIFT stores the accepted message centrally and acknowledges receipt to Bank Alfa — the network now owns delivery.
- NOTIFICATION
When Nordbank's connection is available, SWIFT forwards the message and records the delivery; Bank Alfa can see it was delivered.
RMA — Relationship Management Application
Before two institutions exchange live traffic, each sets up an RMA authorisation that says, in effect, "I am willing to receive these kinds of messages from you." It is a permission list on the network: it controls *who may send what to whom*. Without a matching authorisation, the message is not accepted for that counterparty. RMA is how a bank limits its exposure to unwanted or unexpected traffic at the network layer.
COMMON CONFUSION
“If Bank Alfa has an RMA with Nordbank, it means the two banks hold accounts with each other and can settle payments between them.”
RMA is purely messaging authorisation — permission to exchange certain message types. It says nothing about whether an account relationship exists. Two banks can be authorised to message each other and still have no way to settle directly; conversely, a correspondent account is a separate commercial and operational arrangement. Never read an RMA as proof of a funding relationship.
What is actually happening here — is RMA the same as screening or a sanctions check?
No. RMA operates before and beneath the business checks. It decides whether the network will even accept a message from this sender for this receiver. Sanctions screening, format validation, funding, and the credit decision all happen afterwards, inside the banks. RMA is the doorway; the room beyond it still has all its own controls. A practitioner separates "was the message allowed onto the network?" from "did the receiving bank agree to pay?".
FOR NOW, REMEMBER
- SWIFT is a communication platform: members address each other and exchange structured messages.
- Store-and-forward means SWIFT holds a validated message and delivers it when the receiver is ready — no need to be online together.
- RMA (Relationship Management Application) authorises who may send which message types to whom.
- An RMA authorisation is messaging permission only — never proof of a correspondent account or a settlement relationship.
TRY IT YOURSELF
Bank Alfa has a valid RMA authorisation with a bank it has never transacted with. An operator wants to send it a high-value payment straight away. What is the sound assessment?
You have seen the post office at work. Underneath it runs a private network with its own security — SWIFTNet. Next: what that network is, and the concrete ways a bank plugs into it.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
SWIFT transports financial instructions; it is not the funds themselves.
- 02
Standard formats make messages interpretable across institutions.
- 03
Messaging and settlement paths must be mapped separately.
Practical use cases / 04
Where you would use this
A treasury analyst traces a cross-border instruction sent over SWIFT and reconciles it with account movements.
A migration team maps business data from an MT format into an ISO 20022 MX structure.
A support engineer distinguishes a message-delivery issue from a downstream settlement delay.
Worked example / 05
Put the idea into a real situation
Bank A sends Bank B a standardized instruction through SWIFT. The network authenticates and delivers the message, while each bank records the delivery status. Separately, the banks use their correspondent or infrastructure arrangements to settle the associated value. If Bank B receives the message but the beneficiary is not credited, investigators must inspect the downstream payment and posting steps rather than assuming the communication platform moved the funds. This is a simplified logical example.
Evidence & review / 07
Evidence & review
SWIFT store-and-forward messaging and RMA, at a conceptual level; specific message categories and RMA administration detail vary by institution.
What this brief simplifies: Describes store-and-forward and RMA conceptually; does not cover RMA bootstrapping, distribution, or per-message-type granularity in full.
Sources for this brief3
- Market practice
Swift products and services ↗ — Swift · Store-and-forward messaging; Relationship Management Application (RMA)
Used for the public overview of product details documented behind swift.com.
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · Message validation against published 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.