Settlement Currencies

Settlement currencies list every currency currently enabled for settlement or payment conversion. Fields shown match the /currencies endpoint. Use the Code column when you build payment requests, quotes, and when you interpret settlement and reporting responses.

This table applies to:

• Payments created through the Payments APIs

• Settlement records in the Settlement APIs

• Reporting endpoints that expose currency codes and amounts

Currency table

Code	Name	Currency type	Tender type	Decimals	Enabled
USD	US Dollar	fiat	ethereum	2	✓
BTC	Bitcoin (Lightning)	crypto	bitcoin_Lightning	8	✓
USDC	USDC Ethereum	crypto	usdC_Ethereum	6	✓
USDC_NPL	USDC Polygon	crypto	usdC_Polygon	6	✓
ETH	Ethereum	crypto	ethereum	18	✓
BTC	Bitcoin (on-chain)	crypto	bitcoin	8	✓
CIT_USD_ALI	Alipay USD	walletApps	alipay	2	✓
CIT_USD_PPAL	PayPal USD	walletApps	paypal	2	✓
CUS_USD_VENMO	Venmo USD	walletApps	venmo	2	✓
CUS_USD_WECHAT	WeChat Pay USD	walletApps	weChatPay	2	✓
USD_KLARNA	Klarna USD	walletApps	klarna	2	✓

Column definitions

Code Identifier for the currency. Uses ISO 4217 for fiat or a platform specific symbol for crypto and wallet apps. This value appears in payment requests, settlement records, and reporting responses.

Name Human readable name for the currency and where relevant the network or platform. For example, USDC Ethereum or Bitcoin Lightning.

Currency type High level category for the currency. Values include fiat, crypto, and walletApps. This indicates whether the currency represents traditional money, a digital asset, or a wallet application balance.

Tender type Value used in tenderTypes arrays when limiting payment methods or interpreting how a payment will be routed. For crypto and wallet entries this typically maps to a specific network, Lightning configuration, or QR platform identifier.

Decimals Number of minor unit decimal places the platform accepts and returns for this currency. For example, USD has 2 decimals and Ethereum has 18.

Enabled Indicates whether the currency is currently live for both Sandbox and Production. Currencies marked with a check mark are fully enabled. If a currency is not enabled it may be present in schemas but blocked for use.

Notes

All crypto rows map to testnets in Sandbox environments. Production uses mainnet equivalents for the same codes.

New currencies follow the same schema and will appear in this table when they are enabled. If you see a currency code in an API response that is not listed here, contact the Bead team before relying on it in production.