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

# Account structure

> Understand the account hierarchy, roles, and sub-account model in Digital Asset Accounts

The Digital Asset Accounts hierarchy organizes funds across programs, accounts,
and sub-accounts. This structure enables regulatory segregation, per-entity
compliance tracking, and clear fund ownership under the
[Direct End-User Custody model](/digital-asset-accounts/concepts/custody-model).

## Roles

Digital Asset Accounts defines two primary roles:

| Role             | Description                                                                                                                                                                                        |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Distributor**  | A fintech, platform, or marketplace that integrates with the Digital Asset Accounts API to offer stablecoin-backed account services to their customers. Distributors do not hold custody of funds. |
| **End customer** | A business entity onboarded through the distributor. Each end customer is verified by Circle through KYB (Know Your Business) and receives a dedicated account.                                    |

## Account hierarchy

Digital Asset Accounts organizes funds across three levels:

* **Program**: The top-level container for a distributor's integration. When
  Circle provisions your API access, your credentials are scoped to a specific
  program, and all accounts and transactions in your integration belong to that
  program.
* **Account**: Each onboarded business entity receives an account under your
  program. The account is the primary identity for the end customer in Digital
  Asset Accounts. Circle performs KYB verification before activating an account,
  and each account receives a risk tier that determines its
  [transaction limits](/digital-asset-accounts/concepts/limits-and-risk-ratings).
* **Sub-account**: Each account contains one or more sub-accounts. Each
  sub-account holds a balance in a specific currency (for example, USDC or EURC)
  and is created automatically when an account is provisioned.

Sub-accounts serve as the unit for:

* **Balance tracking**: Each sub-account maintains its own balance in a single
  currency.
* **Transaction history**: Deposits,
  [wire withdrawals](/digital-asset-accounts/howtos/wire-deposits-and-withdrawals),
  and transfers are recorded against specific sub-accounts.
* **Internal transfers**: Funds move between sub-accounts in the same program
  instantly and at no cost.

## Onboarding flow

End-customer onboarding involves three stages:

1. **Business information submission**: The distributor submits the business
   entity's information using the
   [End User Onboarding API](/end-user-onboarding). The API provides a JSON
   Schema that defines required fields, supports bulk data submission, and
   handles document uploads. Required details include the business name,
   registration, and beneficial owners.
2. **KYB verification**: Circle reviews the submitted information and performs
   compliance checks. If the compliance team needs additional data, the
   application moves to `PENDING_CUSTOMER_INFORMATION` and the distributor can
   respond through the API. See
   [Handle requests for information](/end-user-onboarding/howtos/handle-rfis)
   for details.
3. **Account activation**: After KYB is approved, Circle activates the account
   and provisions sub-accounts for the supported currencies. The account is then
   ready to receive deposits and perform transactions.

## API key scoping

Your API key is scoped to your program, which means:

* You can only access accounts and transactions in your own program
* All API operations are automatically restricted to your program's scope
* You cannot access accounts belonging to other distributors

This scoping ensures data isolation between distributors while allowing full
visibility into your own end customers' accounts and transactions.