← All Posts
Development

Sandbox Mode Explained: Test Your Integration Without Real Funds

May 10, 2026· 2 min read
Sandbox Mode Explained: Test Your Integration Without Real Funds

What Is Sandbox Mode?

Sandbox mode is a parallel configuration that uses BNB Testnet (chain 97) and a custom test token (sUSDT) instead of real USDT on mainnet. Your integration logic is identical — only the network changes.

The key difference: in sandbox mode, you can trigger a simulated deposit via API instead of waiting for a real blockchain transaction.

Enabling Sandbox Mode

In the admin panel, go to Network Config and switch the active mode to "Sandbox". The dashboard will show a yellow "SANDBOX" badge to remind you.

Triggering a Test Deposit

First, start a payment session to get a deposit address:

POST /api/v1/addresses/start-session
{ "userId": "test-user", "amount": 100 }

Then credit the deposit address using the sandbox API:

POST /api/sandbox/credit
{
  "toAddress": "0x...",
  "amount": "100",
  "userId": "test-user"
}

This fires your webhook immediately — no waiting for block confirmations.

What Gets Tested?

The sandbox exercises your full integration path:

  • Webhook delivery and signature verification
  • Your order fulfillment logic
  • Error handling (try sending wrong amounts, expired sessions)
  • Idempotency (send the same txHash twice — your system should handle it)

Limitations

Sandbox mode does not test actual BNB gas logic or sweep timing. For those, you need testnet integration testing with real BSC Testnet transactions.

Switching Back to Production

Change the mode back to "Production" in the Network Config page. API keys work in both modes — there's no separate set of keys to manage.

← Back to Blog
sandboxtestingdevelopmenttestnet