Resources
Mobile payment and financial inclusion
Mobile payment is the everyday financial infrastructure for a large share of the West African population. Designing an offer that builds on it requires understanding its economics and its interoperability conditions.
One infrastructure, several models
Mobile payment rests on an agent network, an electronic money account and transfer rules. Business models differ according to whether the operator charges for deposit, withdrawal or transfer, and according to the share passed on to the agent network. Designing an offer on top of it therefore requires knowing those flows, measuring the per-transaction cost for the end user, and anticipating interoperability between operators, which governs real usage.
- An agent network, whose density governs real usage
- An electronic money account, distinct from a bank account
- A pricing structure that decides frequency of use
- Interoperability between operators, which broadens usage
- Impact measurement based on actual use, not on accounts opened
Designing an offer built on mobile payment
- 01
Map the flows
Who pays what, when, with which fee. That map determines viability before any technical design.
- 02
Size the per-transaction cost
Set against the average amount, it decides adoption. A flat fee mechanically excludes small amounts.
- 03
Plan the degraded mode
An interrupted transaction must be replayable without double charging. Idempotency is designed into the first diagram.
- 04
Measure actual use
Frequency, median amount, share of active users: those three figures say whether the offer genuinely serves.
What the catalogue covers on the subject
- taught hours on the subject
- 160
- hours of the customer adviser title
- 400
- modules in the finance field
- 47
Ecosystem, models, interoperability, design, impact.
Level 4, 40 credits.
Continuing-education base, real count.
Mobile payment questions
How should the applicable regulatory framework be approached?
By identifying the competent authority and the status required for the intended activity, before any technical design. The block devoted to the subject covers the actors, the obligations and the supervisory arrangements that structure the ecosystem.
How is the inclusion actually produced measured?
Through usage rather than account openings: transaction frequency, median amount, share of users active over three months. Those three indicators say whether a service serves, where account counts only say it was distributed.
Does the subject only concern financial institutions?
Any organisation that collects payments is concerned by pricing, interoperability and degraded mode. Retailers, carriers and public services design their collection journeys under exactly the same constraints.
Explore next
- Trade and customsIncoterms, document sets, customs value, tariff classification, customs regimes and documentary credit: running an export operation.
- Supply chainTransport modes, chartering, warehousing, cold chain, traceability and full logistics cost: running a supply chain.
- Market researchCustomer interviews, need validation, market size, value proposition, revenue streams and unit economics: validating before building.
- Framing a projectNeeds analysis, framing note, scope, stakeholder mapping, success criteria and initial budget: framing a project.
- Multi-site projectsShort rituals, written decisions, shared progress, risk management and supplier steering: running a project across several sites.
- Structured hiringJob description, sourcing, structured interview, evaluation grid, reasoned decision and onboarding: running a hire end to end.