Individual accounts

• Custodial — the account receives Brale-custodied wallets and can hold stablecoin balances at Brale. U.S.-only, with a narrower state list than business custodial accounts.
• Transactional — the account is non-custodial: it receives no custodial wallets, cannot create custodial addresses, and is shaped for inbound value. Use it when your end user needs to receive stablecoins on-chain or be the destination of an on-ramp, but should not hold a Brale-custodied wallet.

​

What it does

• Registers a natural person as a Brale account (entity_type: individual, with account_type: custodial or account_type: transactional).
• Runs KYC identity verification on the individual.
• Emits the same account.verification.* webhook events as business KYB.
• Custodial: provisions Brale-custodied (type=internal) wallets the account can hold balances in.
• Transactional: lets you register external on-chain destination addresses so the account can receive value.

​

Who it’s for

• End users of a wallet or fintech app who hold stablecoin balances in Brale-custodied wallets (custodial).
• Payout recipients who need to receive stablecoins on-chain but do not hold balances at Brale (transactional).
• End users of a wallet or fintech app who receive on-ramps to their own self-custody wallet (transactional).
• Any natural person your platform needs to identify and pay, without provisioning custody (transactional).

​

Choosing custodial or transactional

​

What a transactional account cannot do

• No Brale-custodied wallets, ever. A transactional account has no automatic custodial wallet at creation and cannot hold internal (type=internal) addresses. This is enforced.
• External addresses are destination-only. An external address on a transactional account can receive value but cannot be the source of a transfer.
• The account cannot originate an on-chain transfer. An attempt returns 422 with type compatible_address_not_found. Checking the address balance first does not predict this, because the constraint is about the address role, not funds.
• Automations from a transactional account may only target external destinations. A Brale-custodied destination is rejected.

​

How it works

1. Create the account.
   Call POST /accounts with entity_type: individual, account_type: transactional, an individual object, and a tos_attestation. Business-only fields (business_name, ein, website, business_controller, beneficial_owners) must not be sent. See Accounts — Creating an individual account for the full payload and field reference.
   Request

   {
     "entity_type": "individual",
     "account_type": "transactional",
     "verification_mode": "standard",
     "individual": {
       "first_name": "Jane",
       "last_name": "Doe",
       "date_of_birth": "1990-01-01",
       "email": "[email protected]",
       "phone_number": "2125550182",
       "country": "US",
       "address": {
         "street_line_1": "123 Main St",
         "street_line_2": "Apt 4",
         "city": "Des Moines",
         "state": "IA",
         "zip": "50309"
       },
       "identity": {
         "number": "222-22-2222",
         "type": "SSN9"
       }
     },
     "tos_attestation": {
       "version": "2025-04-01",
       "accepted_at": "2026-05-13T20:45:15Z",
       "ip": "203.0.113.42",
       "user_agent": "Mozilla/5.0 ..."
     }
   }
   
   201 Response

   {
     "id": "3Ar9BnQCKIrB3SYjKGBzCtFs6XL",
     "name": "Jane Doe",
     "status": "pending",
     "created": "2026-05-13T20:45:16Z",
     "updated": "2026-05-13T20:45:16Z"
   }
   
   The created account’s name is derived from the individual’s first and last name. Non-US individuals in approved countries are supported; see Account availability for the country list. individual.address.state is optional and free-form, and the postal code accepts any format; send the identity document type that matches the individual’s country. See Identity types for the accepted values and Creating a non-US individual account for an example.
2. Wait for verification.
   Brale runs identity verification asynchronously. On approval the account is enabled, status becomes complete, and account.verification.completed fires. This is typically fast — on the order of seconds. If more documents are needed, account.verification.documents_required fires with the required documents; stage and link them exactly as documented for business accounts. Polling is also supported.
3. Add an external destination address.
   Register the on-chain wallet that will receive value with POST /accounts/{account_id}/addresses/external. External addresses on a transactional account are destination-only.
   Request

   {
     "name": "Recipient EVM Wallet",
     "address": "0xb518d4d6221d9a41d23d71cbce8e106e7aab8f9b",
     "transfer_types": ["ethereum", "base"]
   }
   
4. Receive value.
   The account’s external addresses can be used as the destination in transfers originating elsewhere (for example, an on-ramp automation owned by your managing account). Inbound events carry data.account_id so a subscription on the managing account can attribute them to the correct managed account. See Webhook Events.
5. Do not attempt to originate transfers from this account.
   Any attempt to use an external address on a transactional account as a transfer source returns 422 compatible_address_not_found. Route outbound value through a different, custodial account.

​

Managed by the API key owner

​

Use an individual account as an Automation brand

{
  "name": "Jane Doe Onramp",
  "source": { "value_type": "USD" },
  "destination": {
    "address_id": "2MhCCIHulVdXrHiEuQDJvnKbSkl",
    "value_type": "SBC",
    "transfer_type": "Solana"
  },
  "brand": { "account_id": "3Ar9BnQCKIrB3SYjKGBzCtFs6XL" }
}

​

Related API references

• POST /accounts — create an individual account.
• GET /accounts/{account_id} — check verification status.
• POST /accounts/{account_id}/addresses/external — register a destination address.
• POST /documents and Link verification documents — supply KYC documents when requested.
• Webhook Events — account.verification.completed, account.verification.rejected, account.verification.documents_required, and inbound payment events with data.account_id.