Sandbox

The sandbox is a full test environment — build and test your integration (API keys, webhooks, subscriptions, payments) without touching live data or moving real money.

Base URL

Point your integration at the sandbox host (same /api/v1/ paths as live):

https://test-be.suqo.ai

Getting a sandbox API key

There is no separate sandbox signup. You use your normal SUQO account and switch it into Test mode; the sandbox data — including API keys and webhooks — lives behind that switch.

1. Sign in to the dashboard as usual.
2. Flip the Live / Test switch in the sidebar to Test Mode. See Test mode.
3. Go to Configuration → API integration and create a key. A key created in Test mode is a sandbox key, and only works against the sandbox host below.
4. Add webhooks the same way — they are environment-scoped too (see Authentication).

Your sign-in, business profile, account settings and KYC are the account itself and are always live. Everything else — products, customers, transactions, API keys, webhooks — is separate per environment.

SMS and email

Checkout OTPs are stubbed. A buyer verifying their phone during a sandbox checkout receives no SMS, so a fixed code stands in for the real one:

123456

Sign-in and signup OTPs are not. Authentication is part of the account, which is always live (see above) — so a code sent while you register or sign in is a real SMS to a real phone, and 123456 will not work there. Only checkout is stubbed.

Email is not sandboxed at all. Emails are delivered for real, to whatever address is submitted, in the sandbox exactly as in live. Use addresses you own, and never put a real customer's address into a test checkout.

Payments

SUQO Pay is the only payment method in the sandbox. eSewa, Khalti, ConnectIPS and NPS are live-only; a sandbox checkout offers SUQO Pay's UAT gateway and nothing else, so there is nothing to configure. It is a test-only rail, standing in while the production integration is pending.

No real money moves. It returns a payment_url and behaves like Khalti from there on, so the checkout_url handling and the webhooks you will use in live can both be verified end-to-end against it.