Table of Contents
- What B2B Cross-Border Payments Are
- How B2B Cross-Border Payments Work
- Payment Methods Used in B2B Cross-Border Transactions
- The African Context: Why Cross-Border B2B Payments Work Differently Here
- Common B2B Cross-Border Payment Challenges
- Types of Cross-Border Payments: Wholesale vs. Retail vs. B2B
- FX Risk and Currency Management in Cross-Border Transactions
- Regulatory and Compliance Requirements for B2B Cross-Border Payments
- Stablecoins as a B2B Payment Rail for African Businesses
- How to Choose a Cross-Border B2B Payments Provider
- Geographic coverage and rail depth
- Settlement speed
- FX (foreign exchange) transparency
- Compliance infrastructure
- API quality and integration effort
- Pricing structure
- Multi-Currency Treasury Management Across African Markets
- How HoneyCoin Supports B2B Cross-Border Payments Across Africa
- Final thoughts on Cross-Border B2B Payment Solutions for African Businesses
- FAQ
- What's the difference between using SWIFT and mobile money rails for B2B cross-border payments across Africa?
- OTC desk vs stablecoin rails for high-volume B2B payments in Africa: which makes more sense?
- How do I integrate mobile money and bank rails into a single payments API for Africa?
- What tools should I use to manage multi-currency treasury across African markets like Kenya, Nigeria, and Ghana?
- What is a cross-border B2B payment, and how does it differ from a consumer remittance?
Do not index
Running a business across African borders means your finance team is constantly dealing with fragmented rails, FX volatility, and compliance requirements that change by country. A payout method that works in Kenya may need a completely different integration in Uganda, and your correspondent bank isn't rushing to tell you how much they're taking along the way. Here's a clear look at how cross-border B2B payments work across Africa and what actually moves the needle on cost and speed.
TLDR:
- According to the South African Reserve Bank, sending USD 200 to sub-Saharan Africa cost 8.78% on average in Q1 2025 (a regional average that varies by corridor), against a 6.49% global average.
- Transfers advertised as free often hide an FX (foreign exchange) spread inside the exchange rate, visible only at reconciliation.
- Stablecoins like USDC reduce currency conversion steps on NGN and GHS corridors where correspondent banking adds cost and delay.
- Each new African corridor requires its own KYB (know your business) documentation; your compliance posture from Lagos does not transfer to Nairobi.
- HoneyCoin is a financial services aggregator covering mobile money, Virtual Accounts, stablecoin on/off-ramps, and an OTC Desk across 24+ markets.
What B2B Cross-Border Payments Are
Business-to-business (B2B) cross-border payments are transactions where one business sends money to another business in a different country. A Kenya-based importer paying a supplier in China, a Nigerian SaaS company settling contractor invoices in Ghana, or a logistics firm running payroll across five African markets are all real examples of this.
The key distinction from consumer remittances is purpose and scale. B2B transactions carry commercial obligations: supplier invoices, service contracts, trade settlements, and bulk payroll. The amounts are larger and the documentation requirements more demanding.
These payments flow through several channels, including bank wire transfers, mobile money networks, card rails, or stablecoins, each with different speeds, costs, and currency support depending on the corridor.
How B2B Cross-Border Payments Work
When a business initiates a cross-border payment, the money rarely travels in a straight line. Most transactions pass through multiple institutions before reaching the recipient's account.
Here's the typical flow:
- The sending business instructs their bank or payment provider to initiate a transfer.
- If no direct relationship exists with the recipient's bank, a correspondent bank steps in as an intermediary.
- The correspondent bank converts the currency and routes the funds through its own network.
- The receiving institution credits the final account in local currency.
Each hop in that chain introduces a fee, an exchange rate margin, and a potential delay. Correspondent banking relationships are not universal, so payments to some African corridors may route through two or three intermediaries before settling. That's where transit time stretches from hours into days, and where value disappears in foreign exchange (FX) spreads and intermediary charges. The sending institution holds counterparty risk at each leg until final settlement confirms.
Payment Methods Used in B2B Cross-Border Transactions
Several rails exist for moving money between businesses across borders. Each carries different trade-offs depending on your corridor, volume, and how fast you need funds to land.
Method | Speed | Relative Cost | Suited For |
SWIFT wire | 2 to 5 days | High | Large, bank-to-bank transfers |
ACH / SEPA | 1 to 3 days | Low | US and EU corridors |
Mobile money | Minutes to hours | Medium | Payouts between markets like Kenya, Uganda, and Ghana |
Virtual accounts | Real-time to 1 day | Low-medium | Collections in local currency |
Commercial cards | Same day | Medium-high | Ad spend, subscriptions |
Stablecoins (USDC/USDT) | Minutes | Low | FX-volatile corridors |
PSPs / aggregators | Hours to 1 day | Variable | Multi-rail, multi-market coverage |
SWIFT transfer timing remains the default for large institutional transfers, but its correspondent banking chain adds fees at every hop. Mobile money networks fill the gap across Africa where banking penetration is uneven. Stablecoins are gaining ground on corridors where local currencies face volatility or where settlement speed matters more than familiarity. Payment service providers (PSPs) that aggregate multiple rails give finance teams a single integration point across methods.
The African Context: Why Cross-Border B2B Payments Work Differently Here
In Kenya, Uganda, and Ghana, mobile money is a core payment rail. On corridors like Kenya to Uganda or Ghana to Uganda, M-Pesa, MTN MoMo, and Airtel Money can often move funds faster than a bank wire. Yet the infrastructure connecting these networks across borders remains fragmented. A payout that works in Kenya might require a completely different integration in Uganda, and the two systems rarely talk to each other natively, which is why merging mobile money and bank rails into one API matters.

The banking layer compounds this. Many African markets have limited correspondent banking relationships, meaning a payment from Lagos to Accra may route through London or New York before landing in Ghana. That detour costs money and time, a recurring theme in cross-border payments across high-growth markets. According to the South African Reserve Bank, the average cost of sending USD 200 to sub-Saharan Africa in Q1 2025 was 8.78%, against a global average of 6.49%. For businesses moving serious volumes, that gap compounds fast.
Currency risk adds another layer. Corridors involving the Nigerian naira (NGN) or Ghanaian cedi (GHS) carry meaningful foreign exchange (FX) volatility. A supplier invoice priced in USD, settled days later, can land at a materially different value than what either party agreed to, before factoring in the spread a correspondent bank quietly takes along the way.
Common B2B Cross-Border Payment Challenges
Most of these challenges are not new. They're persistent enough that finance teams have started treating them as the cost of doing business internationally.
Settlement delays are the most visible problem. Payments traveling through correspondent banking chains can take 2 to 5 days to clear, creating real cash flow strain for businesses managing supplier relationships across multiple countries at once.
Foreign exchange (FX) fees are often less visible. Many providers advertise a free transfer and embed their margin inside the exchange rate. A business moving USD 50,000 from Kenya to Nigeria may not realize it absorbed a spread until reconciliation, if it notices at all.
Know Your Business (KYB) checks, local documentation standards, and anti-money laundering (AML) requirements vary by corridor. What satisfies onboarding in Ghana may fall short in Egypt, forcing finance teams to maintain separate document sets for each market.
Reconciliation is where the hidden cost quietly accumulates. When a single bulk payout fans out across six countries through different rails, matching those transactions to invoices manually is slow and error-prone. Failed payments, partial settlements, and currency conversion discrepancies can leave a finance manager spending days untangling what should have been a routine payroll run.
Types of Cross-Border Payments: Wholesale vs. Retail vs. B2B
Cross-border payments get grouped together as if they're one thing. They're not.
Three distinct categories cover most of the volume:
- Wholesale payments: large-value settlements between financial institutions, central banks, and corporations, such as interbank foreign exchange (FX) settlements and treasury transfers moving hundreds of millions at a time. Speed and finality matter more than cost per transaction.
- Retail cross-border payments: consumer remittances and small purchases across borders. A freelancer receiving USD from a client abroad, or an individual sending money home. High transaction count, low individual value, and very cost-sensitive.
- B2B cross-border payments: trade invoices between suppliers and buyers, bulk payroll across multiple countries, platform disbursements to agents or merchants, and service contract settlements. Higher average transaction values than retail, with compliance and documentation requirements that wholesale infrastructure was never designed to handle.
Wholesale rails like SWIFT were built for financial institutions. Consumer-focused money transfer operators (MTOs) were built for remittances. Neither was designed around the day-to-day reality of a finance team running payroll across six African markets or settling supplier invoices in local currency.
B2B payments sit in between, and the providers that serve them well are a specific subset. Look for multi-rail coverage, bulk payout capability, and local currency support: not speed benchmarks measured on a different transaction type entirely.
FX Risk and Currency Management in Cross-Border Transactions
When you price a supplier contract in USD but pay from a NGN or GHS wallet, the exchange rate on settlement day determines your real cost. That rate can shift by several percentage points between invoice date and payment date, and in volatile corridors, the swing is rarely in your favor.
Two rate concepts matter here. The mid-market rate is the midpoint between buy and sell prices on the open market. The spot rate is what you actually transact at. Every provider sits somewhere between the two, and the gap is their margin. A provider advertising free transfers is usually charging through that spread.
Forward contracts let you lock a rate today for a payment you'll make in 30, 60, or 90 days. For a business settling a USD-denominated supplier invoice due next quarter, the NGN or GHS cost is fixed at the point you book the contract, regardless of where the exchange rate moves before settlement day. The tradeoff is flexibility: you're committed to that rate even if the market moves in your favor, and some providers require a margin deposit at the time of booking, with terms that vary by the bank or treasury provider offering the contract.
For businesses on NGN or GHS corridors, stablecoin payments infrastructure like USDC offers a practical hedge. Holding a USD-pegged stablecoin balance means your treasury doesn't fluctuate with local currency moves between the time you collect revenue and the time you pay a supplier.
Regulatory and Compliance Requirements for B2B Cross-Border Payments
Compliance is the infrastructure underneath every cross-border transaction, not an afterthought.
AML (anti-money laundering) rules require that payment providers and their clients can account for the origin and destination of funds. KYC (know your customer) verifies individual identities, while KYB (know your business) verifies legal entity structure and operating purpose. Both must be completed before a payment rail will process your transfers, and both vary by jurisdiction.
The fragmentation across African markets makes this expensive. Kenya, Nigeria, Egypt, and Ghana each carry different documentation thresholds, reporting timelines, and central bank requirements. A business expanding from Lagos to Nairobi cannot assume its existing compliance posture transfers. Each new corridor may require fresh documentation, new local entity registrations, or market-specific licenses.
Licensing frameworks like MiCA (Markets in Crypto-Assets Regulation) and MSB (Money Services Business) licenses govern what financial services companies are authorized to offer and where. Ask any provider which specific jurisdictions their licenses cover, and confirm which activities and corridors each license authorizes, because operating in a market is not the same as being licensed there.
For your own business, multi-jurisdiction tax obligations add a further layer. Transfer pricing rules, withholding tax on cross-border service payments, and VAT treatment of digital services all differ by country. These are not your payment provider's problem to solve, but they do affect how you structure invoices and where you book revenue.
Stablecoins as a B2B Payment Rail for African Businesses
The mechanics are straightforward. A business in Lagos converts NGN to USDC through an on-ramp, sends USDC to a supplier in Nairobi, who converts it to KES at the other end. Fiat in, stablecoin transfer, fiat out. No correspondent banking chain, no multi-day settlement window, no rate locked in by an intermediary you never chose.
This reflects how stablecoin infrastructure is changing cross-border trade in Africa, and it reduces the number of currency conversion steps a payment takes. A traditional wire from Nigeria to Kenya may convert NGN to USD, then USD to KES across two or three institutions, each taking a spread. A stablecoin transfer collapses that into two conversions at predictable points, with the business controlling when each conversion happens.

According to Grand View Research, the global cross-border payments market was valued at USD 187.7 billion in 2025 and is projected to reach USD 312.1 billion by 2033, though estimates vary across research firms with other reports projecting higher figures depending on scope and methodology. Stablecoins are capturing a growing slice of that B2B settlement volume, particularly on corridors where foreign exchange (FX) volatility and banking fragmentation make traditional rails expensive.
A few caveats apply. Stablecoin balances are not bank deposits and carry no government-backed insurance. USDC and USDT are pegged to USD but that peg can face stress under extreme market conditions. Counterparty risk moves from a correspondent bank to the stablecoin issuer and the on/off-ramp provider you transact through, which is where a reliable USDC payment API becomes useful. These are manageable risks, but they require a different due diligence conversation than opening a bank account.
How to Choose a Cross-Border B2B Payments Provider
Choosing a provider on name recognition alone is a reliable way to get burned on a corridor that wasn't in their marketing deck.
There are six areas worth pressing on before you commit to any provider.
Geographic coverage and rail depth
Ask which specific countries the provider covers, and go beyond the headline number. A company listing "24 African markets" should be able to tell you whether that includes mobile money payouts in Cameroon or bank transfers in Ethiopia. Ask what happens when a rail goes down in a specific market and whether they have a backup.
Settlement speed
Get the actual settlement window per corridor, not the headline figure. A provider that settles Kenya to Nigeria in hours may take several days on Ghana to Uganda. Ask about cut-off times and whether weekends affect settlement.
FX (foreign exchange) transparency
Ask for the spread over mid-market, and go beyond whether they charge a fee. Many providers embed their margin in the exchange rate. A transparent provider will tell you exactly how many basis points above mid-market you're paying per conversion.
Compliance infrastructure
Confirm what KYB (know your business) documentation they require per corridor, how long onboarding takes for each new market, and what AML (anti-money laundering) reporting they handle on your behalf versus what stays with you.
API quality and integration effort
Review their documentation before signing anything. A well-maintained REST API with SDKs, sandbox access, and clear error codes saves your engineering team weeks, a point covered in depth in our guide to sending USDC across Africa via API. Ask about webhook reliability and how failed payments surface in their transaction data.
Pricing structure
Per-transaction fees favor low-volume senders. Monthly subscription pricing favors high-volume operations. Understand which model the provider defaults to, and whether bulk payout runs are priced differently than one-off transfers.
Multi-Currency Treasury Management Across African Markets
Running payroll in NGN, collecting revenue in KES, and paying suppliers in GHS inside the same month is not unusual for a business operating across several African markets. The treasury question is how you hold those balances without losing value every time you convert between them.
The starting point is separating your operating balances by currency. Holding a KES wallet for Kenya collections and a NGN wallet for Nigeria payouts means you're only converting when you need to, not every time a transaction settles. Virtual accounts take this further: a named account issued in your business name through a partner bank lets you collect local currency from customers or partners as if you were a local entity, and this virtual account treasury stays separate from your fiat and stablecoin wallets.
For high-volume conversions, an OTC desk changes the economics. Where a standard payment provider might embed their margin in the exchange rate silently, an OTC desk offers tighter, quoted pricing at volume, with the specifics available in your dashboard under Settings > Fees. Timing also becomes a tool: if you know a large NGN payable is coming in 30 days, you can convert at today's rate and avoid absorbing whatever volatility arrives by then.
Liquidity management across corridors requires knowing your float requirements per market. A business paying weekly supplier invoices in Ghana needs a different GHS reserve than one making monthly lump-sum transfers. Prefunding requirements vary by provider and rail, and some corridors require funds on deposit before a payout triggers while others settle post-transaction. Building a treasury position that accounts for those timing mismatches per market is where finance teams spend most of their energy.
How HoneyCoin Supports B2B Cross-Border Payments Across Africa
HoneyCoin is a financial services aggregator built by Africans for Africa, processing USD 150 million in transactions monthly across 350 enterprise clients in 24+ markets, including Kenya, Nigeria, Ghana, Uganda, Rwanda, and the DRC.
Five core products cover each layer of the B2B payment problem this article walks through:
- Mobile Money Collections and Payouts across 50+ providers, covering the intra-African rails that bank wires miss
- Virtual Accounts in KES, GHS, and NGN, so you collect local currency as if you were a local entity
- Stablecoin On/Off Ramps for USDC and USDT across ETH, Arbitrum, Base, Polygon, BSC, and Optimism, for foreign exchange (FX)-volatile corridors where correspondent banking is expensive
- Wallets as a Service (WaaS), letting banks and fintechs issue their own branded stablecoin wallets without building blockchain infrastructure
- Card Collections for businesses needing card-based acceptance across markets
For high-volume FX, the OTC Desk offers same-day (T+0) settlement with no prefunding required, and pricing is customized per client. Developers can integrate through a cross-border payment API with SDKs in Node, Python, and Ruby. HoneyCoin holds four licenses: MiCA (Czech Republic), MSB (Canada), PSP (Canada), and PSP (Rwanda); operating in 24+ markets is not the same as being licensed in each one.
Final thoughts on Cross-Border B2B Payment Solutions for African Businesses
Running payroll or settling supplier invoices across multiple African markets does not have to mean absorbing hidden FX spreads and multi-day delays on every transaction. Your treasury gets cleaner when you match the right rail to each corridor and hold local currency balances where your volume supports it. The tools exist. The question is how well your current setup uses them.
FAQ
What's the difference between using SWIFT and mobile money rails for B2B cross-border payments across Africa?
SWIFT routes payments through correspondent banking chains that can take 2 to 5 days and quietly absorb value in FX (foreign exchange) spreads at each hop, meaning a payment from Lagos to Accra may route through London or New York before it lands. Mobile money rails typically settle faster and reach recipients in markets where banking infrastructure is uneven, making them the more practical choice for B2B payouts between markets like Kenya and Uganda.
OTC desk vs stablecoin rails for high-volume B2B payments in Africa: which makes more sense?
An OTC (over-the-counter) desk works best when you're converting large fiat amounts and need a quoted rate benchmarked against the market. HoneyCoin's OTC Desk offers same-day (T+0) settlement with no prefunding required; limits vary by corridor and method. Stablecoin rails using USDC or USDT are better suited for corridors where currency volatility in NGN or GHS erodes value between invoice date and settlement, since holding a USD-pegged stablecoin balance lets your treasury stay stable while you decide when to convert.
How do I integrate mobile money and bank rails into a single payments API for Africa?
Look for an API-first aggregator that connects to both mobile money providers and bank networks across your target corridors in one integration, instead of building separate connections per country. HoneyCoin's REST API covers 50+ mobile money providers and 200+ banks across 24+ markets, with SDKs in Node, Python, and Ruby, sandbox access, and webhook support for failed payment visibility, so your engineering team handles one integration instead of one per market.
What tools should I use to manage multi-currency treasury across African markets like Kenya, Nigeria, and Ghana?
HoneyCoin's virtual accounts currently support KES, GHS, and NGN, so you can hold and collect in each currency without routing everything through a USD account first. Virtual accounts issued in your business name let you collect local currency as if you were a local entity, and an OTC desk becomes relevant once your conversion volumes reach the point where the spread difference over mid-market rate adds up to a material cost.
What is a cross-border B2B payment, and how does it differ from a consumer remittance?
A cross-border B2B (business-to-business) payment is a transaction between two businesses in different countries, such as a Kenya-based importer paying a supplier in China, or a Nigerian SaaS company settling contractor invoices in Ghana. Unlike consumer remittances, B2B transactions carry commercial obligations like supplier invoices, trade settlements, and bulk payroll, with larger amounts, stricter KYB (know your business) documentation requirements, and compliance needs that consumer-focused money transfer infrastructure was never designed to handle.

