Testing and going live
Nodal has one environment: https://api.tfolanodal.com. Every collection, mandate debit, payout and refund moves real money through your MTN MoMo merchant wallet. This page shows how to test your integration safely anyway.
No test mode yet
There are no test keys or test phone numbers. A separate test environment is planned; until then, test with small real payments as described below.
Test with small amounts on your own number
- Pay with your own MTN MoMo number, or a colleague's, so the money stays with you. Use amounts like E1.00.
- Refund each test payment from the portal (Once-Off Collections → the payment → refund). MTN charges a fee on refunds and payouts (1% of the amount), so a E1.00 test costs about one cent.
- Test payments count as successful collections on your monthly Nodal bill, like any other payment. At E1.00 they are worth keeping few.
- Give test orders an obvious
reference, likeTEST Order 1042, so they are easy to find in reports and exports.
What to test before going live
A successful payment
Pay, then check your server only marks the order paid after confirming it with
GET /checkout/sessions/:idor a verified webhook — never because the customer reached your success page.A declined payment
Start a payment and reject the prompt on your phone (or let it time out). The checkout page tells the customer nothing was taken and lets them try again; a direct collection ends
FAILED. Your order must stay unpaid.A customer who never comes back
Pay, then close the browser before you are sent back. Your
checkout.session.completedwebhook should still mark the order paid.Retries
Send the same create request twice with the same
Idempotency-Key. You must get the same session or collection back, and only one payment prompt.Webhook signatures
Use Send test on your endpoint in Integrations, then change one character of the secret on your server and check that the request is rejected.
Going live checklist
- Your MTN MoMo collection keys are saved in Settings (and disbursement keys, if you pay out or refund).
- Your API key lives in your server's environment, and nowhere else.
- Every create request sends an
Idempotency-Keyderived from your own order or payment id. - Orders are fulfilled only after server-side confirmation.
- Your webhook endpoint verifies signatures, ignores events it has already processed and answers within 10 seconds.
- Someone on your team can approve payouts and refunds in the portal — the person who requested one can't approve it.