Notes

• Supported countries and operators vary by market. Use the Mobile Money Operators guide to choose the correct momoOperatorId.
• Ensure the phoneNumber includes the country code (e.g., 254 for Kenya).
• The externalReference must be unique for each transaction.
• Some operators require a customer-generated OTP before you initiate the charge. Follow the operator-specific customer instructions for the market you are collecting in and pass the generated code as otpCode.
• For redirect-capable mobile money rails, such as Senegal Wave (XOF), you can pass successRedirectUrl and failureRedirectUrl to control where the provider returns the customer after authorization.
• Some providers return a USSD step after charge initiation. When a pending transaction reports stepRequired: "ussd", display stepMetadata.ussdCode and the supplied description. Optional stepMetadata.expiry is a Unix timestamp in milliseconds. The customer completes the action on their phone; no OTP validation or USSD confirmation request is required. See Handle USSD Codes.
• A redirect return or completing a USSD phone flow does not confirm payment. Confirm the final status through webhooks or the get transaction endpoint.
• Keep your publicKey secure and do not share it publicly.