> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cdp.coinbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Custodial Wallets

> Programmatic accounts for custody, balances, and money movement on CDP.

<Note>
  Custodial Wallets require a business account. If you're interested in using this product, [get in touch](https://www.coinbase.com/developer-platform/developer-interest) and our team will follow up to discuss fit.
</Note>

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. In current milestones, the focus is **entity-owned accounts** for treasury, settlement, and operational balances. Support for **customer-owned** accounts (balances attributed to your KYC-verified end users) is rolling out in line with the broader payments roadmap.

## How accounts fit your integration

Typical flows build on three ideas:

1. **Create and name accounts** to segment funds (for example per merchant, product line, or settlement bucket).
2. **Receive value** using [deposit destinations](/payments/deposit-destinations/overview). **Crypto** deposit addresses are the supported path for inbound funds today. **Fiat** deposit destinations are in active development.
3. **Move value** using [transfers](/payments/transfers/overview) 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 (coming soon) | Your end customer under an approved program | Per-user balances, payouts, and disclosures where you need customer-level ledgering |

For how customer identity and verification relate to future customer accounts, see [Customers & KYC](/customers-kyc/overview).

## Supported assets and networks

Supported assets, networks, and settlement behavior depend on your entity configuration and environment. Use [Supported networks and assets](/get-started/supported-networks#payments-apis-network-support) as the source of truth for what you can hold and move in each environment.

## Core API operations

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

Authentication follows the same CDP API key and JWT model as the rest of the platform. See [Authentication](/api-reference/v2/authentication) and [Idempotency](/api-reference/v2/idempotency) for request signing and safe retries.

## What to read next

<CardGroup cols={2}>
  <Card title="Custodial wallets quickstart" icon="rocket" href="/wallets/custodial-wallets/quickstart">
    Create an account in Sandbox and confirm balances with the API
  </Card>

  <Card title="Accounts API reference" icon="code" href="/api-reference/v2/rest-api/accounts/accounts">
    OpenAPI-backed reference for account and balance endpoints
  </Card>

  <Card title="Sandbox: Accounts guide" icon="flask" href="/get-started/sandbox/guides/accounts">
    Portal funding and curl examples for Sandbox accounts
  </Card>

  <Card title="Payments overview" icon="credit-card" href="/payments/overview">
    How payment acceptance, transfers, and deposit destinations relate to accounts
  </Card>
</CardGroup>