> 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/stablecoin/minting.md).

# Minting

Registering intent, choosing a funding source, and what happens between a deposit and tokens in your wallet.

Minting is how BRD enters circulation: a verified account holder funds a mint request, and cleared funds convert 1:1 into tokens. There is no discretionary issuance.

## 1 · Register the intent

Minting starts with a request, not a transfer. In the dashboard you tell the platform you want to mint and choose what you are funding with:

<table><thead><tr><th width="170">Funding source</th><th>Settlement</th></tr></thead><tbody><tr><td><strong>PIX</strong> (BRL)</td><td>Settles in seconds, 24/7, including weekends and holidays.</td></tr><tr><td><strong>USD</strong></td><td>Provided through regulated partners, on those partners' operating hours.</td></tr><tr><td><strong>USDC</strong></td><td>Settles on network finality.</td></tr></tbody></table>

You receive instructions and a **reference** specific to that request. The reference is how the incoming payment is matched to your account, so send it exactly as shown.

## 2 · Fund it

Send the funds from an account or wallet belonging to you or your verified organization. Transfers from unrelated third parties do not meet institutional-grade compliance expectations and are held for review.

## 3 · What happens to the deposit

1. **Receipt.** The payment arrives at the platform's banking or on-chain endpoint.
2. **Screening.** Sender and payment are screened against sanctions lists, source of funds, and consistency with your profile.
3. **Reconciliation.** The reference is matched to your account. A missing or altered reference is the most common cause of a stalled mint.
4. **Clearing.** The platform waits for the rail's own settlement guarantee.
5. **Delivery.** Tokens are delivered to your registered wallet, and the on-chain transaction appears in your activity history.

## Instant mints and the buffer

A quantity of BRD is kept pre-minted so mints and redemptions can settle instantly rather than waiting on issuance. The size of that buffer varies over time, and is sized to cover smaller transactions.

Requests larger than the available buffer are minted against the deposit directly, which takes longer. The dashboard tells you which path your request is on.

## The cleared-funds rule

Minting happens against **cleared** funds, not received funds. "Cleared" is rail-specific: PIX settlement confirmation, or sufficient on-chain finality for a stablecoin deposit. The rule exists so a reversed or failed payment can never leave unbacked tokens in circulation. It is the operational face of the 1:1 invariant.

## Commercial terms

Minting terms applicable to your organization are agreed during onboarding and available from the institutional desk.

## Related pages

* Redemption, the reverse path
* Proof of Reserves, where the deposit goes once cleared


---

# 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/stablecoin/minting.md?ask=<question>&goal=<user_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.