KODA's free developer sandbox and telco simulator let you test every outcome — verified, late, replay, reversal, even fraud — with magic references and no real money.
— reads
Before a developer trusts verification in production, they need to see how it behaves in every situation — not just the happy path. KODA's developer sandbox exists for exactly that: a free, unlimited test environment where you can rehearse every possible outcome of a mobile money verification without sending a single franc of real money. It never expires, so you can build, test and regression-check against it for as long as your integration lives. The developer reference is on KODA API for developers.
The sandbox works through magic references — special codes that force a known result. Submit TEST-OK and the verification returns verified; TEST-LATE simulates a confirmation that arrives after a delay; TEST-REPLAY shows what happens when a code is reused; TEST-SUFFIX exercises partial-match handling; and TEST-REVERSAL plays out an operator reversing a payment after the fact. Each one lets you write and prove the handling for a specific case deterministically, so your code is ready for it before a real customer ever triggers it.
For deeper testing there is a telco simulator. A call to the sandbox SMS endpoint lets you inject a fabricated operator confirmation message — as if a payment had just hit the merchant's phone — and watch the engine parse, match, score and lock it exactly as it would in the field. This is how you test the full inbound path end to end, including the webhook that fires on a verified payment, without touching a real operator or a real wallet. The webhook contract itself is in Get a Webhook the Moment a Payment Is Verified.
The quiet value of this is that you can rehearse fraud safely. You can fire a replay, feed a malformed or forged-looking message, or simulate a reversal, and confirm that your system does the right thing — holds the goods, flags the order, alerts a human — all in an environment where nothing is at stake. Most teams discover their fraud handling is wrong the first time it matters, in production, with a real loss; the sandbox lets you discover it beforehand, for free.
Because the sandbox is unlimited and permanent, it fits naturally into continuous testing. The same magic references can drive your automated test suite, so every change to your checkout or your order logic is re-checked against verified, late, replayed and reversed outcomes before it ships. An AI agent or autonomous checkout, of the kind described in Mobile Money Payment Verification for AI Agents, can be exercised against the full range of verdicts long before it handles live money.
It is honest to note what the sandbox is: a faithful simulation of the verification engine's behaviour, not a connection to real operators. Its results are designed to match production's logic precisely, but a magic reference is a scripted outcome, not a real payment. When you move to live keys, the same code runs unchanged against real confirmation messages — the sandbox's job is simply to let you arrive at that moment already certain of how your integration behaves. The move from test to live is covered on KODA API for developers.
If you are building anything that acts on a payment — a checkout, a bot, a platform — test it against every outcome first. Explore the magic references and the telco simulator on KODA API for developers, see how the core calls work in The Mobile Money Verification API (3 Endpoints, No Telco Deal), and Get started with KODA free to pick up a sandbox key. Ship knowing exactly what your code does when a payment is late, replayed or reversed — not hoping.
Every outcome of a verification: verified, late, replayed, partial-match and reversed, using magic references like TEST-OK, TEST-LATE, TEST-REPLAY, TEST-SUFFIX and TEST-REVERSAL. It is free, unlimited and never expires. Start on KODA API for developers.
No. The developer sandbox is free, unlimited and permanent, so you can build, run automated tests and regression-check your integration against it for as long as you need. Pick up a key on Get started with KODA free.
Yes. The telco simulator lets you inject a fabricated operator confirmation through the sandbox SMS endpoint, and the engine parses, matches, scores and locks it just as in production — including firing the verified webhook described in Get a Webhook the Moment a Payment Is Verified.
Yes, and you should. You can fire replays, forged-looking messages and reversals and confirm your system responds correctly — holding goods, flagging orders — with nothing at stake, before any of it can happen with real money.
Yes. The sandbox mirrors the engine's real logic, so the same integration runs unchanged against live confirmation messages when you switch to production keys. Moving from test to live is covered on KODA API for developers.