Supported Chains

Overview

Daya supports a defined set of blockchain networks for stablecoin settlement. Supported chains differ between Sandbox and Production environments. Support is directional. A token can be enabled for deposits on a chain without being enabled for withdrawals on that same chain.

Need the same information programmatically? Use List Supported Chains.

Use the API endpoint for the authoritative live matrix of deposit and withdrawal support. Do not hard-code this table into your product.

Environment Support

Sandbox
Production

Sandbox is designed for testing and integration.
It supports a limited set of chains with test behavior that mirrors production.

Supported Assets

Chain	USDC Deposit	USDC Withdraw	USDT Deposit	USDT Withdraw
Ethereum	Yes	Yes	Yes	No

Ordinary sandbox USDT/USDC funding and withdrawals use Ethereum only. Bridge simulations use the separate list below.

For ordinary sandbox USDT/USDC funding and withdrawals, requests specifying other chains will fail. This restriction does not apply to bridge simulations.

Production supports multiple blockchain networks for real settlement.

Chain	USDC Deposit	USDC Withdraw	USDT Deposit	USDT Withdraw
Polygon	Yes	No	Yes	Yes
Ethereum	Yes	No	Yes	No
Base	Yes	Yes	Yes	No
Optimism	Yes	No	Yes	No
BNB Smart Chain	Yes	No	Yes	Yes
Solana	Yes	Yes	Yes	Yes
Sui	Yes	No	No	No
Tempo	No	No	Yes	No
Tron	No	No	Yes	No
Aptos	Yes	Yes	Yes	Yes

The production table is a snapshot. Your integration should still call /v1/supported-chains before showing chain options or submitting a request.

USDT onchain settlement for NGN onramps is supported on BNB Smart Chain (BSC) and Polygon when the token entry returns withdraw_enabled: true.

Temporary funding and bridge chains

Temporary crypto balance funding and bridging use narrower chain lists than the general table above.

Product	Asset	Production chains
Temporary crypto balance funding	`USDT`, `USDC`	`ETHEREUM`, `BSC`, `SOLANA`, `BASE`, `POLYGON`
Bridging	`USDT`	`POLYGON`, `BSC`, `SOLANA`, `APTOS`

For temporary funding, select a deposit-enabled asset and chain. For bridging, the source must support deposits and withdrawals, and the destination must support withdrawals. The two chains must differ. Sandbox temporary funding uses Ethereum. For bridge simulations, use the USDT bridge row above rather than the ordinary sandbox table returned by /v1/supported-chains. See temporary balance funding and Bridges.

Important Notes

Always ensure that:

The asset (USDC or USDT)
The chain
The destination address format

all match exactly.Funds sent to an unsupported chain or incorrect network might not be recoverable.

How Chains Are Used

Chains are specified when configuring ONCHAIN settlement for an NGN funding account, creating a crypto funding account address, or withdrawing merchant balance onchain. Use the endpoint flags this way:

Flag	Use it for
`deposit_enabled`	Crypto funding account receive addresses and crypto-to-NGN offramp deposits.
`withdraw_enabled`	ONCHAIN settlement for NGN funding accounts and merchant balance withdrawals to wallets.

Rules to keep in mind:

Chain selection is per funding account.
Different funding accounts may use different chains.
Merchant balance settlement does not require a chain until withdrawal.
A chain name appearing in an older guide, enum, or conversation does not mean it is available for every flow. For ordinary flows, the asset, chain, environment, and direction must all be enabled by /v1/supported-chains. Apply the product lists and sandbox bridge exception above as well.

See:

Adding New Chains

Support for additional networks may be added over time. If you require a chain not listed here, contact support@daya.co.

Next Steps

Funding Accounts

Learn how on-chain settlement works

Create Funding Account API

Configure settlement via the API