> 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/cross-border.md).

# Cross-border

Institutional-grade FX and settlement between BRL and other currencies, with the rate known before you commit.

Cross-border operations move value between BRL and other currencies: funded on one rail, settled in stablecoins at a quoted rate, paid out on another.

## What it replaces

A conventional BRL cross-border payment traverses two or three intermediaries, each adding time and a spread, with the rate discovered after the fact and IOF applied on top. A BRD corridor is one operation, priced before you commit, visible end to end from the dashboard: **quote → fund → settle → payout**.

Where an operation has a US dollar leg, that leg is provided through regulated partners.

## Rails

<table><thead><tr><th width="200">Rail</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>Stablecoins</strong> (on-chain)</td><td>Settle on network finality, subject to network conditions.</td></tr></tbody></table>

## Settlement times

Timelines vary with the rails involved, the counterparty, and the size of the operation.

* **On-chain legs** settle on network finality, subject to network speed and congestion.
* **PIX legs** settle in seconds, at any hour.
* **Legs provided through regulated partners** follow that partner's operating hours, cut-offs and holiday calendars.

When estimating arrival, look at the slowest leg in the operation rather than the average. The dashboard shows which stage an operation is in at any point.

## What to expect operationally

* **The rate is quoted first.** You see and accept the price before anything moves. See FX Conversion.
* **Compliance is in the loop.** Operations are screened to institutional-grade standards, and supporting documentation may be required. Having invoices or contracts ready keeps things moving.
* **End-to-end visibility.** Every leg is tracked in your activity history.

## In this section

* Settlement Flow, the corridor stage by stage.
* FX Conversion, how quoting works.


---

# 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/cross-border.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.