Custodial Wallets

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.

Custodial Wallets hold balances in one or more assets (for example USD, USDC, or other supported crypto) and act as the source or target for deposits, transfers, and payouts you orchestrate from your backend. Coinbase provides custody for assets in these accounts on behalf of your CDP entity. You can create entity-owned accounts for treasury, settlement, and operational balances, and customer-owned accounts for balances attributed to your KYC-verified end users via Customers & KYC.

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

Model	Who owns the balance	Typical use
Entity account	Your CDP organization	Company treasury, settlement pools, operational hot balances
Customer account	Your end customer under an approved program	Per-user balances, payouts, and disclosures where you need customer-level ledgering

To create a customer-owned account, pass the customer ID as owner on POST /v2/accounts. The customer must hold all three custody capabilities (custodyCrypto, custodyFiat, and custodyStablecoin). See the Customers quickstart for an end-to-end example.

Supported assets and networks

Your entity configuration and environment determine which assets, networks, and settlement behavior are available. Verify your account setup before moving funds.

Core API operations

Operation	What it does
Create account	`POST /v2/accounts` — provision a new account (optional display `name`, optional idempotency header)
Get account	`GET /v2/accounts/{accountId}` — metadata such as type, owner, and timestamps
List accounts	`GET /v2/accounts` — paginated accounts for your entity
List balances	`GET /v2/accounts/{accountId}/balances` — balances per asset
Get balance for asset	`GET /v2/accounts/{accountId}/balances/{asset}` — single-asset balance detail

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.