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

# Managed Accounts

> Create and operate verified stablecoin accounts for your customers. Choose custodial accounts for Brale-managed wallet addresses and balances, or transactional accounts for approved self-custody destination flows.

## Create stablecoin accounts for your customers

Managed accounts let your platform create and operate verified accounts for your end customers through Brale.

Each managed account has its own `account_id`. Choose the account model that matches the customer experience you are building:

* **Custodial accounts** include Brale-managed internal wallet addresses on supported chains and can hold stablecoin balances.
* **Transactional accounts** are non-custodial. They use external destination addresses and do not hold Brale-custodied balances.

Your platform owns the customer experience and uses the API to create accounts, check status, retrieve addresses and balances where applicable, and initiate supported activity. Brale operates the applicable account, custody, verification, and compliance infrastructure.

<Columns cols={2}>
  <Card title="Build with Custodial Accounts" icon="vault" href="/guides/custodial-accounts">
    Give verified customers Brale-managed wallet addresses and stablecoin balances.
  </Card>

  <Card title="Build with Transactional Accounts" icon="arrow-right-to-bracket" href="/guides/transactional-accounts">
    Support verified customers with self-custody destination flows, without a Brale-held balance.
  </Card>
</Columns>

## Why use managed accounts?

* **Give each customer an account structure.** Associate onboarding, addresses, balances, transfers, and events with one account ID.
* **Avoid building wallet infrastructure.** Custodial accounts receive Brale-managed internal wallet addresses on supported chains.
* **Embed stablecoin movement in your product.** Use the API to support account onboarding, balance visibility where applicable, and supported transfers or payouts.

## Choose an account model

| Customer need | Recommended model | What it provides |
| - | - | - |
| A verified business needs a Brale-custodied stablecoin balance and supported movement | Business custodial | Internal wallet addresses and custodied balances |
| A verified individual needs a Brale-custodied stablecoin balance and supported movement | Individual custodial | Internal wallet addresses and custodied balances |
| A verified business needs a self-custody destination, not a Brale-held balance | Business transactional | External destination addresses; no internal wallet |
| A verified individual needs a self-custody destination, not a Brale-held balance | Individual transactional | External destination addresses; no internal wallet |

<Note>
  Transactional accounts do not receive internal wallet addresses, do not hold Brale-custodied balances, and cannot originate on-chain transfers. See [Transactional Accounts](/guides/transactional-accounts).
</Note>

## How the model works

| Your platform | Managed customer account | Brale |
| - | - | - |
| Owns the product experience, customer relationship, and API integration | Is the verified business or individual represented by an `account_id` | Operates the applicable account, custody, verification, and compliance infrastructure |
| Designs the end-user experience and collects information required for the selected account flow | Uses the selected custodial or transactional account model | Supports the account lifecycle and provisions internal addresses for custodial accounts |

<Note>
  Account availability depends on customer type, account type, jurisdiction, verification, and program approval. Availability in a jurisdiction does not guarantee approval for every customer, payment rail, transfer direction, or funds flow. See [Account availability](/coverage/account-availability).
</Note>

Before calling `POST /accounts`, your onboarding flow must present the current [Brale End User Agreement](https://brale.xyz/legal/end-user-agreement) to the end user and capture the required consent. See [Accounts](/key-concepts/accounts) for account-creation requirements.

## Before you build

* [Compare account types](/key-concepts/account-types)
* [Check account availability](/coverage/account-availability)
* [Review the Accounts resource](/key-concepts/accounts)
* [Create an account](/api-reference/brale/create-account)

## Common questions

### Is a managed account the same as a wallet?

No. A managed account is the verified customer account identified by an `account_id`. A custodial managed account can have one or more internal wallet addresses on supported chains.

### What is the difference between custodial and transactional accounts?

Custodial accounts can hold Brale-custodied stablecoin balances in internal wallet addresses. Transactional accounts are non-custodial. They use external destination addresses and do not hold a Brale-custodied balance.

### Where are managed accounts available?

Availability depends on customer type, account type, and jurisdiction. See [Account availability](/coverage/account-availability).

### Do I need to build separate wallet infrastructure?

Not for approved custodial account flows. Brale provisions internal wallet addresses on supported chains. You still build the customer experience and integrate through the API.