> 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/connect-a-wallet.md).

# Connect a Wallet

Where tokens are delivered, and where funds are allowed to leave. Both are set once and then enforced.

BRD delivers minted tokens to a **registered wallet** and pays funds out only to **approved destinations**. Both are set up once and then enforced by the platform. This page explains how, and why.

## Registered wallets

During onboarding you provide the wallet address, or custody account, where minted BRD should be delivered. The address is registered to your account and confirmed with you before first use. BRD is live on Solana, Ethereum and Base, and the contracts for each are listed on [Stablecoin](/brd-digital-docs/stablecoin.md).

## Withdrawal destinations

Funds leave the platform only toward destinations on your account's approved list:

* **Bank accounts** for fiat redemption, verified as belonging to you or your organization.
* **Wallet addresses** for on-chain withdrawals, registered ahead of use.

New destinations enter the list as **pending** and become usable only after approval. The list, and the status of each destination, is visible in the dashboard's wallet section.

{% hint style="info" %}
**Why the friction exists.** If a session is ever compromised, an attacker who cannot add a destination cannot redirect funds. Approval of new destinations is the control that turns a stolen session from a catastrophe into an inconvenience. It is standard practice at institutional-grade venues, and it is why the step is not optional.
{% endhint %}

## Deposit instructions

The dashboard's wallet section carries your deposit instructions per rail: PIX details for BRL, and an address for stablecoin deposits. Each carries the reference that ties an incoming payment to your account.

{% hint style="warning" %}
**Always copy deposit details from the dashboard, never from an email or a chat message.** Deposit instructions and destination addresses are exactly what phishing tries to substitute. The dashboard, behind your two-factor login, is the only place to trust them.
{% endhint %}

## Next step

→ Mint BRD


---

# 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/connect-a-wallet.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.