Payment API Sandbox to Production in Africa: What Changes on Paystack, Daraja and MTN MoMo

Picture the last demo before launch. Your sandbox payment goes green, the client claps, and the next morning you learn production needs documents you do not have. The sandbox was never the hard part.

This page compares the go-live step on each rail: who says yes, what you hand over and what behaves differently once the money is real. It is a companion to the African payment rails matrix, which holds the country rows.

Every fact below links to the provider's own page and carries the date we checked: 3 November 2026.

Rail	Sandbox	Who approves production	What you submit
Paystack (Kenya, Ghana, Nigeria, South Africa, Côte d'Ivoire)	Test mode, every new account	Paystack Business Reviews, automatic if documents verify	Compliance page by business type and country
M-Pesa Daraja (Kenya)	Sandbox app on the portal	Safaricom	Shown inside the portal; not readable to us
MTN MoMo	API Sandbox section, portal marked "Test environment"	MTN, per country	Country specific documents on the Go-Live page after login
Airtel Money	Not confirmed	Not confirmed	Not confirmed

Sources: Paystack guide to activating a business, Safaricom Developers Portal, MTN MoMo developer community, Airtel Africa developer portal, checked on 3 November 2026.

To practise the whole path from key to live callback, try the Payment Integration for Developers course.

New Paystack accounts start in test mode, "a safe sandbox environment where you can use Paystack without using real money" (Paystack guide to activating a business, checked on 3 November 2026). You confirm your legal business name, country and business type, then move to the Compliance page. When every section shows a green tick, you press "Activate Business". If documents verify, the business goes live automatically. If not, the Business Reviews team emails within 24 hours (Paystack guide to activating a business, checked on 3 November 2026).

The documents depend on the country and business type. A Kenyan Starter business needs a National ID or valid passport and a personal bank account or mobile money line, with names that match. A Kenyan limited company needs a certificate of incorporation, a CR-12, a KRA PIN and a business bank account (Paystack Kenya compliance, checked on 3 November 2026).

What changes once you are live:

• Webhook retries. Live mode sends events every 3 minutes for 4 tries, then hourly for 72 hours. Test mode sends hourly for 10 hours with a 30-second timeout (Paystack webhooks docs, checked on 3 November 2026).
• Keys. Test keys for development, live keys for production (Paystack API reference, checked on 3 November 2026). Keep them in separate environment variables so a test key never ships to production.
• Real phones. Mobile money test numbers need no PIN or OTP in test mode (Paystack test payments, checked on 3 November 2026). Live customers approve on a phone within 180 seconds.

The existing guide Paystack test mode working but live mode failing covers the debugging side.

The Safaricom portal says you can register as a company or an individual, then "create a sandbox app and test it by simulating the app on any external API Client" (Safaricom Developers Portal, checked on 3 November 2026). Many developers use Postman or curl for this.

The go-live path is the part we cannot quote from the official source. The portal renders its pages with scripts, so a plain fetch returns only the home text. We do not state the production documents or timings here. Our own written steps, from projects we have shipped, are in the Daraja production checklist; confirm each against the portal before you promise a client a date.

Two things we do tell clients from experience, without claiming they are official rules: callbacks need a public HTTPS URL that your server answers quickly, and a sandbox success tells you nothing about whether Safaricom has approved your shortcode.

MTN's community manager says the go-live documentation is country specific and is listed on the Go-Live page of the portal after you sign in (MTN MoMo developer community, checked on 3 November 2026). That means two developers in two countries can face different checklists on the same API.

The practical step is dull and useful. Sign up, open the Go-Live page, and save the document list with the date. Then start collecting those documents, such as company papers and director IDs, while you code, not after.

For Airtel Money, the developer portal returned only its title when we fetched it (Airtel Africa developer portal, checked on 3 November 2026). We cannot describe its sandbox or go-live path, so we do not. Check the portal in a browser.

For country by country detail on MoMo build steps, see our guides on MTN MoMo API in Uganda and testing MoMo payments in the sandbox. They are tutorials, not MTN confirmations.

1. List the documents your provider asks for in your country, and who holds each one in the client's company.
2. Store sandbox and live credentials separately, with different names.
3. Make your callback handler safe to run twice, because retries happen on every rail.
4. Reconcile one live payment by hand against the provider's dashboard or statement before launch day.
5. Write down the date you checked each rule. Rules move.

For a wider view of which rail fits which country, return to the rails matrix. To learn the full path yourself, the Payment Integration for Developers course is built for it. To have it built, see payments integration at Mctaba Labs. Also read Paystack mobile money provider codes by country, how to check a payment API in your country and Paystack Pesalink in Kenya.