> ## 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.

# Native Messaging

> Lerian's own, non-intermediated messaging connections to Brazil's payment system — direct links to BACEN networks and market infrastructures across seven rails.

**Native Messaging** is Lerian's own connectivity layer with the Brazilian payment system: direct, non-intermediated links to the Central Bank of Brazil (BACEN) networks and the market infrastructures under its supervision. Lerian owns and operates these connections, rather than adapting them from a third-party provider.

## What "native" means

***

A provider interface reaches a rail through another institution's infrastructure — your traffic rides on a connectivity provider's systems. A native connection removes that intermediary: your institution's messages travel on Lerian-owned software straight to BACEN's networks (over the RSFN) and the market infrastructures that clear and settle Brazilian payments. One less dependency in the money path, and full alignment with the platform principle that clients own their stack.

## The family

***

Native Messaging spans seven rails. Each one speaks the messaging contract of a specific Brazilian settlement or clearing system:

| Rail                             | System                                         | What it moves                                                                                                          |
| -------------------------------- | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **Lerian SPB**                   | Sistema de Pagamentos Brasileiro               | TED and STR messaging — large-value interbank transfers settled in real time                                           |
| **Lerian SPI**                   | Sistema de Pagamentos Instantâneos             | Pix — instant payments settled directly in BACEN's instant-payment system                                              |
| **Lerian SILOC**                 | Sistema de Liquidação Diferida (Nuclea)        | Deferred net settlement of interbank credit orders — TEC and boleto flows                                              |
| **Lerian SLC**                   | Serviço de Liquidação Centralizada (Nuclea)    | Centralized settlement of the Brazilian card arrangement between acquirers, sub-acquirers, and settlement institutions |
| **Lerian STA**                   | Sistema de Transferência de Arquivos           | File exchange with BACEN over the RSFN — regulatory and operational file transfer                                      |
| **Lerian SISBAJUD**              | Sistema de Busca de Ativos do Poder Judiciário | Court-ordered asset searches, balance queries, and blocking and unblocking orders                                      |
| **Lerian Consignado — Dataprev** | Dataprev                                       | Payroll-deductible (consignado) credit operations exchanged with Dataprev                                              |

## How native rails coexist with provider interfaces

***

Native rails and [provider interfaces](/en/rails/what-are-brazil-rails) are two ways to reach the same payment system, and they run side by side on the platform.

* A **provider interface** connects your institution through a connectivity partner — Pix and TED via **JD**, Pix via **BTG**. The partner absorbs the mechanics of the BACEN link; your integration with the Lerian platform stays the same.
* A **native rail** connects your institution directly, on Lerian-owned software, with no connectivity partner between you and BACEN.

Both models settle through Midaz, so your ledger, accounts, and business logic are identical regardless of how a message reaches the rail. For which Pix and TED paths run in production today, see [What are Brazil Rails?](/en/rails/what-are-brazil-rails).