Table of Contents
- What SWIFT Is and How It Fits Into Global Banking
- A Brief History of SWIFT
- How SWIFT Payments Work: The Step-by-Step Process
- What a SWIFT Code Is and How It Works
- SWIFT Message Types: MT and ISO 20022
- The Role of Correspondent Banks in SWIFT Transfers
- Who Uses SWIFT and Who Owns It
- SWIFT Fees: What It Actually Costs to Send a Payment
- SWIFT and Compliance: AML, Sanctions, and KYC
- Why SWIFT Is Slow for African Businesses
- Alternatives African Businesses Use Instead of SWIFT
- How HoneyCoin Closes the SWIFT Gap for African Businesses
- Final Thoughts on How SWIFT Payments Work
- FAQ
- How does the SWIFT payment process actually work, step by step?
- Why is SWIFT so expensive and slow for business payments between African countries like Nigeria, Kenya, and Ghana?
- SWIFT vs stablecoin rails vs PAPSS: which one should African businesses use for cross-border payments?
- What is an MT103 SWIFT message and when does your bank send one?
- How do I move money across African markets without routing through SWIFT's correspondent chain?
Do not index
SWIFT payments work great if you're moving money between New York and Frankfurt. For businesses operating across African markets, the story gets more complicated fast. The fees stack up, the delays stretch out, and the routing often makes little logical sense. Here's a clear look at how SWIFT payments actually work and why the system creates so much friction for African businesses in particular.
TLDR:
- SWIFT is a messaging network, not a money mover. It sends payment instructions; banks settle the funds separately.
- Your payment can clear SWIFT in under an hour, yet still take 2 to 7 days to land due to compliance queues and cut-off windows.
- Sending USD 200 to Sub-Saharan Africa averaged 8.78% in fees in Q1 2025, well above the 6.49% global average.
- Intra-African payments often route through London or New York first, because direct correspondent relationships between African markets are thin.
- HoneyCoin is a financial services aggregator that settles across 22+ African markets via local rails, bypassing the correspondent chain entirely.
What SWIFT Is and How It Fits Into Global Banking
SWIFT stands for Society for Worldwide Interbank Financial Telecommunication. Founded in 1973 and headquartered in La Hulpe, Belgium, it connects over 11,000 financial institutions across more than 200 countries and territories.
The most common misconception is that SWIFT moves money. It does not. SWIFT is a secure messaging network that carries payment instructions between banks. The actual movement of funds happens through correspondent banking relationships and local settlement systems.
When your bank sends a SWIFT message, it transmits a standardized instruction: who is paying, who is receiving, how much, in what currency, and why. The receiving bank then acts on that instruction through its own settlement processes. That distinction matters, especially for businesses trying to understand why a "sent" payment can still take days to arrive.
A Brief History of SWIFT
Before SWIFT, banks sent international payment instructions by telex, a system that was slow, error-prone, and relied on manual verification of sender identities. A group of 239 banks across 15 countries decided to fix this, and in 1973, SWIFT was formally registered in Brussels as a member-owned cooperative.
The network went live in 1977, replacing telex with a standardized, encrypted messaging format. That cooperative structure was a deliberate choice: no single government or commercial entity would control it. Member banks collectively own and govern it, which is partly why the system has proven so durable across decades of geopolitical change.
The architecture built in the 1970s was designed for a world of mainframes and business-hours banking. It was never rebuilt from scratch; it evolved through layers of added standards and protocols on top of its original foundation, which explains much of the friction businesses experience today.
How SWIFT Payments Work: The Step-by-Step Process
When you instruct your bank to send funds internationally, your bank creates a SWIFT message, typically an MT103 for a single customer credit transfer, containing sender details, recipient details, amount, currency, and purpose code. That message is encrypted and transmitted over the SWIFT network to the next bank in the chain.
Here is what the flow looks like:

- Your bank generates and sends the SWIFT message
- If your bank has no direct relationship with the recipient's bank, one or more correspondent banks relay the instruction
- Each correspondent bank debits and credits accounts along the chain
- The recipient's bank receives the final instruction and credits the beneficiary's account
The distinction worth noting is between network time and total settlement time. SWIFT's own data shows 75% of payments reach the beneficiary bank within 10 minutes, and over 90% arrive within one hour. But that clock measures only the "in-flight" leg, which on average represents less than 20% of the total end-to-end journey. The remaining time is spent on compliance checks, cut-off windows, currency conversion, and the recipient bank's own posting processes.
What a SWIFT Code Is and How It Works
A SWIFT code is formally called a Business Identifier Code (BIC). Every financial institution on the SWIFT network has one, and it functions like a routing label for the bank itself.
The code is either 8 or 11 characters long:
- Characters 1 to 4: Bank code that identifies the institution
- Characters 5 to 6: Country code in ISO 2-letter format, e.g., "KE" for Kenya
- Characters 7 to 8: Location code for the city or region
- Characters 9-11: Branch code, optional; "XXX" typically indicates the primary office
For example, a BIC of KCBLKENXXXX points to KCB Bank in Kenya at its primary branch. When your bank transmits a SWIFT message, the BIC tells the network exactly where to route it.
One point worth clarifying: a SWIFT code identifies the bank, while an IBAN (International Bank Account Number) identifies the specific account within that bank. Some corridors, particularly in East Africa and parts of Asia, do not use IBAN at all, so recipient account details must be structured differently depending on the destination country.
SWIFT Message Types: MT and ISO 20022
SWIFT messages come in two format families. The older one, MT (Message Type), has been the backbone of interbank communication since the 1970s. The newer one, ISO 20022, became the global standard for cross-border payments after the SWIFT coexistence period ended in November 2025.
The MT format organizes messages by number. The one most businesses encounter is the MT103, which handles single customer credit transfers. A simplified MT103 looks roughly like this:
:20:Transaction reference number
:32A:Value date, currency, and amount (e.g., 261015USD5000,00)
:50K:Ordering customer (sender name and account)
:57A:Account with institution (recipient's bank BIC)
:59:Beneficiary (recipient name and account number)
:70:Remittance information (payment purpose or invoice reference)
:71A:Who bears the charges (OUR, BEN, or SHA)
ISO 20022 carries richer, more structured data in the same instruction. Where an MT103 compresses location details into a free-text field, ISO 20022 uses defined fields for street, city, and postal code separately, reducing compliance friction and manual intervention downstream.
The Role of Correspondent Banks in SWIFT Transfers
Correspondent banks sit between your bank and the recipient's bank when no direct relationship exists. The SWIFT network relies on a web of bilateral agreements to move funds across that chain.
The mechanism runs on two account types. A nostro account is your bank's account held at a foreign bank, in that bank's local currency. A vostro account is the same relationship seen from the other side.
For African corridors, direct bilateral relationships are relatively thin. A payment from Nairobi to Lagos often routes through London or New York first, because that is where deep correspondent relationships sit. Each hop adds a fee and its own compliance checks. Sub-Saharan Africa transfer costs averaged 8.78% of the transaction value in Q1 2025, in part because fees accumulate at each intermediary stop.
Who Uses SWIFT and Who Owns It
SWIFT is a cooperative owned collectively by its member financial institutions. No single government, central bank, or private company controls it. Member banks govern it through a board of directors, with representation weighted toward larger financial centers, particularly in Europe and the US.
Membership is open to several institution types:
- Commercial banks and central banks
- Broker-dealers and money brokers
- Non-bank financial institutions and custodians
The cooperative model has kept SWIFT politically neutral for decades, though that neutrality has limits. The exclusion of certain Russian banks in 2022 showed that geopolitical pressure can influence access, with those decisions coordinated through member governments and not through SWIFT's own governance.
SWIFT Fees: What It Actually Costs to Send a Payment
Sending a SWIFT payment involves several distinct fee layers, and most businesses only see one of them on their bank statement.
- SWIFT network fees: SWIFT charges member banks for connectivity and per-message transmission, and banks pass these along, usually bundled into the wire fee.
- Sending bank wire fee: typically a flat charge ranging from $15 to $50 per transfer, depending on the institution and the destination.
- Correspondent bank lift fees: each intermediary bank deducts its own processing charge, often $10 to $25, directly from the transfer amount.
- Foreign exchange (FX) markup: when currency conversion is involved, banks apply a spread on top of the mid-market rate. This is usually where the largest cost sits, and it rarely appears as a visible line item.
Three fee allocation codes govern who absorbs those charges. OUR means the sender covers all fees, so the beneficiary receives the full amount. SHA splits it: the sender pays their own bank's fees, while correspondent and recipient bank fees come out of the transferred amount. BEN puts all charges on the beneficiary.
SHA is the most common code in practice. For African recipients, that matters because multi-hop routing through London or New York means multiple lift fees, each quietly reducing the final credit.
SWIFT and Compliance: AML, Sanctions, and KYC
Every SWIFT message passes through a compliance layer before it moves. Banks screen each transaction against anti-money laundering (AML) rules, international sanctions lists, and their own internal risk thresholds. When a flag is triggered, the payment pauses, sometimes for hours, sometimes for days, while compliance staff review it manually.
Three checks happen at every bank in the chain:
- Know Your Customer (KYC) verification on both the sender and recipient
- Sanctions screening against lists including OFAC, EU, and UN designations
- AML transaction monitoring for unusual patterns or amounts
The problem compounds with each correspondent hop. A payment routed through two intermediary banks gets screened two additional times, and any one of those checks can freeze the transfer. SWIFT's Customer Security Programme (CSP) adds another layer, requiring member banks to meet baseline cybersecurity controls or risk having messages rejected by counterparties.
For corridors like Nigeria–Kenya or Ghana–South Africa, false positives are a recurring practical headache. Thin correspondent relationships mean more hops, and more hops mean more screening. A legitimate supplier payment can sit in a compliance queue simply because the recipient country or institution carries a high-risk profile in a foreign bank's model.
Why SWIFT Is Slow for African Businesses
SWIFT's network leg is fast. The structural reality for African businesses is not.

Most intra-African corridors have no direct correspondent path. A transfer from Nairobi (Kenya) to Lagos (Nigeria) typically routes through London or New York first, because that is where the bilateral relationships exist. Each extra hop adds fees, compliance queues, and cut-off windows, making settlement windows of 2 to 7 days routine for these routes.
Cost tells the same story. As noted earlier, fees for Sub-Saharan Africa corridors averaged 8.78% in Q1 2025, nearly double the UN SDG 10.c target of 3% by 2030. The architecture was built around corridors that matter to European and US banks. African corridors were never the design priority, which is part of why fintech payment infrastructure in Africa has developed around alternative rails.
Alternatives African Businesses Use Instead of SWIFT
When SWIFT's cost structure or routing delays make a corridor unworkable, finance teams across Africa have a few practical routes they use instead.
Mobile money networks are the most widely used alternative for intra-African transfers at smaller values. M-Pesa, MTN Mobile Money, and Airtel Money all operate their own rails, settling directly through local telecom infrastructure and bypassing correspondent bank chains entirely. They are fast and accessible, but coverage is fragmented: a payment that works inside Kenya may hit a dead end the moment it crosses into a market where the recipient network has no interoperability agreement, a gap that approaches to mobile money and bank rail integration are designed to close.
PAPSS, the Pan-African Payment and Settlement System, takes a different approach. Launched by the African Export-Import Bank (Afreximbank), it lets African currencies settle directly with each other, bypassing USD or EUR as an intermediary. Its network of participating banks continues to grow, but for corridors it does cover, it cuts out the London or New York hop entirely.
Stablecoin infrastructure for cross-border trade, USDC and USDT rails in particular, has gained serious traction among fintechs and treasury teams managing high-value cross-border flows. A business can convert local fiat to a dollar-pegged stablecoin, move it across chains without a correspondent bank in the middle, and off-ramp on the other end in minutes, not days, an approach covered in this guide to sending USDC across Africa via API.
Rail | Settlement speed | Best fit |
Mobile money (M-Pesa, MTN, Airtel) | Minutes | Low-value intra-African retail |
PAPSS | Same day (where live) | African currency-to-currency B2B |
Stablecoin (USDC/USDT) | Minutes | High-value cross-border, treasury |
SWIFT | Hours to days | USD/EUR correspondent corridors |
How HoneyCoin Closes the SWIFT Gap for African Businesses
HoneyCoin was built for exactly the structural problem this article describes. Instead of routing through SWIFT's correspondent chain, HoneyCoin coordinates settlement across 22+ markets — including Kenya, Nigeria, Ghana, Tanzania, and Uganda — by connecting directly to 50+ mobile money providers and 200+ banks over local rails. Your business can move funds without accumulating multi-hop correspondent fees or sitting in a foreign compliance queue, as covered further in this roundup of NALA alternatives for African businesses.
For high-volume foreign exchange (FX), the OTC Desk delivers same-day (T+0, meaning settlement on the same business day) settlement at competitive rates. For enterprises and fintechs needing stablecoin payments infrastructure for Africa, the Minting product converts fiat to USDC or USDT via bank or mobile money across Ethereum, Arbitrum, Base, Polygon, BSC, and Optimism. Wallets as a Service (WaaS) — where the enterprise owns KYC, ledger, and compliance — lets banks and fintechs issue branded stablecoin wallets without building blockchain infrastructure themselves, complementing the USDC payment API for Africa for teams embedding settlement directly.
HoneyCoin is a financial services aggregator, not a bank, delivering African payment processing across all rails. It holds four licenses: a MiCA license (Czech Republic), an MSB license (Canada), a PSP license (Canada), and a PSP license (Rwanda).
Final Thoughts on How SWIFT Payments Work
Most of the friction your business feels with international transfers has nothing to do with SWIFT's network speed. It comes from the correspondent chain sitting underneath it. Understanding that structure puts you in a better position to ask the right questions and choose the right tools for each payment corridor you run.
FAQ
How does the SWIFT payment process actually work, step by step?
SWIFT carries payment instructions between banks; it does not move money itself. Your bank creates a SWIFT message (typically an MT103 for a single customer credit transfer), transmits it over the network, and one or more correspondent banks relay it until the recipient's bank receives the instruction and credits the account. The SWIFT network leg is fast (over 90% of messages arrive at the beneficiary bank within an hour), but compliance checks, correspondent bank cut-off windows, and currency conversion at each hop extend total end-to-end settlement to 2 to 7 days for many African corridors.
Why is SWIFT so expensive and slow for business payments between African countries like Nigeria, Kenya, and Ghana?
Most intra-African corridors have no direct correspondent banking path, so a payment from Nairobi to Lagos typically routes through London or New York first, and each hop adds a lift fee and its own compliance queue. Sending USD 200 to Sub-Saharan Africa averaged 8.78% of transaction value in Q1 2025, well above the global average of 6.49%, because the architecture was built around European and US corridors and African routes were never the design priority. Finance teams at African businesses regularly absorb multi-hop correspondent fees, false-positive compliance holds, and multi-day settlement windows simply because the rails they are forced onto were not built for them.
SWIFT vs stablecoin rails vs PAPSS: which one should African businesses use for cross-border payments?
SWIFT still makes sense for USD or EUR correspondent corridors where your bank has direct relationships, but for intra-African flows it is the most expensive and slowest option available. PAPSS settles African currencies directly with each other, cutting out the USD intermediary hop entirely, but its participating bank network is still growing, so coverage depends on your specific corridor. Stablecoin rails (USDC/USDT) have become the practical choice for high-value cross-border flows and treasury management, settling in minutes across chains like Ethereum, Arbitrum, and Base, with no correspondent bank in the middle.
What is an MT103 SWIFT message and when does your bank send one?
An MT103 is the standard SWIFT message type used for single customer credit transfers; it is what your bank generates when you instruct an international wire. It contains the sender's details, recipient's bank BIC (Business Identifier Code), account number, amount, currency, value date, and a field indicating who bears the charges (OUR, SHA, or BEN). Understanding the SHA charge code matters in practice: it means correspondent and recipient bank fees are deducted from the transferred amount, so African recipients on multi-hop routes often receive less than the amount sent.
How do I move money across African markets without routing through SWIFT's correspondent chain?
You need payment infrastructure built on local rails, not correspondent banking. Mobile money networks like M-Pesa, MTN Mobile Money, and Airtel Money settle directly through local telecom infrastructure, but interoperability across borders is fragmented. For businesses managing treasury or high-volume payouts across multiple African countries, API-first aggregators like HoneyCoin connect directly to 50+ mobile money providers and 200+ banks across 22+ markets, with an OTC desk offering same-day (T+0) settlement and stablecoin on/off-ramps for USDC and USDT, so your payment never needs a London hop to reach Lagos or Accra.

