Ask the MoMo Community

Good day, I would like to seek clarification regarding the requirements for using the live Mobile Money API.Could you please confirm whether I need to register and use a dedicated Mobile Money agent number to access the live API, or if I can use any Mobile Money number, provided it is registered and active? I would appreciate your guidance on this matter so that I can proceed with the integration correctly. Thank you for your assistance, and I look forward to your response. Regards

Hello MTN MoMo Developer Support Team,I am developing a multi-tenant order management and POS platform for businesses in Ghana that primarily conduct sales through WhatsApp.Our platform allows multiple independent businesses to register, manage customer orders, and track payments. Each business may have multiple MTN MoMo numbers for receiving payments.Our current payment process: Customers place orders with businesses through WhatsApp. The business manually records the order in our platform. The customer sends payment directly to the business's MTN MoMo number using the traditional USSD (*170#) process. The business manually confirms receipt of the payment and updates the order status. What we want to achieve:We want to integrate with MTN MoMo so that our backend can automatically detect incoming payments to each business's registered MoMo wallet, retrieve the transaction details, and help match those payments to orders.Importantly, we do not want to initiate payment requests thr

Hello MTN MoMo Support,My Collections subscription, “Paiements AgriZone,” is active, but I am unable to retrieve my existing Sandbox API User. The request GET /v1_0/apiuser/{X-Reference-Id} returns HTTP 500 directly from the developer portal.Activity ID: 398d0d31-c716-44c3-b40e-551b4d25ffb7The access token request also returns HTTP 500.Activity ID: d16207d8-a437-4c90-a2b2-b178d713066aCould you please investigate whether the Sandbox User Provisioning and Collections Token services are experiencing an issue and advise me on how to proceed?My goal is to complete the integration of MTN MoMo Collections Sandbox with my AgriZone application.Thank you for your assistance.Best regards,AgriZone Developer

Getting internal seever error 500 while creating api user and api key 

Hello MTN Developer Support,I am integrating the MTN MoMo Collections API in the sandbox environment.My API User exists and can be retrieved successfully using GET /v1_0/apiuser/{id} (HTTP 200).However, POST /v1_0/apiuser/{id}/apikey returns HTTP 500 Internal Server Error.The response includes activityId: 25f7ca0a-8d3d-434e-a619-30936b328619Could you please investigate whether API Key provisioning is currently operational and whether my subscription requires additional activation?Thank you.

Hello MTN MoMo developers,I am integrating MTN MoMo Collections into my business system in Uganda. My Collections subscription is active, but I cannot create a sandbox API user.Endpoint: POST https://sandbox.momodeveloper.mtn.com/v1_0/apiuserError: HTTP 500 Internal Server Error.The API-user lookup request also returned HTTP 500. In addition, the developer application page displays an “Oops, something went wrong” error.Activity IDs from my failed requests: API-user creation: 4f421cf7-3fb8-474f-bb80-056712eb9db6 API-user lookup: 07316d2d-858e-4372-8982-24e3378ba32c Could anyone from MTN confirm whether sandbox provisioning is currently operational, whether my developer account needs additional application registration, and when this issue is expected to be investigated or resolved?Thank you.

====================================================================MTN MoMo sandbox — API user provisioning====================================================================Subscription key : ba6f8194...b59d  (len=32)Callback host    : example.comBase URL         : https://sandbox.momodeveloper.mtn.com[1/2] Creating API user      X-Reference-Id : 7c3a8651-7978-4b00-9302-c900f742e710      Response       : HTTP 500      Body           : { "statusCode": 500, "message": "Internal server error", "activityId": "16e27f8e-4ec1-4ff1-9960-79f2606ea327" }FAILED at step 1 — MTN rejected API user creation.Diagnosis:  MTN's backend returned an internal error.  This is almost always one of:    • No registered developer application on your      MTN profile (register one at      https://momodeveloper.mtn.com/developer).    • An MTN-side sandbox outage (transient — retry in      an hour, or check their community forum).  Copy the activityId from the body above and include it  in any support ticket —

Hi team,Sandbox provisioning is failing for me. Creating an API user returns HTTP 500 with no MTN error code, so the request appears to fail before it reaches the backend.Endpoint:POST https://sandbox.momodeveloper.mtn.com/v1_0/apiuserHeaders:- X-Reference-Id: new UUID v4 on each attempt- Ocp-Apim-Subscription-Key: Collections primary key (subscription is Active)- Content-Type: application/jsonBody:{"providerCallbackHost": "webhook.site"}Response:{  "statusCode": 500,  "message": "Internal server error",  "activityId": "3b3ab7c7-1707-4073-a48a-4bd60e1c63ea"}Date: 16 October 2026Client: Postman (same result from the portal's Try it feature)Could you check the activity ID and confirm whether the sandbox provisioning service is currently operational? If anything in my request is wrong, please let me know what to change.Thanks,

Sandbox provisioning on sandbox.momodeveloper.mtn.co.rw is failing for my Collections subscription (started 2026-10-14). POST /v1_0/apiuser with my subscription key returns 404 "Resource not found". POST /v1_0/apiuser/{id}/apikey returns 500. Without a key the gateway returns 401, so the route exists. Activity IDs: e2bd02ef-395b-4c72-afee-30c8117b00f9, 5dd1aca2-f6ab-420d-96b0-6411db42e2cc, 7b12d60c-5f5c-4cd4-b37a-52910d78b43e. Please enable sandbox user provisioning for this subscription.

Hello MTN MoMo Developer Support,I need assistance with my MoMo API Sandbox Disbursements subscription.Product: DisbursementsApplication: DIFFERENT.TECH FinanceEnvironment: SandboxBase URL: https://sandbox.momodeveloper.mtn.comTarget Environment: sandboxMy Disbursements subscription is Active.I have verified both my Primary and Secondary subscription keys locally without exposing them.The following sandbox operations are returning:HTTP 500 Internal Server Error1. OAuth Disbursement token requestActivity ID:7da2522e-1410-4ae2-97be-c314a527ec962. Existing Sandbox API User lookupActivity ID:959f2b5e-49cb-48ad-ad80-12fd0d4f5b743. Creating a new Sandbox API User using the Primary subscription keyActivity ID:8a6718ae-1be1-412b-9ca0-eb2944f99d4f4. Creating a new Sandbox API User using the Secondary subscription keyActivity ID:c40a6f85-4b83-4221-9e79-17a6b6af6ddaBoth Primary and Secondary subscription keys produce the same HTTP 500 result.Please check whether my Sandbox User Provisioning and D

Hello MTN MoMo Developer Support Team,I am applying to move our DIFFERENT.TECH integration to production in Zambia using the Disbursements product.During the Zambia Go-Live application, I downloaded the provided Zambia KYC contracting package. The package contains the following documents:Mobile Money Account Details Form Mandate Form Self Liquidation Application FormHowever, the Self Liquidation Application Form appears to reference MTN Uganda Limited and MTN Uganda throughout the document, while our business and Go-Live application are for Zambia.Could you please confirm:Which documents are required specifically for a Zambia Disbursements Go-Live application? Should we complete the Self Liquidation Application Form that references MTN Uganda, or is there a Zambia-specific form that should be used instead? For Disbursements, which option/service should be selected on the Mobile Money Account Details Form? Are there any additional Zambia-specific KYC documents required before we upload

Failing to subscribe for collections. Any help i can receive?

Hello, I'm registered on the MoMo Developer sandbox portal. When I try to create a sandbox API user (POST /v1_0/apiuser) using my Subscription Key from the Collection/Get Paid product, I get the error "401 - Access denied due to invalid subscription key". I confirmed I am subscribed to the product and I am using the Primary Key from my profile. Could you help me understand why this key is not being accepted?

I have an active Collections subscription in the MTN MoMo Developer sandbox. Both the Primary and Secondary Collections subscription keys return HTTP 401 when calling POST /v1_0/apiuser on the sandbox API. The response is: “Access denied due to invalid subscription key. Make sure to provide a valid key for an active subscription.” DNS and HTTPS connectivity to the sandbox endpoint are working. Please verify or reactivate the Collections sandbox subscription/API Management keys for my developer account.

Hello MoMo team,I am unable to subscribe to the Collections product on the MoMo Developer Portal. I have followed the standard steps — signed in, navigated to the Collections product, entered a subscription name, checked "I agree to the Terms of Use," and clicked Subscribe — but the subscription never completes and my profile page continues to show "You don't have subscriptions yet."

Hello,I cannot subscribe to the Collections product in the sandbox. The subscriptionrequest fails server-side with HTTP 400.Steps to reproduce:1. Log in to momodeveloper.mtn.com2. Go to Products > Collections3. Enter a subscription name, accept the terms, click SubscribeRequest:POST /developer/users/<my-user-id>/subscriptions/<id>?api-version=2022-04-01-previewResponse: HTTP 400 Bad Request{"error":{"code":"ValidationError","message":"You've reached the maximum numberof Subscriptions (25000) in Product. Please delete one or more Subscription(s)from Product to continue, or consider upgrading your plan to increase thelimit.","details":null}}My account has no subscriptions at all — the page shows "You have nosubscriptions yet". The 25000 limit is the Azure API Management cap on theProduct itself, not on my account, so there is nothing I can delete on my side.Could someone on the MoMo team clean up stale sandbox subscriptions on theCollections product, or raise the APIM tier

Account: weruku@gmail.com (registered 09/11/2026). I cancelled Collection Widget (mpf-widget). I cannot subscribe to Collections — the button does nothing and the new subscription never appears on my profile. I need sandbox Collections (not Widget) for Uganda.

Hello,I am trying to subscribe to the Collections product on the MTN MoMo Developer Portal in order to integrate MTN MoMo Côte d’Ivoire with our OneFlow platform.However, the subscription creation consistently fails with an HTTP 400 error and the following message:You've reached the maximum number of Subscriptions (25000) in Product. Please delete one or more Subscription(s) from Product to continue, or consider upgrading your plan to increase the limit.Could you please increase the subscription capacity for the Collections product or enable my subscription manually?Requested subscription name: OneFlowPay-Collections-Sandbox-CII can also provide screenshots of the failed POST request and the full error response if needed.Best regards,

How to get my api key

I have successfully registered on the MTN MoMo Development Portal and subscribed to Collection Widget. However, when I try to subscribe to the Collections API product, clicking subscribe does not create a subscription. My profile still shows only Collection Widget as Active. I need the Collection API for RequestToPay integration. Please assist with enabling the Collections API subscription on my developer account. 

I'm building a marketplace-style platform where a payment is collected upfront but shouldn't be paid out immediately — it needs to be held and only released to the recipient once the payer approves a completed stage of work, which could be a few days after collection.Is there any native support in the Collections/Disbursements APIs for a conditional or delayed release like this, or is holding funds purely something I'd need to handle in my own backend — i.e., collect immediately via the Collections API, hold the amount in my own ledger, and only call Disbursements once the stage is approved? Trying to understand where the boundary is between what the API handles and what has to live entirely on my side. Any guidance appreciated.

Hello MTN MoMo Team,I am developing Amasampo Palletmarket, an online marketplace operating in Zambia where sellers can list products and buyers can find and purchase items.I would like to integrate MTN MoMo so that our website can receive real payments, including seller subscription/listing fees and potentially customer payments.I have already created an MTN MoMo Developer account and I am interested in the Collections API or Collection Widget for Zambia.I would like guidance on the requirements for going live in Zambia. In particular:Can an individual or sole proprietor apply for production access, or must the business first be formally registered?What KYC documents are required in Zambia?Do I need an MTN MoMo merchant/business wallet for Collections?I currently have an MTN MoMo agent line. Can this line be used for API Collections, or will I need a separate merchant/business MoMo account?Which product should I apply for if I want customers to make payments directly from their MTN MoM

Hello,My name is Nana, and I’m working on a POS platform for businesses in Ghana.We are currently integrating Mobile Money payments into Tabworthy through a payment provider (Paystack), and we have encountered a customer authentication flow that we'd like to understand directly from MTN.The current flow for an MTN customer making their first MoMo payment through our application is: The customer provides their MTN phone number. We initiate the Mobile Money payment. MTN sends a 6-digit code to the customer's phone. The customer has to provide that 6-digit code to the merchant/cashier. The code is entered into the payment flow. The customer then receives the normal MTN MoMo prompt and enters their MoMo PIN. The payment is completed. Interestingly, after the customer completes this process once, subsequent payments do not appear to require the 6-digit code again.Our payment provider has confirmed that this 6-digit code is generated and controlled by MTN and that they cannot byp

Hello,I’m writing this topic because we have successfully completed the integration and sandbox testing of the MTN MoMo Collections API into Equinox, our SaaS invoicing and payment platform : equinox.passerel.caSeveral customers are waiting for us to enable MTN Mobile Money payments in production.Cabinet Passerel, the company operating Equinox, is incorporated in Canada. During the Go-Live process for Benin, we noticed that the onboarding documents request local information such as an IFU, physical address and other Benin-specific company documentation.Can a Canadian company obtain production access to the MTN MoMo Collections API for Benin, or is a locally registered entity/establishment required ?Our technical integration is already complete and working successfully in the sandbox.Best regards,

Hello,I am integrating the MTN MoMo Remittance Sandbox API from a cloud-hosted server environment.The integration previously worked successfully. We were able to:generate an OAuth access token; validate a Sandbox account holder; submit a Remittance transfer (202 Accepted); retrieve the transfer status as SUCCESSFUL.However, the OAuth endpoint is now being rejected:POST https://sandbox.momodeveloper.mtn.com/remittance/token/Instead of the documented OAuth JSON response, MTN returns:HTTP status: 200 Content-Type: text/html Content-Length: 247 message: Request RejectedA Support ID is also returned for the rejected request.The issue appears consistent with a Sandbox WAF/network restriction affecting server-to-server requests from a cloud environment.Could you please confirm:whether the MTN Sandbox WAF may be blocking our server requests; whether an outbound IP or IP range needs to be allowlisted; whether there are specific network/IP requirements for server-to-server access to the Remittan