Integrating a BRL Stablecoin by API: Sub-Accounts, Pix Deposits, Conversion Orders and Webhooks

A product team integrating a BRL stablecoin needs to know what the API covers before deciding what to build around it. Crown’s platform, which issues BRLV and operates Crown FX, is fully accessible through a secure web interface or by API, with public documentation at docs.crown-brlv.com and an OpenAPI specification available. The API is authenticated with API keys and JWT tokens. This is what it lets a team do.

Accounts and sub-accounts

The API creates and queries accounts and sub-accounts. Sub-accounts follow a partner model, designed for companies that serve their own clients and need each client represented separately. A webhook signals when a sub-account is approved.

Wallets and transfers

Teams create wallets and transfer tokens between EVM wallets. BRLV is an ERC-20 token issued on Ethereum, Base and Tempo, and the official source for contract addresses is the whitepaper at the documentation site. A contract address published outside official channels should be treated as suspect.

Pix deposits and withdrawals

The API generates a Pix QR Code for deposits in reais and tracks the deposits. Withdrawals can be requested by Pix, TED or token. Redemption of BRLV for reais, at R$ 1.00 per BRLV, is requested by interface or API, and Crown sends the amount by Pix to a bank account in the client’s name.

Quotes and conversion orders

For Crown FX, the API returns quotes and executes conversion orders between assets, such as BRL or BRLV to USDC or USDT. Execution through API is instant and settles within minutes. The business side of the same capability, including when a company is better served by an OTC desk, is covered in real-time BRL settlement for ERPs.

Balances, history and reconciliation

The API returns balances and the full transaction history, with every on-chain transaction linked and identified. That traceability matters for operational control and for accounting and tax reconciliation, a requirement that also appears in the treasury criteria in non-USD stablecoins for corporate treasury.

Webhooks

Webhooks are emitted for each event: deposit processed, order completed, transfer completed, withdrawal completed, redemption completed and sub-account approved. A system that reacts to these events does not need to poll for status, which is the practical difference between an integration that reconciles in real time and one that reconciles in batches.

What the integration does not remove

An API covers operation, not evaluation. Before building, a bank or fintech still has to assess backing, legal structure, regulatory standing and compliance, the dimensions laid out in what a bank should evaluate before adopting an on-chain real settlement layer. For companies whose use case is paying counterparties abroad, the comparison with bank transfers is in paying contractors in Brazil: BRLV vs. wire transfers. The issuer is Crown.