Recently active topics

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.

Hello, on momodeveloper.mtn.com (account aristide@baobabsuper.app, registered 09/09/2026) subscribing to the Collections product fails silently. The API returns HTTP 400 ValidationError: "You've reached the maximum number of Subscriptions (25000) in Product." Disbursements subscribed fine. Could you please clear stale subscriptions or raise the limit so we can subscribe to Collections? Thank you.

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