Sandbox Environment
The sandbox environment lets you test your entire integration without moving real money.
Environment Model
Ikawaari uses explicit environment separation between sandbox and live.
In addition to test API keys, merchant tooling also includes environment-aware behavior and test-mode operations for synchronizing and validating merchant configuration safely.
How to Use Sandbox
- Use API keys with the
ik_test_prefix - Use the implemented route family required by your integration
- No real transactions are processed
- Data is isolated from your live environment
Sandbox vs Live
| Feature | Sandbox | Live |
|---|---|---|
| API Key prefix | ik_test_ | ik_live_ |
| Real money | ❌ No | ✅ Yes |
| Provider connections | Simulated | Real |
| Webhooks | ✅ Sent | ✅ Sent |
| Dashboard data | Separate | Separate |
Switching Environments
In the dashboard, use the environment toggle in the top navigation bar to switch between sandbox and live views.
Merchant Test Mode
Ikawaari also includes merchant test-mode behavior for controlled sandbox operations.
Current test-mode actions include:
activatedeactivateresync
These flows are important because some merchant configuration can be synchronized into sandbox for testing and validation.
Recommended Sandbox Scenarios
- Create and inspect a payment intent
- Validate webhook signature handling
- Simulate mobile money success, failure, and timeout cases
- Test replay-safe request behavior with idempotency keys
- Validate payout and merchant notification handling
Implementation Notes
- Checkout and merchant APIs may use different route families.
- Dashboard environment switching and test mode are part of the implemented platform behavior.
- Documentation should treat sandbox as an environment model, not only as a list of fake credentials.
Sandbox Limitations
- Mobile money USSD prompts are simulated (no real phone notification)
- Bank transfers complete instantly (no real bank processing)
- Card 3D Secure flows use test pages