Auto-Detect the Network by Prefix and Prefill the Mobile Money Checkout (2026)

The verdict in three sentences

On a mobile money checkout, every removed tap matters: auto-detecting the network from the number prefix skips the selection screen and adds 3 to 5 % completion on 3G connections. But number portability (keeping your number when switching networks) breaks 6 to 9 % of prefix mapping: the prefix no longer proves the real network. The 2026 golden rule: prefill without locking — always leave a manual correction fallback before the payment call.

Why one fewer tap moves conversion

On mobile, every extra funnel step loses buyers. On a slow connection, opening a network dropdown, waiting for it to render, choosing, then returning to the amount field costs 2-4 seconds and an abandonment opportunity. By prefilling the detected network, you show the right logo and the right flow immediately (Orange USSD, Wave redirect, etc.).

The 2026 order of magnitude on West African stores: moving from mandatory manual selection to auto-detection with confirmation gains 3 to 5 points of payment completion, more on small baskets and 3G traffic where patience is low.

The prefix mapping in 2026

The prefix (the first 2-4 digits after the country code) is still a good default hint. Here are common mappings as a 2026 order of magnitude — revalidate with your aggregator, since numbering plans evolve.

Important detail: in Côte d'Ivoire, the 10-digit numbering mixes a network prefix and a geographic prefix — test on real numbers before freezing your rules.

Portability forces a fallback

Number portability lets a subscriber change network while keeping their number: the Senegalese 77 prefix, "historically Orange," may now point to a subscriber who moved to a competitor. In 2026, an estimated 6 to 9 % of numbers no longer match the prefix's original network.

Practical consequences:

• Never trigger a payment assuming the network without a manual exit.
• Show the detected network as an editable pre-selection, not a locked choice.
• If the aggregator returns "wrong network," immediately offer alternatives without re-entering the number.
• For high volumes, consider a real-time carrier lookup API (cost and latency trade-off).

Mini case study

Awa runs a cosmetics shop in Dakar with 1,500 payment attempts per month, average basket 12,000 FCFA. Her checkout forced network choice: completion rate 72 %. She switches to prefix auto-detection with confirmation.

Estimated completion gain: +4 points, i.e. 76 %. Concretely, 60 extra completed orders per month (4 % of 1,500). At 12,000 FCFA, that is 720,000 FCFA of recovered revenue per month, i.e. 8.64 M FCFA/year. In the same month, 3 "ported" customers had their network mis-guessed: thanks to the fallback, they fix it in one tap without dropping off.

FAQ

Is the prefix enough to pick the network? No — it is a good default, not proof: in 2026, 6-9 % of numbers are ported to another network. Use the prefix to prefill, never to lock the payment.

How much conversion do you really gain? Order of magnitude: +3 to 5 points of completion, especially on small baskets and 3G traffic where every tap and second count. Measure on your own before/after traffic.

Should you pay for a carrier detection API? Only at high volume. Below that, prefix mapping + manual confirmation covers 90 %+ of cases. A lookup API adds a per-request cost and latency to weigh.

What if the aggregator returns a network error? Do not force re-entry of the number. Immediately show the 2-3 alternative networks and re-fire the payment on the right flow: you avoid re-typing abandonment.

Does it work for Wave and Orange Money? Yes — detection routes to the right flow (Wave redirect vs Orange Money USSD). The principle stands: prefill, confirm, allow correction.

Let's talk about your project. We implement robust network detection with a portability fallback on your mobile money checkout. WhatsApp +221 77 596 93 33.