Skip to main content
POST /accounts accepts three optional discriminator fields that determine how Brale verifies the account and what it can do:
Omitting all three dimension fields produces exactly today’s behavior. Existing integrations that create business accounts do not need to change.

​
Supported combinations

All eight combinations of the three dimension fields are supported: verification_mode: "reliance" is enabled per managing account by Brale and is not self-serve. A caller without reliance enabled receives 422 unsupported_account_combination. verification_mode: "bypass" is not supported for any combination and also returns 422 unsupported_account_combination. An unsupported combination is rejected with 422 unsupported_account_combination. The rejection is permanent, so it is safe for clients to cache the error against an idempotency key. Where each combination is geographically available depends on the account’s location: the U.S. state for custodial accounts, and the U.S. state or approved country for transactional accounts. See Account availability for the canonical state table and the approved country list.

​
When to choose each

  • Business, custodial — a business entity that will hold stablecoin balances in Brale-custodied wallets, initiate transfers, and use Brale as its record of funds. See Custodial Accounts.
  • Business, transactional — a KYB-verified business that is non-custodial: it has no internal Brale wallet and no stored balance at Brale. It can register external, self-custody destination addresses, which are destination-only. Subject to the business state-availability perimeter in Account availability.
  • Individual, custodial — a natural person who holds stablecoin balances in Brale-custodied wallets. The request shape is identical to the individual transactional path; only account_type changes. U.S.-only, with a narrower state list than business custodial — see Account availability.
  • Individual, transactional — a natural person who receives value on-chain (for example, as the destination of an on-ramp) but does not hold custody with Brale. See Individual accounts.
On any of these rows, verification_mode is standard by default. Use reliance only when your integration operates under an agreement with Brale that specifies a reliance model and Brale has enabled it for your managing account.

​
Backward compatibility

The dimension fields are optional and default to the values that describe today’s account. A request that omits entity_type, account_type, and verification_mode continues to create a KYB-verified business account with Brale-custodied wallets, exactly as before.