> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# What are Brazil Rails?

> How Lerian connects your institution to Brazil's payment rails — Pix, TED, and boletos — through partner providers and Lerian-owned BACEN connections.

**Brazil Rails** is where the Lerian platform meets Brazil's payment system. Each rail — Pix, TED, Boletos & Bill Payment — is a regulated way of moving money, operated by the Central Bank of Brazil (BACEN) or by market infrastructures under its supervision. Lerian gives your institution production-ready access to these rails without giving up ownership of your ledger, your data, or your business logic.

## How this section is organized

***

The documentation here follows a **rail → provider** structure. The rail defines the domain — what Pix is, how TED transfer types work, what a boleto lifecycle looks like. The provider defines the connection — how your institution actually reaches that rail.

* **Rail-level pages** cover concepts, domains, and best practices that hold no matter how you connect.
* **Provider sections** (such as *Direct via JD* or *Indirect via BTG*) cover the integration specifics of one connectivity path.

## Two integration layers

***

Lerian connects institutions to Brazilian rails through two layers:

1. **Native messaging** — Lerian-owned, non-intermediated connections to BACEN's networks and the market infrastructures under its supervision. This layer spans seven rails, from Pix and TED settlement to file exchange and judicial asset orders. See [Native Messaging](/en/rails/native/native-messaging) for the full family.
2. **Partner interfaces** — adapters that integrate the platform with third-party connectivity providers. Today these cover Pix through **JD** and **BTG**, and TED through **JD**. Your integration with the Lerian platform stays the same; the adapter absorbs the provider's specifics.

Payment traffic on both layers settles through Midaz — same ledger, same accounts, same business logic — so the connection model never changes how you record money.

### What runs in production today

Pix runs in production through the **JD** interface — connecting as a direct participant via a certified PSTI — and through **BTG** as an indirect participant. TED runs through **JD**. The native Lerian rails are Lerian-owned software for a direct, non-intermediated connection to BACEN; they do not replace the JD and BTG paths.

## Rails and providers

***

| Rail                                                               | Available today                  |
| ------------------------------------------------------------------ | -------------------------------- |
| [Pix](/en/rails/pix/pix-overview)                                  | Direct via JD · Indirect via BTG |
| [TED](/en/rails/ted/ted-overview)                                  | Via JD                           |
| [Boletos & Bill Payment](/en/rails/boleto/boleto-and-bill-payment) | Console Payments module          |

<CardGroup cols={2}>
  <Card title="Native Messaging" icon="tower-broadcast" href="/en/rails/native/native-messaging">
    Lerian-owned, direct connections to BACEN across seven rails.
  </Card>

  <Card title="Pix" icon="bolt" href="/en/rails/pix/pix-overview">
    Brazil's instant payment system: keys, QR Codes, MED, and the Pix Switch orchestration layer.
  </Card>

  <Card title="TED" icon="building-columns" href="/en/rails/ted/ted-overview">
    Same-business-day interbank transfers with sending, receiving, and P2P flows.
  </Card>

  <Card title="Boletos & Bill Payment" icon="barcode" href="/en/rails/boleto/boleto-and-bill-payment">
    Issue boletos and pay bills through the Console Payments module.
  </Card>
</CardGroup>