Accepting Mobile Money on your website: the questions to ask

In Cameroon, an online shop that only accepts bank cards shuts out a large share of its customers. Mobile Money is a must, but integrating it raises questions that are best settled before launch.

Integrate each operator, or use an aggregator?

Integrating MTN and Orange directly means a contract and a development effort per operator, then maintenance every time their interfaces change. An aggregator puts all payment methods behind a single integration. The choice depends on your volume and your technical team; for most SMEs, an aggregator saves months.

What a good payment page should do

• recognise the operator from the number entered, without asking the customer to choose;
• explain clearly that approval happens on the phone;
• show errors people understand: insufficient balance, timeout, operator unavailable;
• work on a slow mobile connection.

Never rely on the browser coming back

This is the most common mistake. The customer returns to your website after paying, and the order is confirmed. But that return can be faked, or never happen if the phone loses its connection. The confirmation that counts is the one the payment provider sends to your server, signed to prove it really comes from them.

Plan for refunds and reconciliation

A customer who pays twice, a cancelled order: refunds come up in the first weeks. Check that they are possible, in full and in part, and that every payment carries your own order reference. Reconciliation with your accounts depends on it.

Test before taking money

A good provider offers a test environment where you can simulate successful, declined or abandoned payments. Run every case before opening: that's where the gaps show up.

We built Kola, our payment aggregator for Cameroon and the CEMAC zone, to answer these questions. It is currently in early access.