SWIFT doesn't move your money. It moves the message that tells banks to.
If you've ever been paid by an overseas client, paid a supplier in another country, or sent money to a university abroad, there's a good chance your money travelled "by SWIFT." Most people assume SWIFT is a bank, or a pipe that money flows through. It's neither. SWIFT is a secure messaging network: banks use it to send each other payment instructions in a standard format they all understand. The money itself moves separately, across accounts that banks hold with each other. Understanding that one distinction explains almost everything about how international transfers behave â why they cost what they cost, why they sometimes take days, and why "where's my money?" can be surprisingly hard to answer.
Think of SWIFT as a highly secure registered-mail service that only banks can use. When you ask your bank to send USD 5,000 to a supplier in Germany, your bank doesn't put cash in an envelope. It writes a standardised letter â "please pay USD 5,000 to this person, at this bank, for this invoice" â and sends it over SWIFT. The receiving bank trusts the letter because SWIFT verifies who sent it and that it hasn't been tampered with.
The money then moves through a second, invisible layer: the accounts banks keep with one another, called correspondent accounts. If your bank and the German bank don't hold accounts with each other, one or more banks in the middle step in. That's where extra time and extra fees come from. (We unpack this in How banks send money through SWIFT.)
Every bank on the network has a Business Identifier Code (BIC), usually called a SWIFT code. It's 8 or 11 characters long and reads like an address:
So HSBCHKHHHKH identifies HSBC in Hong Kong. A SWIFT code tells the network which bank to send the instruction to â it doesn't identify your account. You still need an account number (or an IBAN in countries that use one).
Because SWIFT is still the default route for money that crosses borders into a bank account, and its design shapes your experience in three practical ways:
If you invoice international clients, pay overseas suppliers or contractors, or receive a salary from abroad, understanding these three points can save real money and a lot of anxious emails.
Payments are only part of the story: in 2025, securities messages made up a slightly larger share of SWIFT traffic (51.5%) than payment messages (43.5%), with treasury, trade and system messages making up the rest.
| Route | What it is | Speed | Reach | Typical use |
|---|---|---|---|---|
| SWIFT | Messaging network between banks; money moves via correspondent accounts | Minutes to 1â3 business days | 200+ countries and territories | Cross-border B2B, large transfers, any-currency payouts |
| Domestic instant rails (e.g. PromptPay, FPS) | Local real-time payment systems run by central banks or bank consortia | Seconds, 24/7 | One country (some now link bilaterally) | Local payments and QR payments |
| Card networks | Visa, Mastercard, UnionPay etc. | Authorised in seconds; settled later | Global merchant acceptance | Consumer purchases, online checkout |
| Stablecoins | Dollar-pegged tokens moved on blockchains | Seconds to minutes, 24/7 | Anyone with a compatible wallet; bank-account reach depends on conversion services | Crypto-native transfers; emerging B2B use |
SWIFT is the most universal way to move money between bank accounts in different countries, but "universal" isn't the same as "cheapest" or "fastest." For many corridors, a provider that collects and pays out over local rails at each end will beat a standard SWIFT transfer on cost and speed. For destinations and currencies where no local option exists â or for large, documented business payments â SWIFT remains the dependable backbone. The smart move is knowing which is which, and asking the right questions (charge type, tracking reference, expected deductions) when you do use SWIFT.