How does an MTN MoMo payment work?
MTN’s MoMo API splits payments into two products: Collections for money coming in and Disbursements for money going out. Each call starts by creating an access token for the merchant’s API user.
A pay-in is a request to pay. The shopper chooses MoMo at checkout and enters their mobile number. The merchant or its provider sends a request to pay with the amount and the customer’s account number, and the MoMo platform answers with HTTP 202 Accepted. The merchant then tells the shopper on screen that a payment is waiting for approval. The request stays PENDING until the customer reviews it on their own phone, through USSD or the MoMo app, and approves or rejects it with their PIN. If the customer approves, the funds move and the status becomes SUCCESSFUL. Otherwise it becomes FAILED.
The result arrives by callback or by status query. If the merchant passed a callback URL, the platform sends one callback when the request reaches a final state. MTN’s documentation says the callback is sent only once and recommends polling the transaction status with a GET request as a fallback. Callback hosts must use HTTPS and be registered when the API keys are created.
Collections also include pre-approval, where the customer approves once and the merchant can then debit the wallet without asking each time, which suits subscriptions.
A payout is a transfer. The merchant sends a transfer request, and the platform moves funds from the merchant’s account to the customer’s wallet and reports the final state by callback or status query. The Disbursements product also includes a refund operation and an account holder check that confirms a wallet is active before money is sent.
Why does MTN MoMo matter for merchants?
Scale across several markets. MTN reported 70.8 million monthly active MoMo users in June 2026, up 12.1% in a year, and fintech transactions worth US$330.5 billion in the first half of 2026. Each market has its own MoMo wallet in the local currency, so a merchant selling in several of them needs a route per country.
Ghana is the largest single MoMo market. MTN Ghana counted 18.3 million active MoMo users in June 2026, and the Bank of Ghana counted 26.4 million active mobile money accounts across all providers in August 2026. Since GhIPSS launched mobile money interoperability in May 2018, money can move between wallets on different networks and to bank accounts. The Electronic Transfer Levy, charged on mobile money transfers from 1 May 2022, was repealed with effect from 2 April 2025. MTN Ghana completed the separation of its Mobile Money business into Mobile Money Fintech Limited on 31 March 2026, to meet the local ownership rule in the Payment Systems and Services Act, 2019.
Uganda is the next largest. Business Day reported that MTN Uganda’s active fintech users grew 11.5% in the first half of 2026, with 2.6 billion transactions worth UGX 113.3 trillion. Across Uganda, Rwanda, Zambia and MTN’s other markets in Southern and East Africa, MoMo monthly active users rose 13.2% to 27.2 million.
Nigeria is newer. MTN’s payment service bank, MoMo PSB, reached 5.0 million active wallets in June 2026, a small base next to Nigeria’s larger wallets.
Online card payments from a wallet. MTN says its virtual card by MoMo, built with Mastercard, is live in Rwanda, Uganda, Côte d’Ivoire, Cameroon, Nigeria, Zambia and Benin, with about 954,000 cards issued in 2026 up to June.
Is MTN MoMo available in Côte d’Ivoire and Cameroon?
Yes. The BCEAO lists MTN Mobile Financial Services Côte d’Ivoire as a licensed electronic money institution offering MTN Mobile Money (MoMo), and payments there run in XOF. MTN Côte d’Ivoire reported 4.9 million active MoMo users in September 2025. An April 2024 survey by the national statistics institute, reported by Ecomatin, put MoMo at 23.5% of money transfers, behind Wave at 31%. In Cameroon, MoMo runs in XAF, and MTN Cameroon had 13.4 million subscribers in June 2026.
What can go wrong?
Most failed MoMo payments are approvals that never happen. The customer misses the prompt, enters a wrong PIN or rejects the request, and the payment stays pending or fails. MTN says the most common reason behind its generic INTERNAL_PROCESSING_ERROR is insufficient funds in the customer’s wallet.
Missed callbacks cause the second set of problems. Because each callback is sent once, a merchant that relies on it alone can leave a paid order unconfirmed. A status query for every pending request closes that gap.
Payouts need care with numbers. The account holder check confirms that a wallet is active, not that it can receive a given amount, so a transfer can still fail. A payout or refund that times out should be checked by status query before it is sent again, or the customer may be paid twice. There is no card-scheme chargeback on a MoMo payment, so disputes are handled between the customer, MTN and the merchant.
Markets differ. Each country has its own MoMo platform, currency, limits and fees, so a provider connected to MoMo in Ghana does not automatically cover Uganda or Cameroon.
How would Omno handle MTN MoMo?
A merchant would show MoMo in the hosted checkout, where the customer enters a phone number and sees a clear prompt to approve, or offer it on its own checkout through Direct Links. Routing rules would send the request to a provider that holds an MTN MoMo connection for that country. In the hosted checkout, if that provider is unavailable or rejects the request, the payment would cascade to the next provider in the rule until one accepts. Pending payments would be checked by status query as well as callback, and the final result would reach the merchant by webhook, which is the source of truth for confirming an order. Payouts could be limited by the customer verification level that the merchant’s own verification provider sets, and the routing-decision log would record which provider handled each step.