A point-of-sale system that works beautifully in Nairobi can be useless in Accra, and the reason is almost always the same: how customers pay.
Africa is not one payments market. It is a set of national markets, each dominated by different rails, and a POS is only as good as its support for whichever rail your customers actually use. This is what a POS has to handle in each of the major markets, and what that means if you are operating across more than one.
If you are choosing a platform, our POS for African businesses page covers the product side. This is the payments landscape underneath it.
Why mobile money changes POS design
In markets where cards dominate, a POS talks to a terminal, the terminal talks to an acquirer, and confirmation arrives in a second or two over a dedicated line.
Mobile money works differently in ways that matter at the counter:
- The customer's phone is the terminal. Confirmation depends on them completing a prompt, which they might fumble, ignore, or do while walking away.
- Confirmation is asynchronous. The request goes out; the answer comes back seconds later, sometimes much later. A POS that blocks the till waiting for it will jam at peak hour.
- Reversals are awkward. There is rarely a clean chargeback path, so getting the amount right the first time matters more.
- Network quality varies. The payment rail and your internet connection can fail independently.
A POS designed for card markets and retrofitted for mobile money tends to get the asynchronous part wrong, which shows up as duplicate charges and stuck transactions.
Kenya
Dominant rail: M-Pesa (Safaricom), with Airtel Money a distant second.
The most mature mobile money market in the world, and the one with the highest customer expectation. Kenyan buyers expect to pay by entering nothing — an STK push arrives, they enter their PIN, done. Asking a Kenyan customer to manually enter a till number and amount is a visible downgrade.
What a POS must do: native Lipa na M-Pesa via Buy Goods or Paybill, STK push initiated from the till, automatic reconciliation of the callback against the sale, and a manual-match fallback for when a customer pays from the wrong number. Plus KRA eTIMS receipts, which is a Kenya-specific compliance obligation no international platform handles natively.
See M-Pesa POS integration for how this works in practice.
Tanzania
Dominant rails: M-Pesa (Vodacom), Mixx by Yas (formerly Tigo Pesa), Airtel Money, HaloPesa.
Tanzania is genuinely multi-rail in a way Kenya is not — a shop cannot standardise on one provider and expect to serve everyone. Interoperability between wallets has improved considerably, but a merchant still benefits from accepting more than one directly.
What a POS must do: support several wallet providers at one till, and present them clearly enough that an operator does not have to ask which network the customer is on.
Uganda, Rwanda and Zambia
Dominant rails: MTN Mobile Money and Airtel Money across all three; Zamtel Kwacha additionally in Zambia.
These are effectively two-provider markets, which simplifies the POS problem: support MTN MoMo and Airtel Money properly and you cover almost everyone. The complication is that merchant onboarding and settlement terms differ per country, so a platform that has done the integration once does not automatically work across the border.
Ghana
Dominant rails: MTN Mobile Money, Telecel Cash (formerly Vodafone Cash), AirtelTigo Money.
Ghana has strong mobile money penetration and mandated interoperability through GhIPSS, which means cross-network transfers work more smoothly than in some neighbouring markets. Merchant expectations are close to Kenya's: customers expect to confirm on their handset rather than type details.
Nigeria
Dominant rails: instant bank transfer, USSD, and cards on the domestic Verve scheme alongside international networks.
Nigeria is the outlier. Mobile money never displaced banking the way it did in East Africa; the dominant behaviour is an instant transfer over NIBSS from a bank app, often confirmed by the customer showing the merchant a receipt screen.
What a POS must do: treat bank transfer as a first-class payment method with proper reconciliation, rather than as "cash, sort of". The failure mode here is a merchant accepting a screenshot as proof and only discovering days later that the transfer never landed.
What this means if you operate in more than one market
Three practical consequences:
One catalogue, per-country pricing. You want the same product list everywhere and prices in local currency, not a separate system per border.
Offline has to work everywhere. Connectivity is uneven across all of these markets. A till that stops when the network does will stop regularly. Sales should continue, stock should keep deducting, and everything should sync when the link returns.
Reconciliation must be per-rail. "Mobile money: 240,000" across three providers in two currencies is not a reconcilable figure. You need it broken out per provider per day, matched to the underlying sale.
The question to ask any vendor
Not "do you support mobile money" — everyone says yes. Ask instead:
- Which specific providers, in which specific countries, natively rather than through a third-party aggregator?
- Does the till initiate the payment prompt, or does the customer type the details in?
- What happens to the sale if the confirmation callback never arrives?
- Can I sell while the internet is down, and what syncs afterwards?
- Do you handle the local tax receipt obligation — eTIMS in Kenya, EFD in Tanzania, and their equivalents?
The fourth and fifth questions are where most international platforms stop being able to answer.
Selling across African markets? Start a free sell.ke trial — mobile money at the till, offline selling, and one catalogue across every branch.