For the complete documentation index, see llms.txt. This page is also available as Markdown.

🧪Sandbox

Sandbox (Test Environment)

Inqud provides a Sandbox — a fully isolated test environment that mirrors production, so you can build and verify your integration without moving real funds. Everything you do in Sandbox (payments, payouts, webhooks, balances) is test-only and never touches the live platform.

Use Sandbox to:

  • develop and debug your integration end-to-end before going live;

  • test deposits, payouts and webhook delivery on real (test) blockchains;

  • demo the product without financial risk.

Sandbox is completely separate from production: separate URLs, separate accounts, separate API tokens, and separate balances. Production credentials do not work in Sandbox and vice versa.

Request rate at sandbox env is limited: 10 RPM for POST requests, 300 RPM for GET requests. You can ask support to increase it.

URLs

Every production URL has a Sandbox twin at the same path under the *.sandbox.inqud.com domain — just swap the host. For example:

Production
Sandbox

API base URL

https://api.inqud.com

https://api.sandbox.inqud.com

Merchant dashboard

https://app.inqud.com

https://app.sandbox.inqud.com

The same rule applies to every other product surface (hosted payment page, on-ramp, recurring, etc.): take the production host and add the sandbox sub-domain.

Authentication works exactly like production — every request is signed with your Sandbox API token pair:

X-Token-API-Id:     {your-sandbox-token-id}     # starts with TKN-
X-Token-API-Secret: {your-sandbox-token-secret}

The request/response formats, webhook payloads and signature verification are identical to production — only the base URL and the credentials differ. This means your integration code can switch between environments by changing the base URL and the token pair, nothing else.

Getting access

  1. Sign up for a Sandbox account. Register at https://app.sandbox.inqud.com. Sandbox has no KYB requirement — you can start building right away.

  2. Generate Sandbox API tokens. In the Sandbox dashboard, open the API tokens section and generate a token pair (X-Token-API-Id / X-Token-API-Secret). These are valid in Sandbox only.

  3. Point your integration at Sandbox. Set the API base URL to https://api.sandbox.inqud.com and use your Sandbox tokens. Follow the same integration guide as production.

The API reference includes a server selector — choose api.sandbox.inqud.com to try requests against Sandbox directly from the docs.

Supported networks & currencies

Sandbox runs on public EVM testnets (no mainnet). Test funds have no real value and can be obtained for free from public faucets.

Pay-ins (Deposits)

Deposits are available on the following EVM testnets:

Network
Chain ID
Native faucet (third-party)

Ethereum Sepolia

11155111

https://sepoliafaucet.com

BNB Smart Chain Testnet

97

https://testnet.bnbchain.org/faucet-smart

Polygon Amoy

80002

https://faucet.polygon.technology

Arbitrum Sepolia

421614

https://www.alchemy.com/faucets/arbitrum-sepolia

Optimism Sepolia

11155420

https://app.optimism.io/faucet

Base Sepolia

84532

https://www.alchemy.com/faucets/base-sepolia

Payouts (Withdrawals)

Payouts in Sandbox are available for USDT and USDC on the EVM testnets above. These are Inqud test tokens (no real value).

Getting test USDT / USDC

The USDT and USDC used in Sandbox are Inqud-issued test tokens. To top up your Sandbox balance with test USDT/USDC, request a credit from your Inqud account manager or via support — we'll credit the test tokens to your Sandbox balance so you can run payouts. (Native testnet coins for gas come from the public faucets above; test USDT/USDC come from us.)

Going live

When your integration works in Sandbox, switch to production:

  1. Change the API base URL from https://api.sandbox.inqud.com to https://api.inqud.com.

  2. Replace your Sandbox API tokens with production tokens generated in https://app.inqud.com (production requires a completed KYB).

  3. Use real networks and currencies.

No other code changes are required — the API contract is identical.

Last updated