SWIFT messages are standardized electronic instructions that banks send to each other over a secure global network to coordinate financial transactions, primarily cross-border payments. The key distinction that surprises many people: SWIFT moves messages, not money. The network doesn’t hold funds, manage accounts, or settle transactions. It transmits the instructions that tell banks what to do with money, making it more accurate to think of SWIFT transactions as transmissions rather than transfers.
How SWIFT Messages Work
When you send an international wire transfer, your bank doesn’t physically move currency overseas. Instead, it sends a SWIFT message to the receiving bank (or to an intermediary bank along the way) with structured instructions: who is sending money, who should receive it, how much, in what currency, and which accounts to debit and credit. The banks then settle the actual funds between themselves through correspondent banking relationships or central bank systems.
Every institution on the SWIFT network is identified by a Business Identifier Code, or BIC. This is a standardized code (sometimes called a SWIFT code) that follows the international ISO 9362 standard, ensuring every bank has a unique, machine-readable identifier. When you fill out a wire transfer form and provide a SWIFT/BIC code, you’re telling your bank exactly which institution should receive the message.
What a SWIFT Message Contains
Every SWIFT message follows a rigid five-block structure: a basic header block, an application header block, a user header block, a text block (the actual content), and a trailer block. Within the text block, each piece of data sits in a numbered field preceded by a tag. Field 20, for example, carries the Transaction Reference Number, while Field 21 holds a Related Reference that links the message to a previous one. Fields can also contain BIC codes identifying parties in the transaction, like the sender’s correspondent bank or the beneficiary.
This rigid formatting is the whole point. Because every bank on the network structures its messages the same way, the data can be read and processed automatically by computers on the receiving end, reducing errors and speeding up processing compared to the days of freeform telexes.
Common Message Types
SWIFT organizes its legacy messages into categories using “MT” (Message Type) codes. The two most widely used payment messages are:
- MT 103 (Single Customer Credit Transfer): This is the standard message for a customer-initiated international payment. When you wire money to someone abroad, your bank sends an MT 103. It contains all the details about the sender, the beneficiary, the amount, and the payment instructions.
- MT 202 (General Financial Institution Transfer): This message handles bank-to-bank transfers. When banks need to move funds between themselves to settle obligations or reposition liquidity, they use an MT 202 rather than an MT 103.
Beyond payments, SWIFT carries messages for securities trading, trade finance (like letters of credit), foreign exchange confirmations, and treasury operations. Each category has its own set of MT codes with specific fields tailored to that type of transaction.
The Shift to ISO 20022
SWIFT is in the middle of a major transition from legacy MT messages to a newer standard called ISO 20022, which uses richer, more structured data formats known as MX messages. The cross-border payment community went live with this new format in March 2023, and SWIFT’s board confirmed November 2025 as the end of the coexistence period when banks could use either format interchangeably for cross-border payments.
Why does this matter? ISO 20022 messages can carry significantly more data than legacy MT messages. Instead of cramming information into rigid, character-limited fields, the new format supports detailed payment information, structured addresses, and richer reference data. For you as a sender or receiver of international payments, this eventually means fewer rejected or delayed transfers caused by incomplete or unstructured information.
Starting in November 2026, SWIFT will begin rejecting cross-border messages that use unstructured postal addresses, requiring banks to send fully structured or hybrid address formats instead. This is one practical example of how the new standard tightens data quality requirements across the network.
Tracking Payments With SWIFT gpi
One longtime frustration with international transfers was the lack of visibility. You’d send a wire and have no idea where it was until it either arrived or didn’t. SWIFT’s Global Payments Innovation initiative, called gpi, addresses this by adding end-to-end tracking to the messaging process.
Every gpi payment carries a Unique End-to-End Transaction Reference (UETR) that follows the payment through every bank it touches. Banks along the payment chain update the status in SWIFT’s cloud-hosted gpi Tracker, so your bank (and increasingly, you as the customer) can see whether the payment is in transit, has been credited to the beneficiary’s account, is on hold, or was rejected. The system also provides real-time confirmation when funds actually reach the recipient.
For businesses, gpi offers additional tools. Corporate treasurers can receive real-time notifications when incoming payments are initiated, see fee breakdowns and payment route details, and query the status of transactions through API connections to their banks. This level of transparency was essentially unavailable before gpi launched.
Who Uses SWIFT Messages
SWIFT connects thousands of financial institutions across more than 200 countries, making it the backbone of international banking communication. Banks are the primary users, but the network also serves broker-dealers, asset managers, clearinghouses, and corporations with direct treasury connections.
If you’ve ever sent or received an international wire transfer, a SWIFT message was almost certainly involved. The same is true for many securities trades, foreign exchange deals, and trade finance transactions that cross borders. While newer payment networks and fintech platforms handle some international transfers differently, SWIFT remains the dominant messaging system for traditional cross-border banking.