The challenge for direct participants
Direct Pix participants must establish and maintain a technical link with BACEN’s instant payment infrastructure (SPI and DICT). This connectivity is provided through a certified PSTI such as JD, which exposes the standardized interfaces required by BACEN. While this model grants full operational autonomy, it introduces significant technical and regulatory responsibilities, including:
- Integration with JD’s SPI/DICT interfaces, following strict message structure and signing requirements
- DICT lifecycle management (key registration, confirmation, deletion, portability and ownership claims)
- Real-time transaction orchestration with sub-second SLAs
- Webhook ingestion and asynchronous event handling
- Transaction limit enforcement with daily and nightly rules
- QR Code generation and EMV-compliant decoding
- Compliance with all Pix rules issued by BACEN
- High-availability processing with 24/7 monitoring
- Alignment between JD events, BACEN settlement, and internal ledger posting
The Lerian solution
The Direct Pix Plugin provides a unified processing layer that abstracts the complexity of direct Pix connectivity. It integrates natively with JD (a PSTI), handling all SPI and DICT interactions on behalf of your institution. The plugin manages:
- JD protocol authentication, signing, and message formatting
- DICT entry lifecycle (creation, confirmation, claims, portability, deletion)
- Transactions: cash-in, cash-out, refunds, reversals
- QR Code generation and decoding (static, dynamic immediate, dynamic with due date)
- Webhook ingestion from JD and automatic ledger posting
- Transaction limit validation (daily, nightly, monthly)
- Directory queries for participant information
- Real-time validation for incoming payment requests
- Comprehensive error handling aligned with JD responses
Key benefits
Direct BACEN Connectivity
Native connectivity to SPI and DICT through JD, eliminating protocol implementation and certification effort.Accelerated Integration
No need to build message parsers, signature layers, token managers, or DICT orchestrators.Native Midaz Integration
Real-time balance checks, holds, postings, and operation routing — without custom mapping.Aligned with Lerian Ecosystem
Seamless connections to CRM, Reporter, Matcher, Flowker, Fee, and Access Manager.Complete DICT Management
Full key lifecycle: creation, confirmation, portability, ownership claims, and deletion.QR Code Operations
Support for static, dynamic immediate, and dynamic due-date EMV QR Codes.Transaction Resilience
Retry mechanisms, reconciliation workers, and eventual consistency workflows.Enterprise Security & Observability
Audit trails, structured logs, access control, and full operational tracing.Regulatory Compliance
Pre-configured workflows aligned with BACEN requirements for direct participants.Scalable Architecture
Optimized for high-volume, low-latency Pix operations with horizontal scaling.Functional architecture
The Direct Pix Plugin is composed of five core modules, each handling a domain of Pix operations while preserving end-to-end cohesion.
1. PIX Keys (Entries) Module
- Register, update, delete keys
- Confirm phone/email keys
- Track status and pending confirmations
- Retrieve payee information from DICT
2. Claims Module
- Initiate portability or ownership claims
- Receive, approve, or reject inbound claims
- Track claim lifecycle and deadlines
3. QR Code Module
- Generate static and dynamic QR Codes
- Decode EMV payloads
- Validate format compliance
- Link QR Codes to transaction flows
4. Transactions Module
- Outbound Pix (cash-out)
- Inbound Pix (cash-in)
- Refunds and partial refunds
- Transaction query and listing
- Resilience and recovery workers
5. Limits Module
- Configure daily, nightly, and monthly limits
- Real-time remaining-limit calculation
- Automatic period resets
6. Banks & Participants Module
- JD Participant Directory
- Query institutions by ISPB
- Identify participant type (direct/indirect)
Lerian ecosystem integrations
Native integrations
- Midaz Ledger — real-time posting and validation
- CRM Plugin — customer and alias account metadata
- Fee Engine — automated fee logic
- Access Manager — OAuth2 and credential management
Figure 1. Lerian Pix native integrations
Downstream integrations
- Reporter — regulatory reporting
- Matcher — multi-layer reconciliation
- Flowker — workflow orchestration
Requirements to operate Direct Pix
Regulatory
- Must be a direct Pix participant (own ISPB)
- Must operate through a certified PSTI (e.g., JD)
- Must maintain valid SPI/DICT certificates and credentials
Technical
- Midaz as core ledger
- CRM for holder & alias-account management
- API Gateway accessibility
- BYOC or on-premise infrastructure
- Webhook endpoints for JD event ingestion
Operational
- 24/7 monitoring
- Incident response process
- Reconciliation routines
- Support for key and transaction disputes