Skip to main content
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. Brazil Rails and Interfaces are separate tabs in this documentation.

​
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. A native connection has one less dependency in the money path, and it follows the platform principle that clients own their stack.

​
The native family

Native messaging reaches the rails below. Each service speaks the messaging contract of a specific Brazilian settlement, clearing, or regulatory system: Three more native connectors are planned: PCR, BC Protege+, and SELIC. BC Protege+ is a BACEN service that lets a person or a company refuse new accounts in their name. SELIC (Sistema Especial de Liquidação e de Custódia) holds and settles Brazilian National Treasury securities.

​
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, Brazil Rails holds one anchor per rail. Interfaces holds one anchor per interface. That tab also lists the paths that run in production today.