SWIFT (Society for Worldwide Interbank Financial Telecommunication)

SWIFT is the messaging network banks use to tell each other about payments. It pays to be clear about what that means, because it is the thing people get wrong: SWIFT moves instructions, not money. When a bank in London pays a bank in Tokyo, SWIFT carries the message that says what to pay, to whom, and on whose behalf. The money itself moves through accounts the two banks hold with each other, or through a third bank that both of them deal with. Mixing those two ideas up explains a lot of the confusion about why an international payment takes days.

The network is a co-operative owned by its member banks, and it reaches most countries. Its main job is a shared language: a standard set of message types that every member reads the same way, so an instruction sent from one bank's system arrives in a form another bank's system can act on. That language is moving to ISO 20022, which carries more set-out data than the older message types. The aim is to cut the number of payments that stop for a person to read, since a stopped payment is where most of the delay and most of the cost sit.

What A Message Actually Carries

A payment message names the sending bank, the receiving bank, the amount, the currency, the beneficiary and a reference. Banks are named by BIC code, and accounts by IBAN code in the countries that use one. There are fields for who pays the charges and for a short note to the beneficiary, and the older formats were tight on space, which is why so many payments arrived with a reference cut short and a finance team left guessing.

The Chain Of Banks Underneath

Two banks that deal with each other directly can settle between themselves. Most pairs do not, so the payment goes through one or more banks in the middle that both sides trust. Each of those holds accounts for the others and debits and credits them as messages arrive. Every extra bank in the chain adds a step, a fee and a chance of a stop. A payment between two large banks in major currencies may pass through one intermediary. A payment into a smaller market may pass through three.

Where The Fees Come From

Each bank in the chain can take a cut, and the message says who bears it. Charges can fall on the sender, on the beneficiary, or be shared. The sender's own bank also applies a currency rate, and the spread on that rate is often larger than the stated fee. The result is the familiar complaint: a payment sent for a round sum arrives short, and nobody can say exactly where the difference went. Asking for the charge option in writing is a reasonable habit.

Why It Takes Days

Time zones, cut-offs and checks. A message sent after a bank's cut-off waits for the next working day. A chain of three banks may cross three sets of working hours. Any bank in the chain can pause a payment for a compliance check, and while it is paused nobody downstream knows. None of this is the network being slow. It is the banks underneath it working to their own clocks.

Checks Along The Way

Every bank in the chain screens what passes through it against sanctions lists and its own anti-money laundering rules. A name that looks like one on a list will stop the payment until a person clears it. Common names, transliterated names and missing address data all raise the odds of a stop. This is a leading reason richer message data matters: a message with a full, structured address is less likely to be held than one with a line of free text.

The Move To Richer Messages

The shift to the newer standard changes what is possible. Structured names and addresses cut false stops. Longer reference fields mean a payment can carry the invoice numbers it settles, which makes matching on arrival far easier. There is also room for purpose codes, which helps the checks along the way. The catch is that the benefit only arrives when both ends use the richer format, and adoption is uneven while banks work through their own timetables.

Where SWIFT Is Not The Answer

For euro payments inside Europe, the SEPA schemes are generally cheaper and quicker. For small, frequent payouts, a provider with local accounts in the destination market can avoid the chain of banks altogether. A wire transfer over this network still suits large, one-off or unusual payments, where certainty matters more than cost. The mistake is using it for everything because it is the route the finance team knows.

Sending A Cross-Border Payment Well

Get the bank and account identifiers right first, since a wrong one is a common cause of a returned payment. Put a structured address on the beneficiary rather than a line of free text. Say who pays the charges. Tell the beneficiary what to expect, so a short arrival is not a surprise. Keep the reference meaningful, because it is what lets the far end match the money. Ask your bank for the reason whenever a cross-border payment is late, since a compliance stop looks the same as a slow chain from the outside. For frequent payouts, payout solutions is designed to cover the local-account route. This piece on moving money across borders compares the options.

‍