Custodial Wallets require a business account. If you’re interested in using this product, get in touch and our team will follow up to discuss fit.
How accounts fit your integration
Typical flows build on three ideas:- Create and name accounts to segment funds (for example per merchant, product line, or settlement bucket).
- Receive value using deposit destinations. Crypto deposit addresses are the supported path for inbound funds today. Fiat deposit destinations are in active development.
- Move value using transfers between accounts, to external onchain addresses, to linked Coinbase balances where supported, or through other supported rails.
Account ownership models
For how customer identity and verification relate to future customer accounts, see Customers & KYC.
Supported assets and networks
Supported assets, networks, and settlement behavior depend on your entity configuration and environment. Use Supported networks and assets as the source of truth for what you can hold and move in each environment.Core API operations
Authentication follows the same CDP API key and JWT model as the rest of the platform. See Authentication and Idempotency for request signing and safe retries.
What to read next
Custodial wallets quickstart
Create an account in Sandbox and confirm balances with the API
Accounts API reference
OpenAPI-backed reference for account and balance endpoints
Sandbox: Accounts guide
Portal funding and curl examples for Sandbox accounts
Payments overview
How payment acceptance, transfers, and deposit destinations relate to accounts