Recently active topics

Hello MTN MoMo Support Team, I am integrating MTN MoMo Collections Sandbox with WooCommerce for Knoxnet Tech Centre of Applied Science and Technology (KTCAST) in Zambia. When I open Collections on the MTN Developer Portal, I see these messages:"You don't have subscriptions yet.""You've reached maximum number of subscriptions." My WooCommerce gateway is configured with the sandbox Collections endpoints. The MTN MoMo payment option appears at checkout, but initiating a payment fails with "Payment request failed, please try again." I have also noticed recent community reports of similar sandbox subscription and API provisioning errors. Could you please confirm whether there is a Collections Sandbox subscription or provisioning issue, and advise how I can activate or restore my subscription? Thank you,KTCAST – Zambia

Hello All,Please I am currently having MTN sandbox API-user creation issues for an application that I built. The collection subscription is active, yet I am getting “404 not found” error message when I try to create the MTN sandbox API-user on POSTMAN.COM.The HTTP status is 404Message is “Resource not found”The date of last attempt is 23rd October 2026 at 2:50amKindly assist meRegards

Hello Team,Please find below issue for your attention as per the above subject or title.404 Not Found HTTP status: 404 Message: Resource not found Date: 23/10/2026  Time: 2:50am Collection subscription is active yet I am getting the above feedback. Kindly assist me

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 —

====================================================================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 : 650cc539-4975-46e6-a996-d75880580b9d      Response       : HTTP 500      Body           : { "statusCode": 500, "message": "Internal server error", "activityId": "5c51b72c-68dd-433d-ad6c-b2195900795b" }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,

Subject: MTN Sandbox Collections Token Endpoint Returns HTTP 500Hello MTN MoMo Developer Support,I am integrating the MTN MoMo Collections API for my escrow application in Zambia.My Collections subscription is active, but I consistently receive an HTTP 500 Internal Server Error when requesting an access token. Endpoint: POST https://sandbox.momodeveloper.mtn.com/collection/token/ Environment: Sandbox Response: 500 Internal Server Error Activity ID: 7cde56b5-c63a-4060-ab20-1abb11e8ed4b Request time: 15 October 2026, 05:27:49 GMT I tested the request directly from Windows PowerShell using Basic authentication, my Collections subscription key, the sandbox target header, and an empty request body.Please investigate this activity ID and confirm whether the Collections token service is operating correctly for my account.Thank you.

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.

MoMo API Upgrade - One API The MoMo API Platform is being enhanced to strengthen security, standardisation, monitoring, and operational efficiency. As part of these improvements, three mandatory implementation changes are being introduced, which all partners must implement, validate, and complete within the prescribed timelines.Credential Migration (New User ID & Credential Token) Token Generation Changes (Mandatory X-Target-Environment Header) Base URL ChangesThese are the primary areas that should be validated during partner readiness.  Key Message for Partners The MoMo API platform enhancement requires partners to update their base URL from https://proxy.momoapi.mtn.com or https://ericssonbasicapi1.azure-api.net to the new MoMo API base URL: https://momoapi.momo.africa. API endpoints, business functionality, request payloads, and response structures remain unchanged. Partners are also required to update their credentials by:Replacing the API User with the UserID. Replacing the A

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 Support,I am integrating the MTN MoMo Collections API in the Rwanda Sandbox.My Collections subscription is Active and the subscription key is loaded correctly from my .env configuration.I am trying to create an API User:POST https://sandbox.momodeveloper.mtn.co.rw/v1_0/apiuserThe request contains:- X-Reference-Id: UUID v4- Ocp-Apim-Subscription-Key: Collections subscription key- providerCallbackHost: solve-arrange-lying-qualified.trycloudflare.comThe callback host has been tested successfully:GET /api/health -> HTTP 200POST /api/momo/callback -> HTTP 200However, the API User creation consistently returns:HTTP 401{  "statusCode": 401,  "message": "Access denied due to invalid subscription key. Make sure to provide a valid key for an active subscription."}Please verify whether my Collections Sandbox subscription is correctly provisioned for the Sandbox User Provisioning API (/v1_0/apiuser), and reset/re-provision the API Management subscription key if necessary.Thank you.

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?

Hi MTN MoMo developer team,I'm building a platform that uses both the Collections and Disbursement APIs for Ghana (GHS).I noticed the Disbursement product exposes two separate operations — /transfer and /deposit — and I have a straightforward question about how they differ in terms of fees:Does a /deposit call to a MoMo wallet carry the same tiered transaction fee as a /transfer call, or is it treated differently? If the fee structures are different, what is the fee charged to the business account for a /deposit to a Ghana MoMo wallet? Is the /deposit endpoint available and supported for Ghana (GHS) specifically, or is it only available in certain markets?A direct answer to question 1 is the main thing I need — specifically whether calling /deposit instead of /transfer results in a different or lower fee for the business initiating the transaction.

Bonjours à tous Sur le portail l'option 'Go-Live' : Sélectionnez le pays d'exploitation dans la liste prédéfinie pour activer les produits dans ce pays, la Guinée Conakry ne figure pas sur la liste.Comment activer les produits d'exploitation pour la Guinée Conakry sur  'Go-Live' ?