Unanswered questions

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 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' ?

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 , I also tried to Fork the SandBox Provisioning Collection using run in Postman.I get this error.Collection doesn't existThis collection seems to have been deleted or is no longer publicI kindly need assistance on a work around 

Hello,I am integrating the MTN MoMo Disbursement API in a Ghana-based application.My Disbursements subscription is Active, and I have successfully created a Sandbox API User and API Key.The following tests are successful:OAuth token request: HTTP 200 Account-holder validation: HTTP 200 API User configuration lookup: HTTP 200However, the following Disbursement operations consistently return HTTP 400 with an empty response body:GET /disbursement/v1_0/account/balance POST /disbursement/v1_0/transfer GET /disbursement/v1_0/transfer/{referenceId}I have also tested the documented Aggregator Transfer request format using EUR, CUSTOM_PAYMENT, and a valid UUID v4 X-Reference-Id, but the transfer still returns HTTP 400.The API User configuration returns targetEnvironment: sandbox.Could someone help me understand what could cause these Disbursement endpoints to return HTTP 400 when OAuth and account-holder validation are successful?Thank you.