Mobile Money
Mobile money adapters support telecom-linked payment accounts, SIM-based wallets, and mobile banking services. These are essential in markets with low card penetration. Approximately 11 direct integrations plus coverage via multi-method aggregators.
Africa — Core Mobile Money
| Provider | Adapter name | Countries | Pay-in | Pay-out | Required params |
|---|---|---|---|---|---|
| Airtel Money | airtel_money | KE, UG, TZ, ZM, RW + | ✅ | ✅ | client_id, client_secret |
| MTN Mobile Money | mtn_momo | GH, NG, UG, CM, RW + | ✅ | ✅ | subscription_key, api_key |
| Orange Money | orange_money | SN, CM, CI, BF + | ✅ | ✅ | client_id, client_secret |
| M-Pesa | via flutterwave / cellulant | KE, TZ, GH, EG, NG | ✅ | ✅ | Through aggregator adapters |
| Vodacom M-Pesa | via peachpayments | TZ, MZ | ✅ | — | Through aggregator |
| Wave | via dpo | SN, CI, ML, BF, GM | ✅ | ✅ | Through DPO Group |
| Chipper Cash | chippercash | NG, GH, KE, UG, TZ, RW | ✅ | ✅ | Cross-border wallet |
| Paga | paga_ng | NG | ✅ | ✅ | principal, credentials, hash |
M-Pesa does not have a standalone adapter. It is accessible via multi-method aggregators: Flutterwave (NG, KE, GH, TZ), Cellulant (KE, TZ), DPO Group (KE, TZ), and Pesapal (KE, UG, TZ). Configure the aggregator adapter on your terminal to enable M-Pesa as a payment method option.
Asia-Pacific — Mobile Wallets (Mobile-Money Category)
| Provider | Adapter name | Countries | Pay-in | Pay-out | Notes |
|---|---|---|---|---|---|
| GCash | gcash | PH | ✅ | — | client_id, client_secret |
| Maya | maya_ph | PH | ✅ | ✅ | public_key, secret_key |
| ShopeePay | shopeepay | ID, PH, MY, TH, SG | ✅ | — | partner_id, partner_key |
| PiPay | pipay_kh | KH | ✅ | ✅ | Cambodia mobile wallet |
| Wing | wing_kh | KH | ✅ | ✅ | Cambodia mobile money |
| bKash | bkash_bd | BD | ✅ | ✅ | app_key, app_secret, username, password |
| Nagad | nagad_bd | BD | ✅ | — | Bangladesh mobile wallet |
Telecom Billing Adapters
Carrier billing routes charges through a user's phone bill — suitable for digital goods and small amounts.
| Provider | Adapter name | Countries | Pay-in | Pay-out | Notes |
|---|---|---|---|---|---|
| Boku | boku | 90+ | ✅ | — | merchant_id, api_key |
| DigiVirgo | digivirgo | EU, APAC | ✅ | — | merchant_id |
| Dimoco | dimoco | AT, DE, EU | ✅ | — | client_id, password |
Coverage by Region
| Region | Methods available |
|---|---|
| East Africa | Airtel Money, MTN, M-Pesa (via aggregators), Wave |
| West Africa | MTN MoMo, Orange Money, Paga, Chipper Cash |
| Southern Africa | M-Pesa (via aggregators), Airtel Money |
| Southeast Asia | GCash, Maya, ShopeePay, OVO, DANA, TNG |
| South Asia | bKash, Nagad, UPI (via bank transfer) |
| Central Asia | Elsom (KG), QIWI (RU/CIS) |
Integration Notes
Limits
Mobile money transactions typically have per-transaction and daily limits set by the telecoms operator. These vary by country and tier of KYC. Configure limits on your terminal accordingly.
Float Management
For pay-out (disbursement) flows, the aggregator or provider requires pre-funded float in-country. Coordinate with your provider account manager for float top-up procedures.
Webhooks
Mobile money transactions can have delayed confirmations (up to 5 minutes in some networks). Ensure your notifyUrl handles late webhook delivery and idempotent status updates.
For detailed configuration, click on any provider above to open its detail page.