The verdict in three sentences
The sandbox is not a formality: it is where you deliberately trigger failures before your customers ever hit them. A serious QA pass takes 3 to 5 days and covers the six most common error paths: insufficient funds, timeout, cancellation, double submission, expired token and lost callback. Going live without them always costs you paid-but-unfulfilled orders and disputes.
Test scenarios and expected results
Every provider offers numbers and amounts that trigger specific behaviour. Always test the happy path AND the failures.
| Scenario | How to trigger it | Expected result |
|---|---|---|
| Successful payment | Valid test card / MSISDN | Order confirmed via callback |
| Insufficient funds | Trigger amount / number | Declined, cart kept |
| Timeout | Do not approve prompt | Pending status, then poll |
| Customer cancels | Voluntary decline | Cart released |
| Double payment | Replay same tx_ref | Single order (idempotency) |
| Lost callback | Block the callback URL | Recovered via reconciliation |
12-point go-live checklist
Before switching keys to production, validate every line. A single missing item is enough to cause incidents.
| # | Control point | Expected status |
|---|---|---|
| 1 | Production keys distinct from sandbox | Verified |
| 2 | Public HTTPS callback URL | Verified |
| 3 | Webhook signature verified | Verified |
| 4 | Idempotency on tx_ref / order id | Verified |
| 5 | Polling reconciliation enabled | Verified |
| 6 | All six error codes handled | Verified |
| 7 | Timeout handled (pending status) | Verified |
| 8 | Min/max amounts enforced | Verified |
| 9 | Clear error messages for the customer | Verified |
| 10 | Transaction logging in place | Verified |
| 11 | One real low-value payment tested | Verified |
| 12 | Refund procedure tested | Verified |
Mini case study
Grace launches a fabric store in Nairobi. Tempted to skip QA to save time, she instead simulates failures for 4 days. She finds that 1 order in 20 timed out on the prompt without recovery: on 300 orders a month at KES 2,500, that is about 15 orders (KES 37,500) lost or mishandled every month. The 4-day QA pass saves her thousands in disputes and a damaged reputation at launch.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
FAQ
How long should sandbox QA take?
Plan 3 to 5 days to cover the happy path and the main failures. It is a tiny investment against the cost of production incidents.
Which tests are most often skipped?
Timeout, double payment and lost callback. These are precisely the ones that cause paid-but-unfulfilled orders.
How do I simulate a payment failure in sandbox?
Providers offer test cards, MSISDNs or trigger amounts that force declines, insufficient funds or timeouts. Use them to validate your error messages.
Should I really test a real payment before launch?
Yes, one low-value real payment (for example 100 FCFA equivalent) validates the whole chain in live conditions, including settlement. It is point 11 of the checklist.
Let's talk about your project. We run your full sandbox QA and go-live so payments launch without surprises. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.