Table of Contents
- Why Francophone West Africa Demands a Different Payments Strategy
- The XOF Market: Size, Growth, and Business Opportunity
- The Three Dominant Mobile Money Networks, by Country
- How to Register as a Merchant and Get Activated on Each Network
- Three Integration Paths: USSD, Direct API, and Aggregator
- USSD
- Direct API per operator
- Aggregator API
- How a Mobile Money Transaction Flows, Step by Step
- Costs and Merchant Discount Rates Across the Region
- Settlement Timelines and Payout Reconciliation
- The BCEAO's PI-SPI Interoperability Regulation and What It Changes for Businesses
- Running Bulk Payouts and Payroll Across Multiple XOF Markets
- Regulatory Compliance: What Businesses Must Know Before Going Live
- Common Integration Mistakes That Break Conversions
- How HoneyCoin Supports Mobile Money Collections and Payouts Across Francophone West Africa
- Final Thoughts on Mobile Money Collections and Payouts in Francophone West Africa
- FAQ
- What's a faster way to accept mobile money payments across multiple XOF markets without signing separate operator contracts?
- Wave vs Orange Money for merchant payments in francophone West Africa: which should I activate first?
- How do I run payroll disbursements across Senegal, Cote d'Ivoire, and Burkina Faso in a single batch?
- What does the BCEAO's PI-SPI interoperability regulation mean for businesses collecting mobile money payments in WAEMU?
- Do I need a BCEAO license to collect mobile money payments as a merchant in francophone West Africa?
Do not index
Mobile money in francophone West Africa does not work the way M-Pesa works in Kenya, and treating it like it does is where most integrations run into trouble. The XOF region has three or four wallets worth activating depending on your markets, a new interoperability network that changes how cross-wallet payments settle, and operator onboarding that runs on its own timeline. Getting this right from the start saves a lot of painful backtracking later.
TLDR:
- XOF markets share one currency but four separate mobile money networks; activate Wave, Orange Money, MTN MoMo, and Moov Money or you leave real volume uncovered.
- Merchant settlement runs on a T+1 or T+2 batch cycle; a success callback does not mean funds have reached your settlement account.
- The BCEAO's PI-SPI (Plateforme d'Interopérabilité du Système de Paiement Interbancaire) now routes cross-wallet transfers in seconds, with 175 participants across UEMOA as of late 2026.
- Covering more than two XOF corridors via direct API means up to six separate contracts and six reconciliation feeds; an aggregator reduces that to one.
- HoneyCoin connects to 50+ mobile money providers across Cote d'Ivoire, Senegal, Burkina Faso, Benin, Mali, and Togo (six of the XOF markets within its broader 24+ market coverage) via a single API integration.
Why Francophone West Africa Demands a Different Payments Strategy
M-Pesa dominates in Kenya, but it has no presence in the XOF markets. Launch without Wave, Orange Money, and MTN MoMo, and you haven't built a checkout. You've published a webpage.
The eight WAEMU (West African Economic and Monetary Union) countries: Cote d'Ivoire, Senegal, Burkina Faso, Mali, Benin, Togo, Niger, and Guinea-Bissau, share a single currency, the XOF (West African CFA franc), overseen by the BCEAO (Banque Centrale des États de l'Afrique de l'Ouest). That shared monetary framework simplifies foreign exchange (FX) exposure across the bloc, but it does nothing to unify the mobile money rails underneath. Each country has its own wallet market share, its own dominant operator, and its own merchant onboarding process.
The XOF Market: Size, Growth, and Business Opportunity
The numbers behind African mobile money are hard to ignore. Globally, the industry processed USD 2.1 trillion in transactions across 2.3 billion registered accounts in 2026, per the GSMA. At the continent level, the Africa mobile money market grew from USD 9.18 billion in 2025 to USD 11.50 billion in 2026, with projections reaching USD 67.18 billion by 2034 at a CAGR of 25.30%.
The XOF zone sits at an interesting intersection of that growth. Eight countries, one currency, one central bank. For a business expanding across multiple markets, that means no per-corridor foreign exchange (FX) hedging, no currency conversion between Dakar and Abidjan, and a single regulatory counterpart in the BCEAO (Banque Centrale des États de l'Afrique de l'Ouest). Compare that to anglophone West Africa, where Nigeria, Ghana, and Sierra Leone each carry their own currency risk. The shared monetary framework won't solve your payment processing across Africa, but it removes a layer of treasury complexity that trips up many multi-market rollouts.
The Three Dominant Mobile Money Networks, by Country
Coverage varies by country enough that choosing the wrong default wallet at checkout will cost you conversions before a single transaction is declined.
Network | Strongest markets | Role |
Wave | Senegal, Cote d'Ivoire | Often the highest-volume wallet in both markets |
Orange Money | Cote d'Ivoire, Senegal, Burkina Faso, Mali, Guinea | Broad reach across WAEMU, plus Guinea (outside WAEMU) |
MTN MoMo | Cote d'Ivoire, Benin | Primary rail where MTN holds operator dominance |
Moov Money | Benin, Burkina Faso, Togo | Secondary network worth activating in these markets |
Wave holds a leading position in Senegal and Cote d'Ivoire. Orange Money reaches more countries but market share varies sharply by corridor. Moov Money rounds out coverage in Benin, Burkina Faso, and Togo, where skipping it means leaving a real slice of the addressable market off your checkout.
How to Register as a Merchant and Get Activated on Each Network
Each operator runs its own merchant portal and issues country-specific credentials. A business active in both Cote d'Ivoire and Senegal must complete Wave onboarding twice, once per market, even though the product feels identical to the end user. The same applies to Orange Money.
Documents typically required across all three networks:
- Proof of incorporation in the operating country
- Tax identification number
- Beneficial ownership declaration
- Business bank account details
Know Your Business (KYB) verification is manual at each operator. Timelines vary by jurisdiction and operator workload, so build buffer into your go-live planning instead of assuming a fixed window.
Three Integration Paths: USSD, Direct API, and Aggregator
Businesses in the XOF region have three ways to accept mobile money, and the right choice depends on your volume, your team's capacity, and how many corridors you're covering.
USSD
USSD (Unstructured Supplementary Service Data) works on any phone, with no smartphone or data connection required. A customer dials a shortcode, confirms the payment on their keypad, and funds move. The tradeoff is limited automation: transaction confirmation is typically asynchronous, reconciliation is harder to programmatize, and the flow sits largely outside your UI.
Direct API per operator
Each mobile money operator publishes its own API, giving you the lowest intermediary cost and the most control over the payment flow. The catch is fragmentation. Wave Senegal and Wave CĂ´te d'Ivoire are separate legal entities with separate API keys, and Orange Money is structured the same way. Covering four networks across six markets means up to six separate contracts, six separate credential sets, and six separate reconciliation feeds to maintain.
Aggregator API
An aggregator sits between your system and the underlying operator APIs, exposing a single endpoint for collections and payouts across multiple wallets and corridors. You sign one contract, integrate once, and the aggregator handles operator relationships underneath. The tradeoff is an additional intermediary layer, which can affect pricing and creates a dependency on the aggregator's uptime and coverage decisions.
For most businesses merging mobile money and bank rails across more than two XOF markets, the aggregator path is the faster route to coverage. Direct integration makes sense if you're operating in one or two corridors at high volume and the margin difference warrants the maintenance overhead.
How a Mobile Money Transaction Flows, Step by Step
A mobile money payment moves through several distinct steps, and knowing each one helps you diagnose failures when they happen.
When a customer reaches checkout, your system sends a collect request to the operator API, which pushes a prompt directly to the customer's handset. The customer sees a summary of the amount and merchant name, enters their PIN, and the wallet is debited in real time. The operator returns a success or failure callback to your system, and the funds post to your collection wallet.
That describes a pull payment: your API triggers the collect request, and the customer approves it. Pull is the standard model for e-commerce checkout and subscription billing.
Push payments work the other way. The customer opens their wallet app or dials a USSD (Unstructured Supplementary Service Data) code and sends funds directly to your merchant account, with no API trigger on your end. Reconciliation is harder here since you're matching inbound transfers against expected amounts, as opposed to receiving a structured callback tied to a specific order.
For payroll disbursements and supplier payouts, the flow reverses entirely. Your system sends a payout request to the operator API with the recipient's wallet number and amount. The operator debits your settlement balance, credits the recipient's wallet, and returns a transaction reference.
Costs and Merchant Discount Rates Across the Region
Fees in XOF markets follow a merchant discount rate (MDR, the percentage the operator retains from each transaction) model, with collections and payouts often priced separately. Payout fees tend to run higher than collection fees across most networks. Confirm current rates directly with each operator or aggregator before finalizing your pricing model.
Wave, Orange Money, and MTN MoMo merchant fees are set by each operator and vary by country and merchant, so confirm current rates directly with each operator before finalizing your pricing model. HoneyCoin pricing is customized per client, and you can view yours under Settings > Fees in your dashboard.
If your operation exits the XOF zone to pay a USD-denominated supplier or settle into a non-WAEMU account, you'll also absorb a conversion spread on top of the MDR. Run the numbers on the full corridor cost against the broader criteria for cross-border payments in high-growth markets, beyond the headline MDR, before finalizing your pricing model.
Settlement Timelines and Payout Reconciliation
Settlement in XOF markets splits into two separate events that many businesses conflate until a cash flow problem forces the distinction.
The first event is the customer-side credit. When a customer pays, their wallet is debited and you receive a success callback within seconds. That callback confirms the transaction, but it does not mean the funds have reached your settlement account.
The second event is the merchant-side settlement. Operators typically batch collected funds and settle to merchant accounts on a T+1 or T+2 cycle, depending on the operator and the volume tier. Some operators settle same-day for high-volume accounts, but that is negotiated, not default. Build your working capital plan around the batch cycle, not the callback.
For payroll disbursements, the timing gap matters more. If your settlement account is funded by incoming collections, running payouts on the same day you expect settlement to land creates a shortfall risk. The standard fix is holding a prefunded float that covers at least one settlement cycle in advance.
Refunds add another layer. Most operators process refunds manually or through a separate reversal flow, and the timeline is operator-dependent. Reconciliation workflows should flag reversals separately from settlement batches, since they often arrive outside the standard settlement window.
The BCEAO's PI-SPI Interoperability Regulation and What It Changes for Businesses
The BCEAO's PI-SPI (Plateforme d'Interopérabilité du Système de Paiement Interbancaire) is the regional payment network connecting banks and mobile money operators across UEMOA (Union Économique et Monétaire Ouest-Africaine). Before it existed, a transfer from an Orange Money wallet to a Wave account could take hours or fail entirely. Now, the PI-SPI typically routes it in seconds, regardless of which institution holds either account.
The network expanded in late 2026. Wave CĂ´te d'Ivoire joined as of September 30, 2026, pushing participants in CĂ´te d'Ivoire from 23 to 38. The BCEAO also made PI-SPI participation mandatory across UEMOA for all licensed operators.
For your business, this changes two things:
- Receiving payments from abroad gets simpler, since customers on any connected wallet can pay your merchant account without hitting an interoperability wall.
- Payouts get faster, since disbursements to employees or suppliers on different networks no longer queue in a separate settlement batch.
Before going live with any provider, verify they appear on the current PI-SPI participant list.
Running Bulk Payouts and Payroll Across Multiple XOF Markets
Disbursing payroll across four WAEMU (West African Economic and Monetary Union) countries in a single run looks simple on paper. In practice, the complexity hides in the recipient data.
Each row in your payout file needs at minimum: the recipient's phone number in local format, their mobile money network (Wave, Orange Money, MTN MoMo, or Moov Money), and the amount in XOF. Country code and recipient name are worth including even when not strictly required, since operators use them for fraud screening and some will reject payouts where the name does not match the registered wallet.
Failed deliveries are the bigger practical problem. You need an exception workflow before you run your first batch, not after. A working pattern looks like this:
- Flag failed transactions by error code immediately after the batch runs so you can triage by failure type instead of chasing each one individually.
- Attempt re-delivery to the same wallet after 24 hours if the failure was a temporary limit issue on the recipient's side.
- Route persistent failures to a manual review queue, where your team confirms the correct network and number with the recipient directly.
- Issue an alternate payout method such as bank transfer or cash pickup if two re-delivery attempts fail.
Gig worker and agent commission disbursements add a timing wrinkle: recipients often expect same-day payment, while your settlement float may not land until T+1. Separate your float account from your operating balance and prefund it by at least one payout cycle. That gap is where most payroll runs break.
Regulatory Compliance: What Businesses Must Know Before Going Live
The BCEAO (Banque Centrale des États de l'Afrique de l'Ouest) is the single regulatory authority governing electronic money issuers and payment service providers (PSPs) across all eight WAEMU member states. Any entity that wants to issue mobile money or operate a payment service in the zone must hold a BCEAO license or operate under one. This shapes the compliance obligations that flow downstream to your business as a merchant.
As a merchant, you do not need to hold a BCEAO license yourself. You do need to pass the KYB (Know Your Business) verification that each operator or aggregator runs before activating your merchant account, covering company registration documents, tax registration, and beneficial ownership disclosure. Businesses registered abroad typically need a local subsidiary or in-country representative, since most operators will not activate a merchant entity with no local footprint.
On the AML (Anti-Money Laundering) side, licensed operators must monitor transaction flows on your account for suspicious activity. Your obligation is to keep your declared business activity accurate and flag unusual volumes to your operator or aggregator proactively. If your actual transaction pattern diverges from what you described at onboarding, your account can be reviewed or suspended without warning.
Working through an aggregator moves some of this compliance burden to the provider. The aggregator holds the operator relationships and works with licensed operator partners on ongoing transaction monitoring. If you integrate directly with each operator instead, you own more of that compliance relationship individually per market: a tradeoff worth weighing against your volume and operational capacity.
Common Integration Mistakes That Break Conversions
Each of these mistakes shows up in real integrations across XOF markets, and most are avoidable with some upfront testing.
- Showing only one wallet at checkout will cut your conversion rate in ways that aren't obvious at first. In Senegal, a checkout built around Orange Money alone misses Wave users: Wave's transaction-volume market share across WAEMU reached 28.4% in 2024 (up from 21.4% in 2023), per The Africa Report, making it too large a slice to leave off your checkout. Map your wallet coverage to the actual market mix before you go live.
- Mobile money confirmations are asynchronous, and treating them like card auth responses breaks order flows. The operator sends a callback after the customer confirms on their handset, which can take 15 to 90 seconds. Build a pending state into your UI and tie order fulfillment to the callback, not the initial API response.
- Individual wallets in XOF markets carry daily and per-transaction caps set by the operator. Check the API documentation for limit handling, since a high-value collection or payout that exceeds those limits will fail silently at the operator level. Test at the limit boundary during integration, and not merely at a small round number.
- French-language prompts matter more than most teams expect. Your merchant name, amount display, and any supplementary message you control should be in French. English-only metadata increases abandonment on feature phones where users read each field carefully.
- USSD sessions time out in roughly 90 seconds across most networks. If your flow asks the customer to switch apps or retrieve an order number mid-session, the session will expire and the payment will fail. Design for straight-through confirmation with no context switching required.
How HoneyCoin Supports Mobile Money Collections and Payouts Across Francophone West Africa
HoneyCoin for Business connects directly to the infrastructure described throughout this guide. We integrate with 50+ mobile money providers and support operations across Burkina Faso, Benin, Cote d'Ivoire, Senegal, Mali, and Togo within our payment coverage across 24+ markets. Finance teams run multi-currency collections and bulk payouts from a single dashboard, reaching mobile money wallets across XOF markets in one CSV run without separate contracts per operator.
For businesses moving value out of or into the XOF zone, our OTC Desk handles high-volume foreign exchange (FX) conversions at same-day (T+0) settlement. We process USD 150 million in monthly transaction volume across 350 enterprise clients. Developers can connect via our cross-border payment API, with SDKs available for Node, Python, and Ruby, with collections, payouts, bank transfers, and stablecoin on/off-ramps all accessible through the same integration.
Final Thoughts on Mobile Money Collections and Payouts in Francophone West Africa
The businesses that win in XOF markets are the ones that treat wallet coverage as a conversion decision, not an afterthought. Match your checkout to the market, design your reconciliation around batch settlement cycles, and build your float before you need it. The region is moving fast, and the right setup lets you move with it.
FAQ
What's a faster way to accept mobile money payments across multiple XOF markets without signing separate operator contracts?
Use a payments aggregator. A single aggregator integration covers Wave, Orange Money, MTN MoMo, and Moov Money across Senegal, Cote d'Ivoire, Burkina Faso, Benin, and Togo in one connection, replacing up to six separate contracts and credential sets. Direct operator integration makes sense at high single-corridor volumes where the margin difference warrants the maintenance overhead: for most multi-market rollouts, the aggregator path gets you to live faster.
Wave vs Orange Money for merchant payments in francophone West Africa: which should I activate first?
Activate both, and add MTN MoMo for Cote d'Ivoire and Benin. Wave holds the highest transaction share in Senegal and Cote d'Ivoire; Orange Money gives you broader country reach across the WAEMU bloc, including Burkina Faso and Mali. Showing only one wallet at checkout will cut your conversion rate in markets where the other wallet dominates.
How do I run payroll disbursements across Senegal, Cote d'Ivoire, and Burkina Faso in a single batch?
Each row in your payout file needs the recipient's phone number in local format, their mobile money network (Wave, Orange Money, MTN MoMo, or Moov Money), and the amount in XOF (West African CFA franc). Prefund a float account that covers at least one full settlement cycle before you run the batch, since collected funds typically settle to your merchant account on a T+1 or T+2 cycle, and running payouts against funds that have not yet landed creates a shortfall. Build an exception workflow for failed deliveries before your first run, not after.
What does the BCEAO's PI-SPI interoperability regulation mean for businesses collecting mobile money payments in WAEMU?
PI-SPI (Plateforme d'Interopérabilité du Système de Paiement Interbancaire) routes transfers between different mobile money wallets and bank accounts in seconds across UEMOA (Union Économique et Monétaire Ouest-Africaine). The BCEAO (Banque Centrale des États de l'Afrique de l'Ouest) has made participation mandatory for all licensed operators, and with Wave Cote d'Ivoire joining as of September 30, 2026, customers on any connected wallet can pay your merchant account without hitting an interoperability wall. Before going live with any provider, confirm they appear on the current PI-SPI participant list.
Do I need a BCEAO license to collect mobile money payments as a merchant in francophone West Africa?
No. As a merchant, you do not hold the BCEAO license: the licensed mobile money operator holds it, and aggregators work through those licensed operators. Your obligation is to pass the KYB (Know Your Business) verification each operator or aggregator runs at onboarding, covering company registration documents, tax registration, and beneficial ownership disclosure. Businesses registered abroad typically need a local subsidiary or in-country representative, since most operators will not activate a merchant account with no local footprint.
