> 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/redemption.md). # Redemption How BRD becomes BRL again: burn against payout, verified destinations only, and what typically T+1 means in practice. Redemption is minting run backwards: tokens are burned, and the corresponding BRL is paid to a verified bank account. Burn and payout are two sides of one operation — supply falls in step with reserves, keeping the 1:1 invariant intact in both directions. ## The flow 1. **Request.** Initiate redemption in the dashboard: amount and payout destination. 2. **Destination check.** Payouts go only to destinations already verified for your organization. A new bank account must pass verification before it can be selected — see [Connect a Wallet](/brd-digital-docs/getting-started/connect-a-wallet.md). 3. **Burn.** The redeemed tokens are burned; the burn is an on-chain event you can observe independently. 4. **Payout.** The BRL payment is initiated on the banking rail, according to cutoffs and operational timelines — **typically T+1**. 5. **Confirmation.** Status is tracked in your activity history from request through payout. ## What "typically T+1" means * **T counts banking days.** A request after the daily cutoff belongs to the next banking day. * **Holidays extend it.** Bank holidays in the payout jurisdiction push settlement to the next open day. * **It is a processing norm, not a promise of instant liquidity.** Redemption converts a token claim into a bank payment, and the payment moves at its rail's speed. ## If a redemption seems stuck Check the request's status in the dashboard first — most "stuck" redemptions are a cutoff or a holiday calendar doing what it always does. If the status itself looks wrong, or a payout is confirmed sent but has not arrived, contact the desk with the redemption reference. ## Related pages * [Redeem BRD](/brd-digital-docs/getting-started/redeem-brd.md) — first-time walkthrough * [Minting](/brd-digital-docs/stablecoin/minting.md) — the forward path * [Proof of Reserves](/brd-digital-docs/stablecoin/proof-of-reserves.md) — how supply and reserves stay verifiably matched --- # 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/redemption.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.