MoMo API Sand Box Q&A

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

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,

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

Hi, I'm integrating the MoMo Collections API (sandbox) into a server-side application. Requests to /collection/v1_0/requesttopay are being rejected with a WAF block page ("Request Rejected... The requested URL was rejected. Please consult with your administrator") when sent from my cloud-hosted server (Render.com), even though the exact same request succeeds when sent from my local machine using identical code and credentials. Could someone confirm whether cloud/datacenter IP ranges are blocked in sandbox, and if so, help whitelist these outbound IP ranges for my app? 74.220.51.0/24 74.220.59.0/24 Account details: API User ID: b3342b64-ffd2-4746-a771-b884953cc72e Thank you!

Hello MTN MoMo Support/Community,I am integrating the MTN MoMo Collections API for my application, Glowza.I have an active Sandbox subscription:Product: CollectionsSubscription: FakorBorla SandboxEnvironment: SandboxI am trying to provision an API User using the Sandbox User Provisioning API.Endpoint:POST https://sandbox.momodeveloper.mtn.com/v1_0/apiuserRequest headers:X-Reference-Id: [fresh UUID v4]Content-Type: application/jsonOcp-Apim-Subscription-Key: [Collections Primary Subscription Key]Request body:{  "providerCallbackHost": "webhook.site"}The request consistently returns:HTTP/1.1 400 Bad RequestContent-Length: 0There is no response body explaining the error.I have also tried the GET API User endpoint with the same UUID:GET /v1_0/apiuser/{X-Reference-Id}This also returns:HTTP/1.1 400 Bad RequestI have verified that:- The subscription is active.- The subscription product is Collections.- I am using the Collections Primary Subscription Key.- The subscription key is 32 characters.

The Sandbox Collection token/payment flow and Sandbox User Provisioning endpoint are returning HTTP 500 Internal Server Error.I tested both the Primary and Secondary Collection subscription keys, but received the same result.Endpoint:POST https://sandbox.momodeveloper.mtn.com/v1_0/apiuserActivity IDs:e8bd5c96-1955-4c73-9b47-285372a833f0c7d94c70-d94b-419f-81f3-1b3f9606a18e903d8124-fc15-4129-9c88-a47d8c410224Please confirm whether the sandbox services are currently operational and advise when they will be restored.

Hitting 500, while trying to create api user key ??Please help us know,if its sandbox provisioning down or other thing else, or if the server is intentionally down mean like under maintenance !

Hello MTN MoMo team,I'm reporting a sandbox issue that started around 7 July 2026 and that I've been unable to resolve through the usual troubleshooting. I'd be grateful for your guidance on the likely cause and the recommended next step.SummaryMy Collections product subscription shows Active in the portal, and its subscription keys are accepted by the API gateway — but every request that is passed through to the backend hangs and never returns, timing out after roughly 30 seconds. This affects token generation and API-user management alike, so I cannot obtain an access token or provision a new API user.Behaviour observed (reproduced independently from two different networks using raw HTTP, so it is not specific to my application or hosting):Request Result POST /collection/token/ — valid Collections key + existing API user Times out (~37s), no response GET /v1_0/apiuser/{referenceId} — existing API user Times out (~21s), no response POST /v1_0/apiuser — create a new API user

I am trying to generate an api user and key for the sandbox environment.I am sure i am using the correct subscription key, and uuid.I tried the postman collection online. This returns the error: access_token or its expiry date are missing.Authentication is set to none, and i could not get this working.I then tried to create this request in a local postman install.The request looks the same as the online version, but returns error 404.The response body isContent-Length: 0Strict-Transport-Security: max-age=31536000; includeSubDomainsX-XSS-Protection: 1; mode=blockRequest-Context: appId=cid-v1:e996501c-e721-4ac1-97ff-dc6887b85e8cDate: Thu, 14 May 2026 10:02:01 GMT I have these headers: Ocp-Apim-Subscription-Key, X-Reference-Id, Content-Type. The request body is : {"providerCallbackHost":"www.google.com"}Any suggestion to resolve this will be highly appreciated. 

What is the difference between a RequestToPay and a RequestToWithdraw

Hi @all,I configured a user and api key. The call works (requesttopay), but the callback is not executed.I added the host dev.domain.com.xyHeader param for callback is “http://dev.domain.com.xy/webhook/mtnmomo”.No callback.Creating another user with callback domain “domain.com” it works…Any issues with “uncommon” domainnames? 

I’m getting invalid subscription key invalid while testing it in sandbox mode while testing it with live url it give resource not found.Below is for sandbox Mode.URL :: https://sandbox.momodeveloper.mtn.com/v1_0/apiuser headers :: {Authorization: Basic ZmY5NTZkMGYtODYwOC00NmZhLWIzMzEtZjRkNDhmNzAwZTNiOm51bGw=, X-Reference-Id: ff956d0f-8608-46fa-b331-f4d48f700e3b, Ocp-Apim-Subscription-Key: 84dbf7a8a0e44923988a0dd621169ec6, Content-Type: application/json} MtnMomo :: body :: {providerCallbackHost: https://dulu.cm/success} [log]MtnMomo :: apiuserAPI :: 401 :: { "statusCode": 401, "message": "Access denied due to invalid subscription key. Make sure to provide a valid key for an active subscription." }Below is for live testing URL :: https://proxy.momoapi.mtn.com/v1_0/apiuser headers :: {X-Reference-Id: 6e1fcdda-0cb1-4a85-8af6-8e3e6ff31942, Ocp-Apim-Subscription-Key: 0144c9f7b7774f4b8108cc4b243561b6, Content-Type: application/json}body :: {providerCallbackHost: https://dulu.cm/success}apiuse