Skip to main content
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:
RailSystemWhat it moves
Lerian SPBSistema de Pagamentos BrasileiroTED and STR messaging — large-value interbank transfers settled in real time
Lerian SPISistema de Pagamentos InstantâneosPix — instant payments settled directly in BACEN’s instant-payment system
Lerian SILOCSistema de Liquidação Diferida (Nuclea)Deferred net settlement of interbank credit orders — TEC and boleto flows
Lerian SLCServiço de Liquidação Centralizada (Nuclea)Centralized settlement of the Brazilian card arrangement between acquirers, sub-acquirers, and settlement institutions
Lerian STASistema de Transferência de ArquivosFile exchange with BACEN over the RSFN — regulatory and operational file transfer
Lerian SISBAJUDSistema de Busca de Ativos do Poder JudiciárioCourt-ordered asset searches, balance queries, and blocking and unblocking orders
Lerian Consignado — DataprevDataprevPayroll-deductible (consignado) credit operations exchanged with Dataprev

How native rails coexist with provider interfaces


Native rails and provider interfaces 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?.