Sandbox and production

Every merchant account has two fully isolated environments, each with its own wallet, API keys, webhooks, and shipment history. Nothing created in sandbox ever appears in production, or vice versa.

Sandbox

• Available immediately after signup, no approval required.
• Pre-funded with a ₦500,000 mock wallet balance so you can test shipment creation, cancellation, and webhook delivery without spending real money.
• Shipments created in sandbox are simulated: they move through the same status lifecycle as real shipments, but no agent is physically dispatched.
• Use SB_... keys.

Production

• Unlocked once your business verification is approved and you has been granted go-live access on your account.
• Your production wallet starts at ₦0. You must fund it before you can create a shipment, funding is done from the merchant dashboard via our payment gateway.
• Use PROD_... keys.

Why this matters for your integration

Because environment is resolved from the API key rather than the URL, you can point the exact same integration code at either environment simply by changing which key your backend loads (for example, from a SANDBOX vs LIVE environment variable). There is nothing else to reconfigure.

Wallet balance and shipment charges

Every shipment is charged against your wallet balance for the environment the request ran in, at the moment the shipment is created. If your balance is insufficient, shipment creation fails with an insufficient_funds error (HTTP 402) and no shipment is created. If a shipment is later cancelled before pickup, or fails and cannot be completed, the charge is automatically refunded to the same wallet.