The SWIFT network and BICs
What the SWIFT network actually is, what FIN does, and how a BIC identifies a bank — the addressing layer behind cross-border payments.
L0 Explain simply
An everyday analogy: SWIFT is a postal service built only for banks. It never carries money — it carries carefully formatted letters that say things like "please pay this customer". Every post office in the system has a unique address so a letter never goes astray; in SWIFT that address is the BIC, a code of 8 or 11 characters that pins down exactly which bank, in which country and location, and optionally which branch, should receive the message. The money itself moves separately, later, when banks adjust the accounts they hold with one another. Keeping the letter and the money apart is the single most useful idea for understanding everything that follows in this domain.
L1 Core concepts
SWIFT is a member-owned cooperative that runs a secure messaging network for financial institutions. Its core messaging service for payments is FIN, a store-and-forward service that validates each MT message against the standard before delivering it. Institutions are addressed by their BIC: 4 characters for the institution, 2 for the country, 2 for the location, and an optional 3 for the branch — 8 or 11 characters in total. Two institutions can exchange most message types only after establishing an RMA (Relationship Management Application) authorisation, which acts as a permission filter over who may send what to whom. SWIFT transports and validates instructions; actual settlement happens on the accounts banks hold with each other or with central banks.
L2 Practitioner view
In practice, teams treat SWIFT as reliable plumbing and spend their time on its edges. Onboarding a new correspondent means exchanging RMA authorisations before the first payment can flow; a missing RMA surfaces as messages that simply cannot be sent. BIC reference data must be kept current, because a payment addressed to a merged or retired BIC will fail or be misrouted. FIN's network validation rejects malformed messages before they reach the counterparty, so format errors show up as negative acknowledgements in the sending bank's own queues rather than as queries from the other side. And because SWIFT moves instructions rather than value, an urgent message does not by itself make funds arrive — that still depends on account relationships, cut-offs, and liquidity.
L3 Technical details
FIN is a store-and-forward service. Every submitted message draws an ACK (accepted onto the network) or NAK (rejected with an error code); the ACK is the sender's proof of submission, and a sender can additionally request a delivery notification confirming when the receiver's interface took the message. RMA authorisations gate traffic: a correspondent can authorise all message types or only a subset, so an MT sent without the matching authorisation is simply not deliverable. Addressing is by BIC: a BIC8 identifies the institution, country, and location, while a BIC11 adds a branch code steering the message to a specific branch; with no branch code, the network treats the destination as the default XXX branch. Message user groups add a further filter, restricting certain message types to institutions registered for the service concerned.
Sources for this topic2
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · Standards MT general information; BIC structure
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 postal analogy compresses SWIFT to a mail carrier: it omits delivery notification, non-repudiation, and other network services, and treats the BIC directory as static when BICs are issued, changed, and retired continuously. Full SWIFT documentation sits behind a swift.com account.
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: L3 — Technical details. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.