SWIFT
Also known as: SWIFT code, BIC code, international wire transfer, interbank messaging network
SWIFT (Society for Worldwide Interbank Financial Telecommunication) is the international messaging network that banks use to communicate securely with each other when processing cross-border wire transfers.
It does not move money itself -- it sends standardized payment messages between banks, which then settle funds through correspondent banking relationships. Founded in 1973 and based in Belgium, SWIFT connects over 11,000 financial institutions in more than 200 countries. Every bank on the network has a unique SWIFT code (BIC -- Bank Identifier Code) used to identify the institution in payment messages.
SWIFT, explained at three levels
At home
SWIFT is the messaging system banks use when you send money to a bank account in another country. When you initiate an international wire transfer, your bank sends a message to the recipient's bank through the SWIFT network saying 'please credit this account with this amount.' The banks then settle the funds between themselves through their banking relationships. To send money to a bank in another country, you need the recipient's SWIFT code (a code identifying their bank) and their account number (IBAN in Europe, account number elsewhere).
At work
If your business pays international suppliers or receives payments from international clients, those transactions likely travel over the SWIFT network. The SWIFT code (also called BIC) uniquely identifies the bank and often the branch. International payments typically take 1-5 business days to arrive because of the time zone differences between banks in the payment chain and the number of intermediary (correspondent) banks involved in routing the payment.
At home
Correspondent banking is why international wires can be slow and have multiple fees: your bank may not have a direct relationship with the recipient's bank. Instead, the payment routes through one or more intermediary 'correspondent banks' that do have relationships with both ends. Each correspondent bank can deduct a processing fee from the amount in transit, meaning the recipient may receive less than you sent. SWIFT GPI (Global Payments Innovation, launched 2017) added real-time tracking of international payments through the correspondent chain, similar to a package tracking number for wire transfers.
At work
Business SWIFT payment considerations: SHA (shared charges, each party pays their own bank's fees -- most common), OUR (sender pays all fees, recipient receives full amount -- used when guaranteeing full invoice payment), and BEN (recipient pays all fees -- uncommon). For vendor payments where the invoice specifies an exact amount, OUR charging avoids disputes about whether the full invoice was paid. SWIFT payment charges range from bank to bank but typically include a flat wire fee plus potential correspondent bank fees.
At home
Alternatives to SWIFT are emerging for specific corridors: Ripple's payment network, SWIFT alternatives built on distributed ledger technology, and direct central bank connections (like the EU's TARGET2 system for euro payments, or India's UPI). Fintech services (Wise, formerly TransferWise) bypass the correspondent banking chain by holding local accounts in many countries and settling through local payment networks rather than SWIFT, offering faster and cheaper international transfers for individuals and SMBs.
At work
ISO 20022 is the new SWIFT messaging standard replacing the older MT message formats. Major currencies (SEPA, US Fedwire, UK CHAPS, and others) are migrating to ISO 20022 through the mid-2020s. ISO 20022 messages carry dramatically richer payment data: full remittance information, regulatory identifiers, and structured address data. This data richness enables better AML screening, fewer payment delays from compliance queues, and better reconciliation at the recipient end. Financial institutions and corporates need to update payment systems to generate and consume ISO 20022 data by the migration deadlines.
Real-world examples
At home
Carlos was freelancing for a US company while living in Portugal. His client initiated a wire transfer through their US bank to his Portuguese IBAN. The payment used SWIFT to send the instruction from the US bank to his Portuguese bank. The transfer took three days and arrived with a correspondent bank fee deducted. He later set up a Wise account to receive future payments faster and without correspondent bank fees.
At work
Sophie managed accounts payable for a manufacturing company that purchased components from suppliers in Germany, Taiwan, and South Korea. She worked with treasury to establish SWIFT wire templates for each supplier with pre-validated BIC codes and IBANs. Using OUR fee instructions for vendor payments ensured suppliers received the exact invoice amount, avoiding disputes. She also used SWIFT GPI reference numbers to track payment status and provide suppliers with estimated arrival dates.
Common confusions
- Many people think SWIFT transfers money directly and instantly — SWIFT sends a payment message -- an instruction. The actual movement of money happens through correspondent banking relationships (accounts that banks hold with each other) and can involve multiple steps across different countries and time zones. This is why international wires take days rather than seconds. SWIFT GPI adds tracking but doesn't speed up the underlying settlement process, which is constrained by bank processing hours and cut-off times in each jurisdiction.
- Some assume SWIFT codes and IBANs are the same thing — A SWIFT code (BIC) identifies a bank: BOFAUS3N identifies Bank of America in the US. An IBAN (International Bank Account Number) identifies a specific account at a specific bank: GB29NWBK60161331926819 identifies a particular account at NatWest in the UK. When making an international payment, you typically need both: the SWIFT code to identify the destination bank and the account number (IBAN or local account number) to identify the specific account within that bank.
For analysts
When a client is building international payment workflows (supplier payments, payroll for global employees, client invoicing in multiple currencies), SWIFT friction points to assess are: correspondent bank fee uncertainty (who pays, and how much), payment tracking capability (can they see where a payment is in the chain), cut-off times (wire submissions must reach the bank before daily cut-off), and FX rate timing (when is the exchange rate locked in?). Identifying these pain points informs whether SWIFT direct banking, a fintech intermediary (Wise Business, Airwallex), or a payment platform is the right solution for the client's volume and geography.
History & origin
Before SWIFT, international banks communicated by Telex -- a slow, expensive, and error-prone system with no standardized format, making international wire transfers difficult and fraud-prone. SWIFT was established in 1973 by a consortium of European and North American banks as a cooperative to build a secure, standardized messaging network. It launched in 1977 and rapidly displaced Telex for interbank communication. SWIFT's messaging standards (MT -- Message Type formats, later evolved to ISO 20022) became the global standard for payment messaging. SWIFT gained global political significance when Western governments used disconnection from SWIFT as a financial sanction: Iranian banks were disconnected (2012) and Russian banks following the 2022 Ukraine invasion -- demonstrating that SWIFT access is de facto infrastructure for participation in the global financial system.