Crypto

Use the tender-type strings in this table when you want to enable or restrict specific crypto rails at the terminal, location, or payment level. In Sandbox, all assets settle on public testnets; Production uses the mainnet equivalents.

Tender type	Display name	Blockchain / Layer	Currency code	Decimals	Sandbox network	Confirmations *
bitcoin	Bitcoin (on-chain)	Layer-1	BTC	8	Testnet	4
bitcoin_Lightning	Bitcoin Lightning	Lightning Network	BTC	8	Testnet (Regtest/Signet)	0
ethereum	Ethereum	Layer-1	ETH	18	Sepolia	1
usdC_Ethereum	USDC (Ethereum)	ERC-20	USDC	6	Sepolia	1
usdC_Polygon	USDC (Polygon)	ERC-20	USDC	6	Amoy	100

* Number of block confirmations required before funds are considered final in Production; Sandbox may accept 0-confirm test transactions for speed.

Key points

• Decimals – send amounts in the asset’s minor units (wei, satoshi, etc.).

• Payment windows – each tender type enforces its own payment and confirmation timeouts; see the /currencies endpoint for real-time values.

• Testnet to mainnet migration – switch only the network and node URLs; tender-type strings stay the same.

• Adding new assets – when Bead enables another crypto or layer, it will appear here and in the /currencies list.