Who is it for?
SandPay is built for teams integrating Mobile Money in Africa who want to exercise the critical path (success, invalid PIN, insufficient funds, timeouts, operator maintenance…) safely. Instead of juggling four developer portals, four authentication formats, and four distinct error schemas, your applications talk toapi.sandpay.dev and SandPay translates internally.
Why a unified sandbox?
Every operator has its own portal, its own OAuth formats, its own native error codes (PIN_INVALID on MTN, INSUFFICIENT_FUNDS on Orange…). SandPay normalises all of that into 11 canonical statuses (SUCCESS, PIN_INVALID, INSUFFICIENT_FUNDS, TIMEOUT, …) and 10 reproducible scenarios you trigger with a single scenario field in the request.
Ready to get started?
Quickstart
First simulated payment in 10 minutes — Stack Builder (starter zip) or manual integration.
API Reference
Endpoints, schemas, error codes — the full spec.