Receiving Stablecoin Deposits

Once you've issued a deposit address, Bitnob monitors it on-chain for incoming stablecoin transfers. When a transfer is detected and passes the required number of confirmations, we emit a webhook (deposit.success) and credit the associated wallet balance in your account.

Testing on Sandbox

To receive stablecoins on sandbox, use Circle's testnet faucet to fund your deposit address: https://faucet.circle.com/.

How It Works

Confirmation Requirements

Each blockchain requires a different number of confirmations before a deposit is considered final and credited to your wallet. The exact counts are enforced internally by Bitnob for safety.

Supported Stablecoin Networks

To retrieve all supported stablecoin networks and their chain codes, use the following endpoint:

GET /api/stablecoins/supported-chains Returns all available chain codes for USDT and USDC.

Sandbox-supported chains

chain	stablecoins
avalanche	USDT, USDC
base	USDC
bitcoin	—
ethereum	USDT, USDC
optimism	USDT, USDC
polygon	USDT, USDC
solana	USDT, USDC
stellar	USDC

Production-supported chains

chain	stablecoins
arbitrum	USDT, USDC
avalanche	USDT, USDC
base	USDC
bitcoin	—
bsc	USDT, USDC
ethereum	USDT, USDC
optimism	USDT, USDC
plasma	USDT
polygon	USDT, USDC
solana	USDT, USDC
stellar	USDC
tron	USDT

Chains available only in production: arbitrum, bsc, plasma, tron.

Get Supported Networks Request

Response

Get Supported Networks Response

Deposit Webhook

When a deposit is detected and confirmed on-chain, Bitnob sends a deposit.success webhook to your configured endpoint. Use this event to credit user balances or trigger downstream workflows.

Example: deposit.success Webhook Payload

deposit.success Payload

For more webhook details, see the Stablecoin Webhooks reference.

Use Case: Dynamic Chain Support

You may want to display supported stablecoin networks to your end-users (e.g. "Send USDT via Tron, Ethereum or Solana") or let them choose the cheapest or fastest one.

Use this endpoint to:

Dynamically render a network selector in your frontend

Validate that your backend supports a specific chain-code before issuing an address

Optimize for low-fee networks based on real-time fee data