SWIFT: how an international transfer actually travels

Almost everyone thinks SWIFT moves their money from one country to another. It doesn't. SWIFT moves the order; the money travels a different path —and that's the key to why a transfer is slow and costly.

You send a transfer to another country and, in your head, the money "leaves" your bank and "arrives" at the destination bank, like a parcel crossing the border. It's a comfy image, and it's false. No money travels between those two banks: a message does. Understanding exactly what that message is —and what it is NOT— is understanding why an international transfer is slow, costly, and sometimes lost from sight along the way.

What SWIFT is (and isn't)

SWIFT is one of those words everyone uses and almost no one defines well. People say "I sent it via SWIFT" as if SWIFT were a pipe with money flowing through it. It isn't. Let's start with the definition that changes everything.

Key concept

SWIFT (Society for Worldwide Interbank Financial Telecommunication) doesn't move money: it's a secure messaging network between banks. Institutions send each other standardized messages to instruct payments, but the money moves through a different mechanism.

Put another way: SWIFT carries the order, not the cash. It's the system by which thousands of institutions across most of international banking reliably tell one another, "make this payment."

The distinction isn't a technicality. It's the basis of everything else. Moving the information ("pay X to Y") and moving the money (getting Y's account credited) are two separate processes, and SWIFT only handles the first.

The BIC: each bank's address

For a message to reach the right bank, each institution needs a unique address within the network. That's the role of the BIC.

Each institution has a BIC (Business Identifier Code), also called a SWIFT code, that identifies it uniquely. Think of it as a postal address for financial messages: it doesn't say how much is paid or to whom, it says which bank the instruction should be delivered to. When you give your "SWIFT code" to receive a transfer from abroad, you're giving exactly that: your bank's address on the network.

MT messages

If SWIFT carries orders, those orders have to be written in a format every bank reads the same way. That's where MT messages come in.

SWIFT defines a catalog of standardized messages with a rigid format: each type has its structure, its fields and its rules. For example, an MT103 is a customer credit transfer —the typical message behind an international transfer from a person or company. The key point: an MT103 is a structured instruction, a form one bank hands another saying "credit this amount to this beneficiary." It is not money. It's the paperwork that says what to do with the money.

Correspondent banking: how the money actually moves

If the message only says "pay Y," the uncomfortable part is missing: where does the money that actually shows up in Y's account come from? This is where correspondent banking comes in, and it's the piece almost nobody sees.

  1. The money doesn't "travel" over SWIFT. What happens is that banks hold accounts with one another: nostro accounts (my account at your bank) and vostro accounts (your account at my bank).
  2. If the sending bank and the receiving bank have no direct relationship, the operation passes through a chain of correspondent banks that are connected to each other.
  3. At each link, a bank debits and credits the corresponding accounts: nobody ships banknotes; balances are adjusted in the accounts banks already hold between them.
  4. That's why an international transfer can take time and rack up fees at each hop: every correspondent involved posts its entry and usually charges for it.

Seen this way, the transfer isn't money crossing the planet, but a sequence of chained accounting entries that, in the end, leaves the amount in the right account. SWIFT synchronizes that choreography with messages; correspondent banking executes it with debits and credits.

The limits of the model

This scheme works and underpins most of the world's cross-border payments, but it has obvious costs for whoever sits at the end of the chain:

The industry knows this and is pushing on it. SWIFT gpi (global payments innovation) improved tracking and speed, bringing end-to-end traceability and payment confirmation. And in parallel, the migration to ISO 20022 is underway —a messaging standard far richer in data than the classic MT messages— which I cover in the entry on ISO 20022: the world's new financial language.

Common mistakes

Common mistake

"SWIFT transfers my money." No. SWIFT transmits the payment instruction; the money moves through correspondent banking and the settlement systems. Confusing the message with the money is confusing the letter with the payment.

The banking angle

From inside a bank, SWIFT is not a detail: it's critical infrastructure for cross-border payments. Three things make that clear.

Understanding SWIFT is understanding that, in payments, moving the information and moving the money are two different things. The message travels over a network; the money, over a chain of accounts between banks. Whoever conflates the two doesn't get why a transfer is slow —or why improving it is so hard.

Jorel del Portal

Jorel del Portal

Systems engineer specialized in enterprise software architecture and high-availability platforms in banking and finance.