Lerian provides dedicated Pix plugins for each model, enabling institutions to adopt the architecture that best matches their regulatory status, infrastructure ownership, and operational strategy. This overview explains the practical differences between the Direct Pix Plugin and the Indirect Pix Plugin, helping institutions choose the model that aligns with their needs.

​

1. What changes between Direct and Indirect Pix?

---

The primary difference lies in how your institution connects to the Central Bank’s infrastructure (SPI and DICT) — and who is responsible for operating that connection.

​

Direct Pix

Your institution connects directly to BACEN’s systems (SPI/DICT) and maintains full operational autonomy.

​

Indirect Pix

Your institution connects to Pix through a Direct Participant, using their infrastructure as a gateway. Each model has distinct responsibilities, capabilities, and operational implications — and Lerian’s plugins are designed to support both.

​

2. Direct Pix Plugin

---

For institutions with full Pix autonomy and direct BACEN connectivity The Direct Pix Plugin is designed for institutions that are (or intend to become) Direct Participants in Pix. In this model, your institution:

• Has its own ISPB registered as a Direct Participant
• Maintains a direct link to SPI and DICT
• Operates its own settlement, liquidity, and Pix compliance
• Is responsible for all BACEN-mandated technical, operational, and security standards

The Lerian Direct Pix Plugin uses the JD infrastructure as the SPI/DICT connectivity layer, enabling institutions to meet all BACEN communication and protocol requirements while still retaining full operational autonomy. Lerian provides the software layer — JD provides the certified connectivity. The plugin delivers the complete Pix capability set:

• Full DICT lifecycle (create, update, delete, portability, ownership claims)
• Static and dynamic QR Codes
• Outbound and inbound Pix flows
• Refunds, reversals, and regulated workflows
• Limits and validation rules
• Complete message orchestration
• MED (Special Refund Mechanism)

This model is suited for institutions that want full independence and control over their Pix operation. Best fit for:

• Banks and regulated institutions with operational maturity
• Organizations seeking full DICT management
• Institutions with a complete DevOps and governance structure
• Entities requiring deep customization of the Pix pipeline

​

3. Indirect Pix Plugin

---

For institutions that operate Pix through a Direct Participant The Indirect Pix Plugin is designed for institutions registered as Indirect Participants in Pix. Instead of connecting directly to BACEN, your institution uses the infrastructure of a Direct Participant, who becomes responsible for:

• SPI and DICT connectivity
• Settlement and clearing
• Availability and routing
• Regulatory compliance for message transmission

Your institution remains responsible for customer accounts and balances in Midaz, while the Direct Participant handles the Pix network layer. The plugin abstracts all communication with the Direct Participant, delivering:

• Cash-out (send) and cash-in (receive) flows
• Refunds (full and partial)
• Key validation
• Static and dynamic-immediate QR Codes
• Reconciliation and sync flows
• MED support when applicable

It dramatically simplifies Pix adoption by removing the complexity of direct BACEN connectivity. Best fit for:

• Fintechs registered as indirect participants
• Institutions seeking fast onboarding
• Teams without capacity to operate DICT infrastructure
• Businesses focused on sending and receiving Pix

​

4. Key differences at a glance

---

​

5. How to choose the right plugin for your institution

---

​

Choose Direct Pix if your institution:

• Has (or will obtain) Direct Participant status
• Needs full DICT control and MED autonomy
• Has internal DevOps and compliance readiness
• Operates at large scale
• Requires complete control over the Pix pipeline

​

Choose Indirect Pix if your institution:

• Operates as an Indirect Participant
• Wants a simpler, faster integration
• Prefers reduced operational responsibility
• Works with a Direct Participant partner
• Needs Pix without managing DICT directly