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 individual custodial accounts, the U.S. state or (for regulated businesses) approved country for business 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. Available in supported U.S. states, and outside the United States to regulated businesses in approved countries that send a regulatory_profile. See Account availability and 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. Available in supported U.S. states and in approved countries outside the United States. See Account availability and Transactional Accounts.
  • 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.

Reliance eligibility

Under the reliance model, Brale relies on your managing entity’s own CIP/KYC program to verify the accounts you create. To qualify, your managing entity must be regulated by a U.S. federal functional regulator:
  • The Federal Reserve
  • Federal Deposit Insurance Corporation (FDIC)
  • Office of the Comptroller of the Currency (OCC)
  • National Credit Union Administration (NCUA)
  • Securities and Exchange Commission (SEC)
  • Commodity Futures Trading Commission (CFTC)
Regulation outside the United States does not qualify a managing entity for reliance. For example, an entity registered only with FINTRAC in Canada cannot use verification_mode: "reliance". To assess eligibility, Brale asks for:
  • Your legal entity name and the U.S. federal functional regulator that oversees it.
  • An overview of your CIP/KYC program, including whether you have documented policies and procedures.
  • A summary of your use case, customer types, jurisdictions, and funds flow.
Brale Risk & Compliance must approve any reliance arrangement before Brale enables it for your managing account.
Reliance eligibility applies to your managing entity, not to the accounts you create. A regulatory_profile on POST /accounts describes the customer business’s own regulator, which can be a non-U.S. authority such as FINTRAC. It determines whether that business can open a custodial account outside the United States. It does not make your managing account eligible for reliance.

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.