Skip to main content
Pix Lerian is Lerian’s Pix plugin. It gives your institution what it needs to operate Pix at the application layer. One unified product covers transaction orchestration, key management, QR Codes, refunds, and dispute resolution. Pix Lerian is one plugin for any provider. You choose the connectivity provider that matches your participation model. Pix Lerian handles the rest. Lerian is a technology provider. We are not a PSP and we are not a PSTI. The regulated connectivity sits below Pix Lerian. Your institution chooses what provides it: a direct participant, a certified PSTI that you hire, or Lerian SPI. Lerian SPI is Lerian’s own BACEN connector, for an institution that participates directly.
The architecture and contracts described on this page reflect the current Pix Lerian product design.

​
Why Pix Lerian

Historically, supporting Pix across different connectivity providers meant maintaining separate, isolated plugins, one per provider, each with its own codebase, API contracts, and integration patterns. This created problems:
  • Duplicated business logic: Each plugin had to implement and maintain the same Pix rules independently
  • Different API contracts: Each provider integration exposed a different API to the client, making it harder to switch or add providers
  • Higher maintenance cost: You had to apply bug fixes, regulatory updates, and new features separately to each plugin
  • No portability: Moving from one provider to another required a full re-integration
Pix Lerian solves this by centralizing all Pix logic into a single product with a unified API and a Provider Adapter Layer that handles provider-specific translation. You get one integration for any provider, with no rework when your connectivity needs change.

​
What Pix Lerian provides

Pix Lerian provides a Pix orchestration layer that handles the full business lifecycle of Pix operations:
  • Cash-out and cash-in flows: Send and receive Pix payments with full message lifecycle management
  • Pix key management (DICT): Create, update, delete, and resolve ownership of Pix keys
  • Static and dynamic QR Code generation: Issue QR Codes for payment initiation
  • MED lifecycle orchestration: Manage the Special Refund Mechanism (Mecanismo Especial de Devolucao) end to end
  • Refund handling: Process full and partial refunds with proper regulatory sequencing
  • Webhooks, event processing, and background workers: React to provider events in real time and run async jobs reliably
  • Native Midaz integration: Midaz is the mandatory ledger for Pix Lerian, providing account validation, balance checks, debit/credit posting, and routing

​
How it works

Pix Lerian uses a Provider Adapter Layer to separate your integration from the specifics of any single connectivity provider. The plugin exposes a single API to your application. Behind that API, a provider adapter translates every operation (transactions, key lookups, QR Code registrations, refunds) into the protocol and format required by your configured provider. Your institution selects which provider to use during setup. The plugin resolves everything else. This architecture means that switching providers or supporting additional participation models does not require rewriting your integration. You change the configuration. The API stays the same.
Pix Lerian does not speak to BACEN itself. It operates above the SPI/DICT gateway layer and handles the Pix business logic. That gateway is a direct participant, a certified PSTI, or Lerian SPI.

​
Participation models

BACEN defines two regulatory models for Pix participation: direct (your institution connects to BACEN on its own) and indirect (you connect through a licensed direct participant). For a detailed explanation of each model, see What is Pix?. In Pix Lerian, the participation model is a configuration, not a different product. The Provider Adapter Layer supports both models. You choose a provider that matches your regulatory status, and the plugin API stays the same. Switching providers or upgrading your participation model does not require re-integrating the plugin.

​
Integrations in the Lerian ecosystem

Pix Lerian requires Midaz as its core ledger. This native integration simplifies:
  • Account validation
  • Balance checks
  • Debit/credit posting
  • Routing
  • Business rules (fees, authorizations)
Pix Lerian also connects with other Lerian ecosystem products:
  • CRM (Midaz CRM): Customer relationship and entity management
  • Fees Engine: Automated fee calculation and collection
  • Access Manager: Authentication and authorization

​
Deployment model

Pix Lerian is delivered under the BYOC (Bring Your Own Cloud) model. Your institution deploys and operates the binaries provided by Lerian in its own infrastructure, on a public cloud, private cloud, or on-premises. Your team is responsible for infrastructure operations. Lerian provides the software, updates, and agreed support.

​
Target audience

Pix Lerian is designed for institutions that:
  • Participate in the Pix arrangement (or intend to)
  • Own a valid ISPB (identifier assigned by BACEN to financial institutions in Brazil)
  • Own the ledger at the business level: your institution controls accounts and balances, regardless of where the infrastructure runs
Pix Lerian is intended for institutions prepared to operate the product under the BYOC model. Not suitable for institutions where a third party controls the ledger or account management at the business level. If your accounts and balances live inside a BaaS provider’s domain (not just its infrastructure), Pix Lerian is not the right fit. The institution must own the ledger layer logically, regardless of deployment model.

​
Requirements to operate

Before adopting Pix Lerian, your institution must have:
  • A valid ISPB registered with BACEN
  • Connectivity to the rail. For indirect participation, a contract with a direct participant. For direct participation, either a contract with a certified PSTI or Lerian SPI as your own connector
  • Logical ownership of the ledger: Midaz must be deployed and operational, with your institution controlling accounts and balances
Additional requirements for BYOC:
  • Your own cloud or on-premise environment to host the plugin
  • DevOps and SRE readiness: your team manages deployment, monitoring, updates, and incident response
  • Security and compliance ownership: your institution is responsible for access control, redundancy, observability, and audit trails

​
Advantages

​
Ecosystem-native integrations

Connect to Midaz, CRM, Fees Engine, and Access Manager out of the box. Each integration is built into the platform.

​
Customization

Extend or modify business logic to match your institution’s specific requirements. Adapt to regulatory changes at your own pace.

​
Economic efficiency

Remove reliance on multi-layer intermediaries that add cost without adding control. In BYOC, size infrastructure for your actual demand.

​
Full control and data sovereignty (BYOC)

Run everything in your own infrastructure. Apply your own IAM policies, encryption standards, and governance frameworks. Define routing rules, business policies, and operational practices. Your ledger, balances, and stored data stay in your environment. Because Pix is a payment rail, the plugin still exchanges the settlement and directory messages required to move money with the Brazilian payment system (the RSFN network operated by Banco Central), directly or through your participation provider. Owning the environment means you own the data and the infrastructure, not that no traffic ever leaves it.

​
Trade-offs

The BYOC model has the following trade-offs:
  • Requires technical maturity: Your institution needs DevOps capabilities, observability tooling, and operational management expertise.
  • Requires governance discipline: Your team must maintain security, uptime, compliance, and audit readiness.
  • More configuration upfront: Flexibility means more orchestration and parameterization during initial setup. Plan for a structured onboarding process.
  • Operational responsibility: Your institution manages software updates, patches, scaling, and continuity plans. Lerian provides the software and tooling. Your team operates it.

​
Technical reference

​
Pix use cases with Midaz

See how Pix Lerian and Midaz work together in practice:

Pix with Transaction Routes

Model validated, reusable Pix transfer flows using Transaction Routes and Operation Routes, from simple transfers to fee collection.

Pix with automated fees

Combine Pix Lerian with the Fees Engine for transparent, automated fee management across fintechs and marketplaces.