> For the complete documentation index, see [llms.txt](https://brd-digital.gitbook.io/brd-digital-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brd-digital.gitbook.io/brd-digital-docs/overview.md). # Overview BRD Digital builds BRL infrastructure on-chain: a fully reserved real-denominated stablecoin, sovereign-bond yield, and cross-border settlement. **BRD** is the stablecoin, a BRL-denominated token fully reserved by Brazilian Treasury LFTs. **BRD Digital** is the company that issues BRD and operates the infrastructure around it. Brazil is easy to operate in and hard to reach. PIX made domestic payments instant and free. Everything that crosses the border, or needs to be programmable, still runs on rails built for a different era: correspondent chains, business hours, FX priced after the fact, and IOF on top. That is a distribution problem. Most companies do not offer Brazil because connecting to it means a local entity, local banking relationships, and months of work before the first transaction. ## Products
ProductWhat it does
BRDThe BRL settlement asset, fully reserved 1:1 by Brazilian Treasury LFTs. Mint with PIX, USD or USDC, hold and settle on-chain, redeem to BRL.
YieldSovereign-bond yield, on-chain. sBRD is live and BRL-denominated. sBRDusd is USD-settled, coming.
Cross-borderInstitutional-grade FX and settlement between BRL and other currencies, on stablecoin rails.
## Three ways in ### 1 · Direct account Hold an account with BRD Digital. Verify once, then mint, redeem, hold yield-bearing balances and run cross-border operations from the dashboard. 1. **Verify.** Sign up at [brd.digital](https://brd.digital/login). Identity verification runs through SumSub. Organizations onboard through KYB. 2. **Register your intent to mint,** choosing what you are funding with: PIX in BRL, USD, or USDC. The instructions and reference you get back are specific to that request. 3. **Fund and mint.** Cleared funds convert 1:1 into BRD, delivered to your registered wallet. 4. **Operate.** Hold, transfer, settle, earn, or send across a corridor. 5. **Redeem.** Burn BRD and receive BRL back to a verified account. → [Getting Started](/brd-digital-docs/getting-started.md) ### 2 · Through a partner A verified third party such as a wallet, a PSP or a fintech integrates once and passes the capability to its own users. Those users are onboarded by the partner and never deal with BRD Digital directly. The planned surfaces are a **PIX API** for BRL in and out with KYC and KYB handled in the flow, a **cross-border API** for FX and settlement on major pairs, and a **yield API** routing to the yield contracts. {% hint style="warning" %} The partner APIs are **not live**. Talk to the institutional desk if you want to be early. {% endhint %} ### 3 · On-chain BRD trades on public liquidity pools, and the yield products are reachable on-chain. A deposit is a transaction with the protocol rather than an onboarding with BRD Digital, which is what lets these products reach wallets that would never open an account. Using a yield position as collateral in a lending market, and looping it through something like Morpho, raises the return and adds that protocol's smart-contract risk. That risk is opt-in, and separate from the collateral. {% hint style="info" %} **What runs through BRD Digital.** Minting with fiat and redeeming to a bank account, both requiring verification. Buying, holding and transferring BRD do not. {% endhint %} ## Where BRD Digital is going The direction is a full-stack BRL on-chain offering that partners build on rather than rebuild: * **BRL PIX in and out**, with KYC and KYB included. * **Cross-border FX** on major pairs, from BRL to stablecoins, to fiat, and back. * **Yield from sovereign bonds**, accessible on-chain. * **Stablecoin payment functionality**, settled in BRL. One integration gets all four, and a partner's users never need an account with BRD Digital. ## The regulatory framework The Brazilian Central Bank has now set out the rulemaking and legal framework for virtual asset service providers operating in the country, implemented in two phases. **Phase 1** runs to October 2026. Companies that meet its requirements are permitted to operate as though they held the licence while the framework is being put in place. **Phase 2** runs until the end of 2029. On its conclusion, companies that have completed the process hold the licence itself. BRD Digital operates under this framework. See [Compliance](/brd-digital-docs/compliance.md). ## The invariant One rule holds the model together: **tokens in circulation are matched 1:1 by reserves**. Supply is readable from the chain, and the reserve position is published. You check the two against each other rather than taking either on faith. → Proof of Reserves --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://brd-digital.gitbook.io/brd-digital-docs/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.