> 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/getting-started/redeem-brd.md).

# Redeem BRD

Converting BRD back to fiat: request redemption in the dashboard, tokens are burned, and funds arrive at your verified bank account — typically T+1.

Redemption is the mint in reverse: tokens are burned, and the corresponding BRL is paid out to a bank account your organization has verified.

## The flow

1. **Request redemption** in the dashboard, choosing the amount and the payout destination.
2. **Destination check.** Payouts go only to [approved destinations](/brd-digital-docs/getting-started/connect-a-wallet.md) — a new bank account must be verified before it can receive funds.
3. **Burn and payout.** The tokens are burned and the payout is initiated on the banking rail. Redemptions are processed according to cutoffs and operational timelines — **typically T+1**.
4. **Confirmation.** The redemption, the burn transaction, and the payout status all appear in your activity history.

## Timing expectations

* Requests after the day's cutoff process on the next banking day.
* Bank holidays in the payout jurisdiction extend the timeline — T+1 counts banking days, not calendar days.
* A redemption pending past expectation is almost always a cutoff or calendar effect; the desk can confirm the specific payment's status.

The full mechanics are on [Stablecoin → Redemption](/brd-digital-docs/stablecoin/redemption.md).

## Done with the basics?

You have the full loop: fund, mint, operate, redeem. From here:

* [Yield](/brd-digital-docs/yield.md) — put idle balances to work as sBRD.
* [Cross-border](/brd-digital-docs/cross-border.md) — quote, convert and settle across currencies.
* [Compliance](/brd-digital-docs/compliance.md) — the framework behind the gates you just walked through.


---

# 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/getting-started/redeem-brd.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.