Skip to main content

Recently active topics

14
K
kbkukuborNew Member
 MoMo Ghana Developers
I
IshimwejayNew Member
 MoMo Rwanda Developers
A
allan.ddamuliraCommunity Manager
 How-To
MoMo API Production Configuration .F.A.Q.

Account details. API_USER & API_KEY Production  Subscription Keys Production configurationsChanging from sandbox configs to production environment details required one to do the following; - Account details.In SandBox, the API_USER and API_KEY are self-generated by calling the APIs in the sandbox-user-provisioning. In production, these details are got from the Partner Portal (https://mobilemoneyreadonly.mtn.co.ug).  The account credentials required to sign in are;-Username (e.g username.sp1) → this is shared one on one by the account manager. MSISDN → a fully registered MTN SIM Card that can receive an OTP. Note: Partner Portal urls are country specific above shared example is for Uganda, an equivalent for another country can be got from your account manager. API_USER & API_KEYOn navigating to the Partner Portal; -Sign in using the option of “Forgot Password” or “First Login”. An OTP is sent to the MSISDN which you can use to sign in and then set/reset your password.   Once si

37179
A
B
BigMoshNew Member
 MoMo API Production Q&A
Preapproval Renew and ValidityTime (Ghana)

Hi Team,I am currently developing a recurring payment solution using the MoMo API (Ghana environment) and would like to clarify the expected behavior for pre-approval mandates to ensure a smooth user experience.1. Renewing Active Mandates:If an MSISDN already has an active pre-approval mandate, what happens if a second POST /preapproval request is sent to that same number before the current one expires?Does the new request overwrite the existing one and reset the validityTime? Does it return a PREAPPROVAL_EXIST_PENDING error even if the previous mandate is already in a SUCCESSFUL state? Is there a recommended way to "extend" a mandate without requiring the customer to perform a fresh approval?2. Maximum validityTime Constraints:Regarding the validityTime parameter in the POST /preapproval payload:What is the maximum allowable value (in seconds) for this field in the Ghana Production environment? Are there platform or regulatory caps (e.g., 365 days) that would cause a validation error

40
B
O
othkimweriNew Member
 MoMo Uganda Developers
L
lukwatajohnNew Member
 MoMo API Sand Box Q&A
S
simzNew Member
 MoMo Zambia Developers
S
SILASNew Member
 MoMo API Sand Box Q&A
S
shackstechNew Member
 MoMo Uganda Developers
E
ExamEaseNew Member
 MoMo API Production Q&A
Request for Technical Guidance on MoMo Real Time Intergration in Django Project

Dear MTN MoMo Developers Team,I amSoftware Engineering student currently developing a Django-based web application that requires real-time MTN MoMo payment integration.I am writing to respectfully seek your technical guidance and support regarding the proper implementation of MTN MoMo APIs within my project. Specifically, I would like assistance with configuring secure API authentication, handling payment request callbacks (webhooks), and ensuring real-time transaction verification within a Django backend environment.My goal is to implement a robust and production-ready integration that complies fully with MTN MoMo developer standards and security requirements. I have reviewed the available developer documentation, but I would greatly appreciate clarification and best-practice recommendations, particularly concerning sandbox testing, callback URL configuration, and transaction status confirmation.Kindly let me know if there are recommended resources, SDKs, sample Django implementations

180
E
C
ColinMcLaughlinNew Member
 MoMo API Production Q&A
D
DdamulaCommunity Manager
 MoMo PWA Mini App Integration
MoMo PWA IntegrationPWA

Guidelines to Installing and testing partners PWA with the MoMo MicroSiteJourney InitializationReceiving: START_JOURNEYAutomatically sent when your microsite loads in the mobile appToken Validity & Refresh RequirementsThe micrositeToken is valid for 10 minutes. If no activity (no heartbeats) occurs within 10 minutes, the session ends and the user must restart. If heartbeats are continuously sent, the session continues beyond 10 minutes. Partners must implement token refresh logic:At 9 minutes, restart the journey to obtain a new valid token.Event Structure :javascript window.addEventListener('MoMoWebViewEvent', (payload) => { const { event, msisdn } =payload.detail; if (event === 'START_JOURNEY') { // Access the security token const token = window.micrositeToken; // Yourinitialization code here startYourApplication(token, msisdn); } }); Heartbeat (Keep-Alive)Sending: IS_STILL_ACTIVEKeep the session alive and prevent automatic timeout/reload, every 50 secondsActual timeout is 60

440
D
A
Akem Dev StudiosNew Member
 MoMo Uganda Developers
D
DevYouNew Member
 MoMo Benin Developers
Terms & ConditionsCookie settingsAccessibility statement