Most people run into a SWIFT code for the first time when a form demands one — a string like CHASUS33 or HSBCHKHH that they copy-paste without really understanding. So if you are asking what are SWIFT codes used for, the short answer is simple: they identify a specific bank and branch so that money — and the payment messages that move it — can be routed across borders accurately. The longer answer is that this single 8- or 11-character code sits underneath almost every cross-border payment in the world, from a $50 family remittance to a $500 million corporate settlement.
This article breaks down the eight real-world uses of SWIFT codes, walks through three concrete case studies with numbers, and lays out the data on how much the SWIFT network actually moves — so you can see exactly where a BIC fits into the global payment stack.
Quick recap
A SWIFT code (also called a BIC, Business Identifier Code) identifies a bank, not an account. An IBAN identifies the account. For most cross-border payments you need the SWIFT code plus an account number or IBAN together. If you need a refresher on the structure first, read our companion guide: What Is a SWIFT Code?
1. Personal international wire transfers
The most familiar use case. When you send money from your bank in one country to someone's bank in another, your bank needs the recipient bank's SWIFT code to address the payment message on the SWIFT network. The recipient also typically needs to give their bank's SWIFT code to whoever is paying them.
This is what powers a wire from a US account to a German supplier, a gift to a relative in India, or tuition payment to a university in the UK. According to SWIFT's own published figures, the network links more than 11,000 financial institutions across 200+ countries and territories and carries on the order of 45+ million messages per day. The vast majority of those messages are payment instructions that depend on a BIC for routing.
2. Getting paid as a freelancer or contractor
Platforms like Upwork, Deel, Payoneer, Remote, and Deel all ask for your bank's SWIFT code when you add an international payout method. The SWIFT code tells the platform's payout processor which bank to credit; your account number or IBAN tells that bank which account to credit.
This matters more than it sounds: a single wrong character in a SWIFT code can route a freelancer's $2,000 monthly payment to the wrong intermediary, triggering a recall that takes 1–4 weeks. Verifying the BIC against the bank's official listing — or with a free SWIFT/BIC lookup — before submitting it to a platform is one of the highest-leverage things a freelancer can do.
3. B2B supplier and invoice payments
For businesses importing goods or paying overseas vendors, SWIFT wires are still the default for amounts above a few thousand dollars. A Chinese manufacturer invoices a US buyer with its bank name, SWIFT code, and account number; the buyer's treasury team sets up the wire in their banking portal; the payment hops through 1–3 correspondent banks before landing.
The SWIFT code here serves a second purpose beyond routing: it is part of the buyer's AP (accounts payable) validation. Most finance teams will not approve a new vendor payment until the BIC, bank name, and country in their vendor record all match — a control designed to catch supplier-invoice fraud and business email compromise.
4. E-commerce and marketplace payouts
Sellers on Amazon, Shopify Payments, Etsy, and Stripe specify a payout bank account, and for cross-border sellers that means providing a SWIFT code. A seller in Vietnam selling on Amazon US, for example, receives USD payouts via a SWIFT wire to a Vietnamese bank — the BIC tells Amazon's payment processor which Vietnamese bank to reach.
Because marketplace payouts are recurring and often large, an incorrect or outdated SWIFT code is a leading cause of "missing payout" support tickets. If the BIC is wrong the funds usually bounce back after 3–7 days, costing the seller a month of cash flow.
5. Expatriate remittances
Remittances — money sent home by people working abroad — are one of the largest financial flows on Earth. The World Bank estimates global remittances to low- and middle-income countries reached roughly $650 billion in 2023, and total cross-border remittances (including high-income destinations) exceeded $800 billion. A meaningful share of those still move over the SWIFT network, especially bank-to-bank transfers.
The 6.2% average cost is the reason services like Wise have grown so fast — they route money differently to stay near the real mid-market exchange rate instead of stacking correspondent-bank fees.
Affiliate disclosure: this is a referral link — using it may earn ibantool.com a small commission at no extra cost to you.
6. NGO and charity disbursements
International NGOs use SWIFT wires to move funds to field offices and partner organizations in countries where local payment rails are limited. A humanitarian grant disbursed from Geneva to a partner bank in Nairobi requires the Nairobi bank's SWIFT code; the same is true for emergency cash transfers after a natural disaster.
Because NGO payments are often audited, the SWIFT code also functions as an evidence trail — the BIC proves exactly which bank and branch received the funds, which matters for donor reporting and sanctions compliance.
7. Treasury and interbank settlements
Behind the scenes, banks use SWIFT messages (the MT 202 and MT 202COV cover messages, and the newer ISO 20022 pacs.009) to settle with each other. When your bank sends a wire, it rarely delivers the money directly — it uses a correspondent bank that holds an account at the destination bank. Each leg of that chain is addressed with SWIFT codes.
This is why a single $500 personal wire can pass through 2–3 intermediaries: the sending bank, a correspondent bank, and the receiving bank. Each intermediary takes a small fee, which is the structural reason SWIFT wires cost $25–45 outbound plus $10–30 in correspondent fees on top.
8. Bank identity verification (KYB / AML)
The last use case is non-payment: Know-Your-Business and anti-money-laundering checks. When a fintech onboards a new corporate customer, or when a bank screens a counterparty, it validates the counterparty's bank by matching the BIC against the SWIFT directory. A valid BIC that resolves to a real bank name, country, and branch is a basic signal that the receiving bank exists and is regulated. A BIC that does not resolve — or resolves to a different bank than the one named on the invoice — is a red flag for invoice fraud.
This is also why many vendor-onboarding forms ask for the bank's SWIFT code even when the first payment is small: it lets the finance team confirm bank details before money moves.
Case study 1: A freelancer in Brazil paid by a US client
Marina, graphic designer, São Paulo → US$4,000 monthly retainer
Marina invoices a US agency monthly. The agency's AP portal asks for her bank's SWIFT code, her account number, and her bank's address. Marina's bank is Itaú, whose primary BIC is ITAUBRSP. She enters it along with her branch account number and waits.
What happens under the hood: the agency's US bank sends a SWIFT MT103 message addressed to ITAUBRSP. The message routes through a US correspondent bank (often JPMorgan, CHASUS33) and a Brazilian correspondent before reaching Itaú, which credits Marina's BRL account after an FX conversion.
The numbers: a typical bank SWIFT wire for this route costs the sender ~$35 outbound, correspondent banks take ~$15, and the FX markup is ~3%. On a $4,000 payment, Marina receives roughly $4,000 − $35 − $15 − $120 (FX) ≈ $3,830. The same payment through a service like Wise typically arrives with total fees around $20–30 and near-mid-market FX — saving Marina ~$100 per month, or ~$1,200 per year.
The lesson: the SWIFT code itself is not the expensive part — the correspondent-bank chain and FX markup are. Knowing the BIC is necessary, but choosing the rail is where the money is.
Case study 2: A UK e-commerce seller paying a Chinese supplier
James, Shopify seller, Manchester → ¥58,000 ($8,000) purchase order
James orders $8,000 of inventory from a manufacturer in Shenzhen. The supplier's proforma invoice lists Bank of Communications, SWIFT COMMCNSH, and a 21-digit CNAPS account number. James sets up the wire in his UK bank's business portal.
What can go wrong: James almost pastes the SWIFT code for Bank of Communications' Beijing head office (COMMCNBJ) instead of the Shanghai branch (COMMCNSH) listed on the invoice. Both are valid BICs for the same bank, but using the wrong branch code can add 2–3 days of internal rerouting at the Chinese bank. James catches it by decoding the BIC with the SWIFT/BIC lookup before submitting.
The numbers: the UK bank charges £25 outbound, the intermediary takes ~$20, and the supplier's bank applies its own fee. The payment lands in 3 business days. If James had used the wrong branch BIC, the supplier would likely have shipped 3–5 days late, risking a stockout that would have cost far more than the wire fee.
The lesson: for B2B supplier payments, matching the exact branch BIC on the supplier's invoice is a cheap insurance policy against delayed shipment.
Case study 3: An expat sending money home to the Philippines
Pia, nurse in Dubai → PHP 30,000 (~$540) monthly to her family
Pia supports her family in Manila. She has two options: a bank SWIFT wire from her UAE bank to a Philippine bank (BPI, PIBPPHMM), or a specialist remittance service.
The numbers: the Philippines is one of the world's largest remittance-receiving countries — the World Bank estimates remittances into the Philippines at roughly $37 billion in 2023, equal to around 8–9% of GDP. The average cost to send $200 to the Philippines from the Gulf is around 3.0–3.5% via specialist services, but a bank SWIFT wire can cost 5–7% once FX markup is included.
For a $540 monthly transfer, the difference is real:
| Rail | Upfront fee | FX markup | Family receives (approx.) |
|---|---|---|---|
| Bank SWIFT wire | ~$20 | ~4% | ~$500 |
| Specialist remittance | ~$5–10 | ~1% | ~$525 |
The lesson: SWIFT wires are reliable but expensive for small recurring remittances. For amounts under ~$1,000, a specialist service routing near the mid-market rate usually leaves 3–5% more in the recipient's pocket — over a year, that is hundreds of dollars per family.
Where SWIFT codes fall short
SWIFT codes solve the addressing problem (which bank), but they do not solve every problem in cross-border payments:
- Cost. The correspondent-bank chain adds $10–45 in layered fees plus FX markup. The World Bank's 6.2% global average remittance cost is well above the UN Sustainable Development Goal target of 3%.
- Speed. SWIFT wires take 1–5 business days. SEPA Instant, FPS, and FedNow settle in seconds for domestic and some cross-border corridors.
- Transparency. Senders often do not know how much the recipient will actually get until the wire lands, because correspondent-bank fees are deducted along the way.
- No account validation. A correct SWIFT code does not mean the account exists. That is what IBAN MOD 97 check digits partially solve — you can validate an IBAN's format with our IBAN validator, but only the receiving bank can confirm the account is open.
How to find the right SWIFT code fast
For any of the eight use cases above, the practical question is the same: how do you get the right BIC quickly? Three reliable paths:
- Bank statement or app. Most banks show their own SWIFT code on the account-details page.
- Bank's website. Look for a page titled "international payments" or "BIC/SWIFT." This is the most authoritative source.
- Free lookup tool. Our SWIFT/BIC code lookup lets you search by bank name and country, or paste any 8/11-character BIC to decode it into bank, country, location, and branch — all in your browser.
Decode any SWIFT code in one click
Search 50+ major banks or paste any 8/11-character BIC. Free, private, runs in your browser — no signup.
Open SWIFT/BIC lookup →FAQ
- What are SWIFT codes used for?
- SWIFT codes (BICs) are used to identify a specific bank and branch in international payments. They route cross-border wire transfers, freelancer and contractor payouts, B2B supplier payments, marketplace payouts, remittances, charity disbursements, interbank settlements, and bank-identity verification (KYB). Any time money or a payment message needs to reach a bank in another country, a SWIFT code is typically required.
- Do I need a SWIFT code for a domestic transfer?
- Usually no. Domestic transfers typically use a national routing system instead: ABA routing numbers in the US, sort codes in the UK, BSB codes in Australia, IFSC in India, CNAPS in China. SWIFT codes are mainly for cross-border payments. A few banks ask for a SWIFT code even domestically, but that is rare.
- How long does a SWIFT transfer take?
- A typical SWIFT wire takes 1 to 5 business days. The speed depends on the currency, the number of correspondent banks in the chain, compliance checks, and time zones. EUR SEPA payments are usually same-day or next-day; USD wires to non-US banks often take 2 to 4 business days.
- How much does a SWIFT transfer cost?
- Outbound SWIFT wires from US and European banks typically cost $25 to $45, plus correspondent bank fees of $10 to $30 and an FX markup of 2% to 4% when converting currency. According to World Bank data, the global average cost of sending remittances was around 6.2% in 2024 — well above the UN Sustainable Development Goal target of 3%.
- Can a SWIFT code be used to verify a bank's identity?
- Yes. SWIFT/BIC codes are used in Know-Your-Business (KYB) and anti-money-laundering (AML) checks to confirm that a counterparty's bank is a real, registered institution. Matching a BIC against the SWIFT directory helps confirm the bank's name, country, and branch before a payment is approved.
Bottom line
So what are SWIFT codes used for? They are the addressing layer under nearly every cross-border payment — personal wires, freelancer payouts, B2B supplier payments, marketplace settlements, remittances, NGO disbursements, interbank settlements, and bank-identity verification. Knowing the right BIC is the price of admission; the bigger savings come from choosing the right rail for the amount and corridor you are sending.
If you have a BIC in hand and want to confirm it, decode it with our free SWIFT/BIC code lookup. If you are sending to an IBAN country, validate the account number format first with the IBAN validator. Both tools run entirely in your browser — no signup, no data uploaded.