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 requirements that could block SMS?
- Do production accounts need special SMS permissions enabled?
What I've Already Verified:
- Phone number format matches ITU-T E.164 standard (225545xxxxxx for CI)
- Using correct country-specific target environment
- Amount and currency are within valid ranges
- All required headers are present
- Customer phone number is active MTN MoMo account
Additional Context: The same setup works in sandbox (though sandbox doesn't send real SMS), and the API documentation doesn't mention any special SMS-specific parameters beyond the standard requesttopay payload.
Has anyone encountered this issue? What additional parameters or configurations are needed to ensure SMS notifications are sent to customers?
Any guidance would be greatly appreciated! 