MTN MoMo Mobile Money API
MTN Mobile Money (MoMo) REST API for businesses across Sub-Saharan and West Africa to request payments from customers (Collections), send money to mobile wallets (Disbursements), and transfer funds between accounts through MTN's 53M+ mobile money subscriber network across 17 African countries including Ghana, Côte d'Ivoire, Uganda, Cameroon, Benin, and others. Enables AI agents to manage payment collection request for Africa mobile checkout automation, handle disbursement for Africa payroll and benefit payment automation, access remittance transfer for Africa cross-border payment automation, retrieve account holder information for Africa KYC automation, manage transaction status for Africa payment confirmation automation, handle balance inquiry for Africa wallet balance automation, access delivery notification for Africa payment event automation, retrieve basic KYC validation for Africa identity verification automation, manage sandbox user creation for Africa development automation, and integrate MTN MoMo with African e-commerce, NGO, microfinance, and enterprise platforms for end-to-end West and Sub-Saharan Africa mobile money automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Africa mobile money. Telecom-regulated. OAuth2 + subscription key. Africa. Mobile wallet data.
⚡ Reliability
Best When
An African business, NGO, or fintech wanting AI agents to automate mobile money collection and disbursement across MTN's 17-country West and Sub-Saharan Africa network — particularly strong in Ghana, Côte d'Ivoire, Uganda, and Cameroon.
Avoid When
SANDBOX REQUIRES CREATING SANDBOX USERS: MTN MoMo sandbox requires explicitly creating sandbox users (POST /v1_0/apiuser) with subscription key before testing; automated sandbox setup must provision test users; automated testing without provisioned sandbox users creates 404 for all collection/disbursement calls. PRIMARY KEY vs SECONDARY KEY: MTN MoMo uses Ocp-Apim-Subscription-Key header (primary or secondary key from portal); automated requests must include subscription key; automated standard bearer-only auth without subscription key creates 401 unauthorized. PRODUCT-SPECIFIC API KEYS: MTN MoMo has separate API subscriptions for Collections, Disbursements, and Remittances; automated multi-product integration requires separate subscription per product; automated single-key assumption for all products creates wrong_product_key error. CALLBACK URL IS OPTIONAL BUT RECOMMENDED: MTN MoMo Collections and Disbursements support both polling and callback; automated production should use callback for efficiency; automated polling-only implementation increases API call volume and has status lag.
Use Cases
- • Collecting mobile payments for Ghana and West Africa e-commerce checkout agents
- • Disbursing to MTN mobile wallets from Africa payroll and welfare payment agents
- • Processing cross-border remittances via MTN MoMo from Africa transfer agents
- • Validating MTN subscriber KYC from Africa identity verification agents
Not For
- • Non-Africa markets (MTN MoMo is Sub-Saharan/West Africa only)
- • Non-MTN subscribers (MoMo serves MTN subscribers; use M-Pesa for Safaricom users)
- • Large international bank transfers (MTN MoMo is mobile wallet for lower-value transactions)
Interface
Authentication
MTN MoMo uses OAuth 2.0 (client credentials) + Ocp-Apim-Subscription-Key header. REST API with JSON. Johannesburg, South Africa HQ (MTN Group). Products: Collections, Disbursements, Remittances, Account Lookup, Balance, Transaction History. SDKs: Node.js, Python, Java, PHP. Licensed in 17 African countries. 53M+ MoMo users. Strong in Ghana, Côte d'Ivoire, Uganda, Cameroon, Benin, South Africa. Developer sandbox available. Competes with M-Pesa for African mobile money.
Pricing
Johannesburg ZA. MTN Group. Per-transaction pricing in local currency per country. Multi-country licensing.
Agent Metadata
Known Gotchas
- ⚠ THREE SEPARATE SUBSCRIPTION KEYS: MTN MoMo requires separate subscription keys for Collections, Disbursements, and Remittances products; automated multi-product integration must subscribe to each product and use product-specific key; automated single shared key for all products creates subscription_key_mismatch
- ⚠ SANDBOX USER CREATION IS PREREQUISITE: MTN MoMo sandbox requires creating API user (POST /v1_0/apiuser with X-Reference-Id) and API key before sandbox auth works; automated sandbox testing must complete user provisioning first; automated sandbox auth without prior user creation creates 404 for all endpoints
- ⚠ X-REFERENCE-ID IS MERCHANT-GENERATED UUID: MTN MoMo transaction ID (X-Reference-Id header) is merchant-generated UUID for idempotency; automated transaction must generate UUID; automated duplicate UUID on retry enables idempotent behavior; automated numeric or non-UUID reference creates invalid_reference_id
- ⚠ COLLECTION REQUEST STATUS POLLING: MTN MoMo Collection status can be polled via GET /v1_0/requesttopay/{referenceId}; automated integration can poll or use callback; automated polling must handle PENDING status while consumer approves on phone
- ⚠ ACCOUNT HOLDER KYC IS BASIC: MTN MoMo account holder lookup (GET /v1_0/accountholder/{accountHolderIdType}/{accountHolderId}/basicuserinfo) returns limited KYC; automated full KYC requires additional MTN partner process; automated treating basic user info as complete KYC creates insufficient compliance verification
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for MTN MoMo Mobile Money API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.