M-Pesa: Kenya (multiple African markets)'s digital wallet
Safaricom's mobile-money wallet — the dominant payment rail in Kenya and a major force across East Africa.
How the M-Pesa flow works
M-Pesa is a mobile-money wallet operated by Safaricom (and Vodacom in adjacent markets). Consumers hold a wallet balance topped up with cash at any M-Pesa agent, from a bank account, or via received payments.
At checkout the merchant's PSP triggers an STK push to the consumer's SIM (or displays a Paybill/Till number to pay to). The consumer approves in the SIM menu / M-Pesa app with their M-Pesa PIN.
Funds move within Safaricom's platform in real time; the merchant receives a webhook confirming the paybill credit and settles out to a linked bank account on a defined cadence.
M-Pesa dominates Kenyan retail and everyday payments and is a critical rail for utilities, education fees, transport and remittances.
Typical use cases
- Any Kenyan e-commerce, in-app or in-person checkout.
- Utility, telco, education and transport bill pay.
- Cross-border remittances landing in Kenya.
- Marketplaces paying out to Kenyan sellers or creators.
Consumer reach
Over 30 million active Kenyan users; overwhelmingly the default digital payment method.
Meaningful presence in Tanzania, DRC, Mozambique, Egypt (via Vodafone) and other African markets under localised branding.
Who should accept M-Pesa
- Any merchant selling to Kenyan consumers.
- Cross-border merchants targeting East Africa.
- Utilities, telcos, schools and transport operators serving Kenyan customers.
Operational detail
The operational half of every method profile — settlement, refunds, disputes, PSP coverage and licensing — is reserved for Payment Methods List founding partners. It's the part vendor sites won't publish and the part that actually decides whether M-Pesa works for your stack.
Settlement time
When M-Pesa balances actually clear from the wallet operator to a merchant account, how top-up float and P2P legs distort the timeline, cut-offs on the operator side, and which PSPs pass funds through same-day vs. hold a reserve.
Book a founding-partner call →Refund mechanics
How M-Pesa refunds flow back to the payer's wallet balance vs. their funding source, partial-refund support, time windows before a refund becomes an off-platform transfer, and the exact PSP API calls used when the wallet has no native reversal.
Book a founding-partner call →Chargeback exposure
Whether M-Pesa supports scheme-style chargebacks, the operator-run dispute program that sits alongside, actionable reason codes, evidence formats accepted, and observed net loss rates versus cards on the same basket.
Book a founding-partner call →PSP coverage matrix
Which acquirers, MoRs and wallet-aggregators actually process M-Pesa in Kenya (multiple African markets) today, whether coverage is direct or piggy-backed on a scheme rail, effective pricing bands, and where the operator has restricted new merchant onboarding.
Book a founding-partner call →KYC & licensing notes
What a merchant needs to legally accept M-Pesa in Kenya (multiple African markets), whether the wallet operator or the PSP is the regulated entity, KYC and AML obligations that flow down to the merchant, and cross-border MoR options.
Book a founding-partner call →