Bitcoin and UTXO payments
When enabled, Bitcoin and other UTXO assets retain their own network, confirmation, and address rules within the common payment flow.
Live payment asset discovery
Supported cryptocurrencies and networks
Discover the mainnet assets currently enabled for CryptPays payments. Live Merchant API metadata keeps network identity, canonical tickers, and exact minimum deposits current.
Network-aware processing
Clear network identity at checkout
CryptPays uses one Merchant API across distinct networks while preserving the asset, network, confirmation, and finality rules that matter to a payment.
Ethereum-compatible networks
Ethereum, BNB Smart Chain, Polygon, Base, and Avalanche assets appear as separate merchant-recognizable networks when currently enabled.
Solana and stablecoins
Enabled Solana and SPL assets use Solana finality. Stablecoins such as USDT or USDC remain clearly associated with their specific network.
TRON and TRC-20
TRON capability can include native TRX and tokens such as USDT when they are returned by the current live catalog.
Runtime authority
Current enabled assets
The catalog is loaded once from the public Merchant API and grouped using authoritative network metadata. Search locally or filter by a network to compare current minimums and confirmation requirements.
Loading current enabled assets…
Live catalog unavailable
Live asset data is temporarily unavailable.
No supported assets are currently available.
Minimums are current runtime processing thresholds and may change with network conditions or operator safety floors. Check live metadata when presenting payment instructions.
Integration-safe discovery
Treat asset metadata as changing operational data
Build checkout choices from current metadata rather than copying a catalog or minimum into application code.
Use the canonical ticker
Use the ticker value when calling CryptPays Merchant API create, info, and logs endpoints. Store it alongside each payment.
Read the current minimum
Minimum values are decimal strings and can change with network economics. Keep their exact precision and check current metadata before creating payment UI.
Expect runtime enablement
An integration should only offer assets returned by the live catalog. A familiar network name alone does not establish current availability.
Next step
Connect current asset data to your checkout
Use the developer documentation for payment creation and signed callback handling, or review how transaction accounting is reported.