Native messaging and partner interfaces

The two ways the Lerian platform reaches Brazil’s payment system — Lerian-owned messaging straight to BACEN, and adapters for connectivity partners such as JD and BTG.

The Lerian platform reaches Brazil’s payment system in two ways, and both run side by side.

Native messaging is Lerian’s own connectivity layer. It gives you 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.

A partner interface reaches the same rail through a connectivity provider’s systems. Each rail section in this documentation lists its native messaging first, then the partner interfaces available for that rail.

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 native 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 — boleto and card 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 the two models coexist

---

• A native rail connects your institution directly, on Lerian-owned software, with no connectivity partner between you and BACEN. Lerian SPI carries Pix, and it covers the full SPI messaging contract. Lerian SPB carries TED and the currently supported SPB messaging flows.
• A partner interface connects your institution through a connectivity partner — Pix through JD and BTG, TED through JD, boletos and bill payment through BTG. The partner absorbs the mechanics of the BACEN link. Your integration with the Lerian platform stays the same.

Both models preserve your ledger, accounts, and business logic regardless of how a message reaches the rail. They do not require a particular ledger; the rail emits settlement facts for your ledger consumer.

In the navigation, Pix and TED show the native rail and the partner interfaces together. The rails that only have Lerian native messaging — SILOC, SLC, STA, SISBAJUD, and Consignado — have their own sections. For the paths that run in production today, see What are Brazil Rails?.