Unanswered questions

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

Hello,My name is Nana, and I’m working on a POS platform for businesses in Ghana.We are currently integrating Mobile Money payments into Tabworthy through a payment provider (Paystack), and we have encountered a customer authentication flow that we'd like to understand directly from MTN.The current flow for an MTN customer making their first MoMo payment through our application is: The customer provides their MTN phone number. We initiate the Mobile Money payment. MTN sends a 6-digit code to the customer's phone. The customer has to provide that 6-digit code to the merchant/cashier. The code is entered into the payment flow. The customer then receives the normal MTN MoMo prompt and enters their MoMo PIN. The payment is completed. Interestingly, after the customer completes this process once, subsequent payments do not appear to require the 6-digit code again.Our payment provider has confirmed that this 6-digit code is generated and controlled by MTN and that they cannot byp

Bonjour,Je développe une application appelée MenuGo pour recevoir les abonnements de restaurants.Mon compte indique que j’ai atteint le nombre maximal d’abonnements. Le produit Widget de collecte est actif, mais il indique qu’il ne possède pas d’API.Je souhaite utiliser l’API Collections / Request to Pay en environnement sandbox.Pouvez-vous m’indiquer quel produit souscrire et comment créer correctement l’API User et l’API Key nécessaires ?

Hello,I’m writing this topic because we have successfully completed the integration and sandbox testing of the MTN MoMo Collections API into Equinox, our SaaS invoicing and payment platform : equinox.passerel.caSeveral customers are waiting for us to enable MTN Mobile Money payments in production.Cabinet Passerel, the company operating Equinox, is incorporated in Canada. During the Go-Live process for Benin, we noticed that the onboarding documents request local information such as an IFU, physical address and other Benin-specific company documentation.Can a Canadian company obtain production access to the MTN MoMo Collections API for Benin, or is a locally registered entity/establishment required ?Our technical integration is already complete and working successfully in the sandbox.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, I am a developer in Uganda building a Flutter web/mobile application called Walking With Christ. I already have an MTN MoMo merchant code and would like to integrate the MoMo API Get Paid/Collections service.When I go to the MoMo API developer portal and click “Sign up with MoMo API,” I am redirected to momoapi.mtn.com/signup, which returns Error 404.Please advise how I can create a new MoMo API developer account and obtain sandbox access for Uganda.

Hello, I am a developer in Uganda building a Flutter web/mobile application called Walking With Christ. I already have an MTN MoMo merchant code and would like to integrate the MoMo API Get Paid/Collections service.When I go to the MoMo API developer portal and click “Sign up with MoMo API,” I am redirected to momoapi.mtn.com/signup, which returns Error 404.Please advise how I can create a new MoMo API developer account and obtain sandbox access for Uganda.

Hello, How can I get API keys for get Paid (Collections | Enable remote collection of bills, fees or taxes.) of production?

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.

Am a developer from another country and want to start the business but i don’t know what’s needed to start the business.