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:
- 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 for the full family.
- 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.
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 | Direct via JD · Indirect via BTG |
| TED | Via JD |
| Boletos & Bill Payment | Console Payments module |
Native Messaging
Lerian-owned, direct connections to BACEN across seven rails.
Pix
Brazil’s instant payment system: keys, QR Codes, MED, and the Pix Switch orchestration layer.
TED
Same-business-day interbank transfers with sending, receiving, and P2P flows.
Boletos & Bill Payment
Issue boletos and pay bills through the Console Payments module.

