The verdict in three sentences
80 % of payment bugs are found in sandbox — provided you test the right scenarios, not just the happy path. A matrix of 12 critical cases covers success, failure, timeout, cancellation, insufficient balance and double submission per operator. In 2026, a 2 to 3-day test plan avoids a rollback whose cost far exceeds that of testing.
The 12 critical scenarios
The classic trap: testing only the payment that succeeds. Incidents are born on error paths, the ones you never see in a demo. Here are the cases to cover systematically.
| Scenario | Expected result | Trap if untested |
|---|---|---|
| Successful payment | Order paid | — |
| Insufficient balance | Clean failure + retry | Order stuck |
| USSD timeout | Session cancelled | Stock locked |
| Customer cancellation | Return to cart | Eternal fake pending |
| Double submission | Idempotency | Double-debit |
| Late webhook | Late reconciliation | Inconsistent status |
| Duplicated webhook | Ignored (idempotent) | Double delivery |
| Invalid signature | 401 rejection | Fake payment accepted |
| Wrong amount | Reject + alert | Under-collection |
| Network drop mid-flow | Resume on reference | Orphan payment |
| Currency / format | Validation | Calculation error |
| Order rollback | Clean refund | Customer dispute |
Figures and per-operator matrix 2026
These 2026 markers (estimates) help size testing and justify the budget.
| Indicator | 2026 value | Note |
|---|---|---|
| Critical scenarios | 12 | Minimum per integration |
| Test plan duration | 2 to 3 days | Full QA |
| Incident rate without tests | 20 to 30 % of tx | Post-launch |
| Average rollback cost | 300,000 to 1,000,000 FCFA | Fix + reputation |
| Operators to matrix | 2 to 4 | Paystack, MoMo, M-Pesa, etc. |
| Sandbox accounts | Free | Per operator |
Multiply the 12 scenarios by the number of operators: a Paystack + MoMo + M-Pesa integration means 36 test cases, all runnable in free sandbox before a single real franc is collected.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Mini case study
Moussa launches an online grocery in Thika with two rails. Tempted to skip QA to save 3 days, he first simulates the 12 scenarios per operator. He discovers in sandbox that customer cancellation left the order in eternal pending, locking stock. Fixed before production, that single bug would have cost an estimated 500,000 FCFA rollback in launch week. The 2.5 test-days (~250,000 FCFA) pay for themselves many times over.
FAQ
How many scenarios should I test at minimum? At least 12 critical cases per operator: success, failure, timeout, cancellation, insufficient balance, double submission, duplicated webhook, invalid signature, and more.
How long should QA take? Budget 2 to 3 days for a one or two-operator integration, more if you stack three or four.
Does the sandbox cost anything? No, the Paystack, MTN MoMo and M-Pesa sandboxes are free and simulate both successes and failures.
What is the risk of skipping tests? Between 20 and 30 % of transactions can generate a post-launch incident, with a rollback costing 300,000 to 1,000,000 FCFA.
Must I retest each added operator? Yes, each operator has its own error codes and timeouts. The matrix is re-run in full for every rail added.
Let's talk about your project. We build your multi-operator sandbox test matrix before any go-live. 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.
