Multi-country mobile money checkout across West Africa 2026: architecture and fees

The verdict in three sentences

A merchant selling across several West African countries needs operator routing based on the MSISDN (the number prefix), not a naive single checkout. Fees run around 1.4% on average, but the real challenge is the asynchronous webhook whose callback arrives between 4 and 40 seconds. Well architected, you push manual reconciliation below 3% and collect in four countries without multiplying errors.

Operator coverage by country 2026

Routing means detecting the country and operator from the entered number, then calling the right API. 2026 orders of magnitude:

The MSISDN gives you the country code, then the operator prefix: you route the transaction without asking the customer to choose.

Technical architecture and watch points

The webhook is the heart of the system. The customer pays, the operator confirms asynchronously: your server must wait for the callback before validating the order.

Survival rules: queue plus retry to absorb slow callbacks, an idempotency key per order to avoid double payment, and an intermediate "pending" status on the client side during the 40-second maximum.

Mini case study

Fatou sells accessories to three countries, 900 orders/month at 25,000 FCFA. At 1.4% average fees, she pays 315,000 FCFA/month in commissions. Without routing, 3% of payments ended up poorly reconciled: 27 orders/month to check by hand, ~9 hours. With MSISDN routing plus idempotent webhooks, she drops to fewer than 5 orders to review, about 1.5 hours/month. Net gain: 7.5 hours/month and reliable cash flow.

FAQ

Do I need a merchant contract per country? Often yes for direct, or a single aggregator contract covering the zone. The aggregator simplifies but costs ~0.4 extra points of fees.

What if the callback never arrives? Add a job that polls the status after 60 seconds and retries, then a clean "failed" status. Without this safety net, the order stays stuck.

Is the 200,000 FCFA/day KYC cap a problem? For average baskets, no. For high baskets, move the customer to full KYC or split the payment.

How do I handle a number that matches no operator? Show a manual operator fallback selector plus a field to enter the paying number.

How long to deploy a 4-country checkout? Count 4 to 6 weeks depending on the number of operators and KYB validations, webhook tests included.

Let's talk about your project. We design your multi-country routing with idempotent webhooks and near-automatic reconciliation. WhatsApp +221 77 596 93 33.