Every year, tens of trillions of dollars appear to cross borders in seconds over the SWIFT network. Not one of those dollars ever touches it. SWIFT carries messages. The money still travels the old way: bank account to bank account, one wire at a time.
Because SWIFT, the network almost every bank uses, only sends payment instructions. It never moves money itself. When your bank has no direct account relationship with the recipient's bank, which is most of the time once you cross currencies, the value has to hop through one or more correspondent banks that hold accounts for both sides, and each hop adds its own cutoff time, compliance review, and fee. A payment on SWIFT's faster gpi network with no correspondent in between can land in minutes; one that crosses two or three correspondent banks typically takes 1 to 5 business days and can lose 2 to 5% of its value to stacked fees and currency markup along the way. Section 04 lets you compute your own corridor's fees and timing live.
When you send $10,000 abroad, what actually leaves your bank in that first instant?
Not money. A message. SWIFT (the Society for Worldwide Interbank Financial Telecommunication) is a members-only network founded in 1973 that now connects more than 11,500 banks and institutions in over 235 countries. In 2025 those members sent an average of 59.8 million messages a day, with a single-day record of 68 million, up 12% from 2024. SWIFT holds none of that value. It never has. It is closer to a very secure, very boring email system built only for banks, and its job is to carry instructions, not cash.
Type a payment below and watch it become a real SWIFT field format. The bank names, account numbers, and reference are generated fictional placeholders, but the structure matches how an actual MT103 message, the standard field format for a single customer credit transfer, is put together.
This is the entire payment as far as SWIFT is concerned: a block of formatted text. It contains no money, only an instruction telling the receiving side what to credit, and only if it agrees the message is genuine. Fields simplified for readability; account numbers and references are randomly generated, not real. See fine print for the field key.
If the message carries no money, what does?
Balances that already exist. Banks that do a lot of business together keep pre-funded accounts with each other: a nostro account ("ours, held by you") from the paying bank's point of view, a vostro account ("yours, held by us") from the correspondent's. When your bank already holds euros at a European bank and wants to pay a euro beneficiary there, the SWIFT message just tells that bank to debit your bank's nostro balance and credit the recipient. No new money crosses any border in that moment. Ownership shifts inside accounts that were already sitting there, and the two banks true up the difference between themselves periodically.
Same correspondent, both accounts. The message just moves the line between two ledger entries that were already there. This is the fast, cheap case, and it only works when your bank already holds the relationship.
What happens when your bank and the recipient's bank have never done business with each other?
Most bank pairs haven't, especially once you cross into smaller currencies or smaller institutions. So the payment routes through one or more correspondent banks that do hold relationships with both ends. Each hop is a separate SWIFT message, with its own cutoff time, its own sanctions and compliance screening, and often its own quiet deduction, a "lifting fee," subtracted from the amount in transit before it's passed along. Industry pricing guides put that fee at roughly $15 to $50 per hop. Neither the sender nor the recipient necessarily knows in advance exactly which banks the payment will pass through, or how much will be left by the time it lands.
Standard international wires take 1 to 5 business days depending on how many of these hops are involved, per current wire-transfer cost guides from Airwallex, Corpay, and Sphere. None of that delay is really about the technology. It's about how many separate institutions have to agree, in sequence, that the payment is legitimate and that their own books balance.
For the same transfer, how much difference does one extra correspondent bank actually make?
Adjust the amount, the currency corridor, the number of correspondent hops, and whether both banks support SWIFT's faster gpi tracking standard. Everything below is computed live from published fee and timing ranges, not a canned demo.
Modeled from published 2026 benchmark ranges (send fee ~$40, receive fee ~$15, per-hop lifting fee ~$25, FX markup 1.5% on major pairs / 3% on emerging pairs), not a live quote from any specific bank. See fine print for sourcing and the timing formula.
Notice what happens at small amounts: the fixed fees barely move, so they eat a much bigger share of a $1,000 transfer than a $100,000 one. That's the opposite of how a percentage-based cost usually feels, and it's a big part of why small cross-border payments are disproportionately expensive.
If SWIFT doesn't move money, what exactly is all that daily volume?
Instructions. Only instructions. Below is a live counter running at SWIFT's own reported 2025 average rate, computed directly from 59.8 million messages divided across a day. Watch it for a few seconds.
11,500+ institutions, 235+ countries, 59.8 million messages a day on average in 2025 (a single-day record of 68 million, up 12% year over year), per SWIFT's own 2025 Annual Review. Every one of those messages is an instruction between banks. None of them is a dollar, a euro, or a yen changing hands inside the network itself, because the network was never built to hold value, only to carry claims about it.
What happens when someone steals a bank's ability to send genuine, correctly authenticated SWIFT instructions?
Over the weekend of February 4 to 5, 2016, hackers who had already spent weeks inside Bangladesh Bank's network, later linked by U.S. prosecutors to North Korea's Lazarus Group, used stolen but entirely valid credentials to issue 35 payment instructions from the central bank's account at the Federal Reserve Bank of New York. They weren't forged in any cryptographic sense. They were real SWIFT messages, correctly signed, sent by someone who had stolen the right to send them. Together the 35 instructions tried to move $951 million out of the account.
The $20 million bound for Sri Lanka was stopped only by luck: the hackers misspelled the beneficiary's name, "Shalika Foundation," as "Shalika Fandation." A Deutsche Bank routing clerk noticed the typo and asked Bangladesh Bank to confirm it, which killed that transfer and, in the scramble that followed, the remaining $850 million too. Sri Lanka's $20 million was later fully recovered. The $81 million that reached five accounts at Rizal Commercial Banking Corporation in Manila was less lucky: it was withdrawn and laundered through casino junkets during the Chinese New Year holiday, when the bank branch involved was effectively unstaffed for the checks that might have caught it. As of 2025, only $15 million of that $81 million has ever come back.
Nothing about SWIFT's cryptography failed here. The messages were exactly what they claimed to be: authenticated instructions from a recognized sender. The system verifies who sent a message. It has no way to verify, on its own, whether the payment should happen. That judgment sits entirely with the humans and controls at each bank in the chain, which is precisely what a stolen set of credentials bypasses.
Is there a way to move value across a border that doesn't rely on correspondent accounts and manual review?
Bitcoin's Lightning Network settles differently by design. A Lightning payment is a direct transfer of value between two parties over a network of payment channels, final in seconds, with no correspondent chain and no separate settlement step happening later behind the scenes. Amboss connects businesses to that kind of instant, global payment rail: you send, receive, and settle directly, in the currency you choose, without waiting on a chain of intermediary banks to each agree that the payment is real.
That doesn't remove every kind of friction. Regulated businesses still carry the same compliance obligations they would anywhere else. What changes is architectural: value moving directly between two parties instead of being represented by a message that a sequence of separate institutions has to relay and re-verify.
If one network sits between 11,500 banks and the rest of the world, who decides who's allowed to stay connected?
SWIFT is a member-owned cooperative headquartered in Belgium, under Belgian and EU law, with oversight from the G-10 central banks. It isn't a government body, but it complies with binding sanctions decisions issued by the jurisdictions it operates under. In February and March 2022, following Russia's invasion of Ukraine, a coalition of the EU, US, UK, and Canada ordered SWIFT to disconnect seven major Russian banks: VTB, Bank Otkritie, Novikombank, Promsvyazbank, Rossiya Bank, Sovcombank, and VEB. SWIFT complied on March 12, 2022, cutting those banks' channels to most of the world's correspondent network overnight. Sberbank and Gazprombank were deliberately left connected at first, to keep EU energy payments flowing, which shows how surgically this kind of cutoff can be applied.
This isn't a flaw unique to SWIFT, and it isn't an absolute kill switch. Russia had already built SPFS, its own domestic message system, and leaned harder on it plus China's CIPS network and bilateral currency arrangements to route around the exclusion, at real cost in friction and reach but not a full stop. The honest point isn't that SWIFT acted maliciously. It's that any network funneling 11,500 institutions through one messaging cooperative is, structurally, a single coordinated policy decision away from cutting a country's banks off from most of the world's correspondent relationships in a matter of days. That's a feature when it's used for enforcement against a government most of the world has sanctioned, and a real, honest risk for anyone whose access depends on staying in every relevant government's good graces indefinitely.
Ask what's actually moving. When someone says "the money's been sent," find out whether that means an instruction went out or a balance actually settled. On SWIFT, those are two different moments, sometimes days apart.
Count the hops before you're surprised by the fee. Ask your bank how many correspondents typically sit in a given corridor. More hops means more lifting fees and more days, and neither shows up until the payment is already in flight.
Treat "instant" claims as corridor-specific. SWIFT gpi's fastest numbers describe gpi-to-gpi payments with few or no correspondents. They don't automatically apply to your route, your bank, or your currency pair.
Know who can flip the switch. Access to SWIFT, and to the correspondent relationships layered on top of it, is a policy decision as much as a technical one. That's true whether the decision benefits you or works against you.
Because SWIFT only sends payment instructions. The money moves separately, through a chain of correspondent bank accounts, and each hop adds its own cutoff time, compliance review, and fee. A single-hop gpi payment can land in minutes; a payment crossing two or three correspondents typically takes 1 to 5 business days.
No. SWIFT is a messaging network used by more than 11,500 banks in over 235 countries. It carries authenticated instructions between banks but holds no funds and settles nothing itself. The actual transfer of value happens separately, through correspondent bank accounts.
It depends on whether your bank already holds an account relationship with the recipient's bank. If not, the payment needs one or more correspondent banks in between, each charging a lifting fee of roughly $15 to $50 and adding its own delay.
SWIFT gpi is a tracking and speed standard launched in 2017. For participating banks, roughly half of gpi payments reach the beneficiary bank within 30 minutes and nearly all within 24 hours. That's the message reaching the bank, not necessarily funds being credited to the account, which still depends on that bank's own processing.
Yes. SWIFT complies with binding sanctions decisions from the jurisdictions it operates under. In March 2022, following a coalition decision by the EU, US, UK, and Canada, SWIFT disconnected seven major Russian banks, cutting their correspondent channels to most of the world overnight.