Ask the MoMo Community

These are the steps I follow, I have created a collection product and I have my primary and secondary subscription keys.First step was to create an API user when was successful Second step, i created an API key for the API user which was successful. Third step, I created an access token for the user under the collections product subscription. Fourth step, I initiated the requestToPay request but it keeps failing with a 400 Bad Request. Is this an issue currently with the system (going by the error, it is not) or is it specific to me?  

I hope you are doing well. I need assistance with an issue I am encountering while trying to generate an API user in sandbox environment.I have followed all the steps outlined in the documentation: Signup For An Account – Completed Subscribe To Our Products – Completed (subscribed to Collection Widget) Manage Your Subscriptions – Subscription is active, and I have received both the primary and secondary keys Generate API User and API Key – This step is failing  To generate the API user, I am using the following endpoint:POST https://sandbox.momodeveloper.mtn.com/v1_0/apiuserHeaders sent:{  "X-Reference-Id": "<uuid-v4>",  "Ocp-Apim-Subscription-Key": "<Subscription-Primary-Key>",  "Content-Type": "application/json"}Body :{  "providerCallbackHost": "webhook.site"} However, the API returns the following error:Response:{  "statusCode": 401,  "message": "Access denied due to invalid subscription key. Make sure to provide a valid key for an active subscription."} I have veri

I'm having trouble signing in to my account. Although the sign-in process appears to be successful, I'm not being redirected to my dashboard afterward. 

I am an owner developer, i have sent my documentation but there is no way to get feedbackcan some one help me with a contact and feedback protocolsthanksK. Baah

I have a mobile application in which people can buy products/services from other users.Is it possible for the sellers, when they signup, to link their mobile money account with this API, so that when the buyers go to buy a product from the seller, they can pay - either with just mobile money too or other payment methods ( I am not sure how that works with this API)  - directly too the sellers mobile money account.Also how would this work with different currencies / countries?Thank you MoMo community!

I'm trying to integrate the MTN MoMo Disbursement API in my Laravel app to generate an access token. However, when switching to the live environment, I receive the following error:"statusCode": 401, "message": "Access denied due to invalid subscription key. Make sure to provide a valid key for an active subscription."

I am getting remittance transfer bad request error message. my request body is this. any wrong?{  "amount": "600",  "currency": "EUR",  "externalId": "00004335",  "payee": {    "partyIdType": "MSISDN",    "partyId": "56733123450"  },  "payerMessage": "MoMo Market Payment",  "payeeNote": "MoMo Market Payment"}

https://momodeveloper.mtn.com/sandbox/Hello MoMo community,I get the below error message on trying to access the sandboxOops, something went wrong

I need this keys please someone help me how to fine them am new

The documentation is very conclusive but the last step in the process was not yielding me what I wanted and I found a video on youtube which used the reference id (uuid) as a username and the api key as the password. As shown in this image https://postimg.cc/87S93Mrk . There was no token. Please I need to clarify the contents of the last request. I don’t want to say the documentation is wrong but the difference is the video used basic auth in the authorization and followed it as I described earlierResponse ```{    "providerCallbackHost": "string",    "targetEnvironment": "sandbox"}```

{StatusCode: 500, ReasonPhrase: 'Server Error', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:{  X-XSS-Protection: 1; mode=block  Request-Context: appId=cid-v1:e996501c-e721-4ac1-97ff-dc6887b85e8c  Date: Wed, 24 Sep 2025 18:39:51 GMT  Content-Length: 0}} what is the fixed

So I want to use Collections and Disbursement APIs. I want to include them in my School Data Management System(SDMS) in Uganda. And my Question is, I have several schools Using my System, So the parents will be paying School Fees directly through the System. Should that money first go through my phone (Using the Collections API) such that i pick my commission and there after my phone sends it to the respective Schools (Using Disbursement). I really need to know how am going to handle this.Someone guide me on what is required.

i have got error in laravel “Unable to obtain a new access token.”in sendbox 

Hello MTN MoMo Community,I'm successfully creating payment requests in production (getting HTTP 202 responses), but customers are not receiving any SMS notifications to authorize the payments.🔧 Current Setup:Environment: Production with live keys Country: Côte d'Ivoire API: Collections requesttopay endpoint Response: HTTP 202 (request created successfully)✅ What's Working:Authentication is successful Payment requests are created without errors API responses indicate success Using correct production URLs and target environment❌ The Issue:Customers receive no SMS notifications When customers dial the USSD code, they see "No pending transactions" Transactions appear to be created but not pushed to customer devices❓ My Questions:Are there specific payload parameters required to trigger SMS delivery? Do I need special headers beyond the standard ones for SMS notifications? Is there a separate SMS trigger API call required after requesttopay? Are there customer number validation requirement

I am consuming the MTN Open API and most of the endpoints worked except for some specific endpoints which I would enlist below;Kindly note that the response I receive from these are all BAD REQUEST so kindly help me out in determining what is the issue; Request to Pay:  POST https://sandbox.momodeveloper.mtn.com/collection/v1_0/requesttopayHeaders: X-Target-Environment X-Callback-Url        X-Reference-Id Ocp-Apim-Subscription-Key Authorization  Request Body: {"amount": "2.0","currency": "GH","externalId": "7916d515-ab40-4bba-bb67-b68bfb13b94c","payer": {"partyIdType": "MSISDN","partyId": "23354****414"},"payerMessage": "Kindly accept for payment of TEST","payeeNote": "Thanks for paying for Test"}   Disbursement / Transfer       POST: https://sandbox.momodeveloper.mtn.com/disbursement/v1_0/transfer       Headers:   X-Target-Environment   X-Callback-Url          X-Reference-Id   Ocp-Apim-Subscription-Key   Authorization Request Body: {"amount": "2.0","currency": "GH","externalId": "e4f7

I tried creating an api user in the postman by sending a post request on postman to this link https://sandbox.momodeveloper.mtn.com/v1_0/apiuser. The post request contained in my header X-Referene-Id(a random uuid generated by a uuid generator), Ocp—Apim-Subscription-Key(which is the primary key gotten after subsrcibing to a product, in my case I subsricbed to the collection widget producr) and Content-type(whose value was application/json). After doing all of this and sending the post request, I am getting a status code of 401 “saying Access Denied due to invalid subscription key. Make sure to provide a valid key for an active subscription”. I have confirmed multiple times that I use the primary key and i even tried out the secondary key but same thing, I have tried to open another account to subscribe to a new product, yet still the same thing. I will sincerely appreciate it if this can be attended to as soon as possible 

I trying to get an api subscription key for collection and disbursement subscribe page activates but can’t subscribe to any product what might be the issue?

i dont know when i try to create the access token in the sandbox i get 401 response invalid client .any one help me

we are working on a time sensitive important project and encountering login failure while trying to obtain an access token using basic authentication

I have tested the API but i am trying to golive but when filling the form this url https://momodeveloper.mtn.com/content/Nigeria_KYC_Form.pdf appears to be deadHow do i resolve this?

Hi everyone,I'm currently in the process of integrating MTN MoMo API for a project under my company, Nyamora Petroleum and General Trading Co. Ltd (South Sudan registered), and I’d appreciate support or insights from anyone who has gone through this before.💳 1. Personal Bank Account Use for BusinessOur business would like to use a personal bank account (under my name – Riak Mawut Angui) to receive MoMo settlement payments temporarily.Has anyone done this before? Is it allowed under MTN’s onboarding policy? If yes, is a signed authorization letter from the board linking the personal account enough? 📝 2. Mandate Form ConfusionI'm the sole authorized person managing this project.Need help understanding: Can one person sign off on the Mandate Form? How should the passport photo be submitted – is digital okay or does it need to be manually endorsed? 📱 3. Mobile Number for MoMo APII plan to use my personal number as the MoMo line for OTPs and system access.Question: Can this one numbe

What are the countries where MoMo APIs are live ?

I successfully created it using/v1/0/apiuser/v1/0我使用/v1/0/apiuser/v1/0成功创建了它I successfully created it using/v1/0/apiuser/v1/0 apiuser, but using/V1_0/apiuser/{X-Reference Id} does not return any data for apiUser. Which API do I need to use to obtain apiUser? I can successfully obtain apiKey through/v1.0/apiuser/{X-Reference Id}/apikey  

I have been looking through the documentation and can’t find much information about the collection widget product. All I could find is that it enables a developer or partner to integrate a MoMoPay checkout button to accept Mobile Money payments on your e-commerce site. but what differentiates it from the othe collections product and how can we implement it in the sand box.

Hi!When I do a POST to the CreateAccessToken endpoint I get a response where the token_type has a value set to "access_token" instead of something like "Bearer". I’m expecting the token_type to be Bearer since the Transfer endpoint documentation states that the Authorization header should be the “Bearer Authentication Token generated using CreateAccessToken API Call”.Am I missing something?Any help/advice would be greatly appreciated!