The FIN Network and SWIFT Message Types

Before ISO 20022 became the direction of travel, cross-border banking communication ran — and to a large extent still runs — on SWIFT, and specifically on its FIN messaging service carrying MT (Message Type) messages. Understanding FIN and the MT numbering scheme is essential for anyone working with correspondent banking or reading legacy payment flows.

What SWIFT and FIN actually are

SWIFT — the Society for Worldwide Interbank Financial Telecommunication — is a cooperative that runs secure messaging between financial institutions. A crucial point often missed by newcomers: SWIFT does not move money. It moves instructions. The actual funds move over correspondent accounts and settlement systems; SWIFT is the standardized, authenticated messaging layer that tells banks what to do.

FIN is SWIFT's store-and-forward messaging service, the classic channel over which MT messages travel. It provides validation, delivery guarantees, and authentication between institutions identified by their BIC (Bank Identifier Code). When people say a payment “went over SWIFT,” they usually mean an MT message travelled across FIN.

How MT message types are numbered

MT messages use a three-digit numbering scheme where the digits carry meaning. The first digit indicates the category — the business area — and the remaining digits identify the specific message. The categories include:

• Category 1 — customer payments and cheques.
• Category 2 — financial institution transfers.
• Category 3 — treasury markets (foreign exchange, money markets).
• Category 4 — collections and cash letters.
• Category 5 — securities markets.
• Category 7 — documentary credits and guarantees (trade finance).
• Category 9 — cash management and customer status (statements, balances).

So the first digit alone tells you the domain. An MT starting with 1 is a customer payment; one starting with 9 is a reporting or statement message.

The messages you will meet most

A handful of MT types dominate payments work:

• MT103 — a single customer credit transfer, the workhorse of cross-border customer payments.
• MT101 — a request for transfer, letting a party instruct payments from an account held elsewhere.
• MT202 — a general financial institution transfer, moving funds between banks, often as the settlement or cover leg behind an MT103. The MT202 COV variant carries underlying customer details for transparency.
• MT940 and MT942 — end-of-day and interim account statements in Category 9.

How MT messages are structured

An MT message is organized into blocks — including a header, the text block, and a trailer — and the text block is made of numbered fields introduced by tags. For example, in an MT103 you see tags such as :20: (sender's reference), :32A: (value date, currency, and amount), :50: (ordering customer), and :59: (beneficiary). The format is compact and rigid: meaning comes from the tag and its position, with the detailed definitions living in SWIFT's standards documentation rather than in the message itself.

Some tags carry a letter option — :32A: versus :32B:, for instance — where each option specifies a different combination of subfields. This tight structure makes MT messages efficient to transmit and parse, but it also means a single misplaced character or wrong option can invalidate a message, which is why FIN performs syntactic validation before delivery. Authentication historically relied on bilateral keys and, more recently, PKI, so a receiving bank can trust that a message genuinely came from the claimed sender.

Why FIN is being complemented, not simply dropped

The MT format's terseness is also its limitation. Free-text fields, length limits, and unstructured data make automated screening and reconciliation harder than they need to be. That is precisely the gap ISO 20022 fills with structured, richer data. The migration of cross-border messaging to ISO 20022 does not erase the concepts — an MT103 maps conceptually to a pacs.008 — but it moves from position-and-tag encoding to a modeled, structured standard. For years to come, though, practitioners will still need to read MT messages, because vast amounts of legacy flow and documentation are written in this language.

Key takeaways

• SWIFT provides secure messaging, not settlement; FIN is its classic store-and-forward service for MT messages.
• MT numbers encode meaning: the first digit is the category (business area), the rest identify the message.
• MT103 (customer credit transfer) and MT202/MT202 COV (institution transfer/cover) are core payment messages.
• MT messages use tagged, position-based fields like :32A: and :59: within structured blocks.
• ISO 20022 complements and increasingly replaces MT for cross-border, but MT knowledge stays essential for legacy flows.