BTG’s role in the Pix ecosystem
As the direct participant, BTG handles the layers that require regulatory licensing and direct BACEN integration:
- SPI connectivity — Sends and receives Pix payment messages (pacs.008, pacs.002, pacs.004) through BACEN’s real-time settlement infrastructure
- DICT access — Manages Pix key lookups, registrations, and claim resolutions at the BACEN directory level
- Settlement and liquidity — Processes financial settlement between institutions through BACEN’s infrastructure
- Regulatory compliance — Maintains the certifications, audits, and operational requirements BACEN mandates for direct participants
- Webhook notifications — Delivers real-time event callbacks for transaction status changes, key events, and dispute updates
- mTLS security — Provides certificate-based authentication for secure webhook communication
Your institution retains full control of its ledger, customer data, business rules, and operational infrastructure. BTG provides connectivity — not account management.
- MED 2.0 Funds Recovery — track fraudulent fund movements across accounts and request coordinated refunds
- Distributed partial refunds — return a refund debited from multiple internal accounts in one operation
- Intra-PSP (P2P) transfers — settle internal transfers without BTG, while reporting to BACEN via TRCK002
- Unblock — recover refunds or transfers stuck in
PROCESSING
Why BTG
BTG brings specific advantages as a direct participant for Pix operations:
- Production-ready infrastructure — BTG already operates at scale in the Pix ecosystem, processing high volumes with proven reliability
- Native integration with Lerian — The Indirect Pix Plugin includes built-in support for BTG’s APIs, authentication, and event model, eliminating custom middleware
- Faster time to market — Institutions launch Pix in weeks instead of months, since BTG absorbs the regulatory and infrastructure complexity
- Enterprise-grade security — mTLS webhook validation, API credential management, and certificate rotation come built into the integration
- Simplified onboarding — BTG provides credentials directly when your institution signs up for indirect BACEN integration — no separate certification process required
Next steps
With this context, explore how to configure and operate the plugin with BTG:
- Setting up the integration — Configure the plugin’s connection to BTG, Midaz, CRM, and all supporting services
- Webhooks — Event types, payloads, retries, and best practices for handling BTG notifications
- MED 2.0 — Funds Recovery — Cross-account fraud recovery and the X-Purpose header
- Refund operations — Distributed partial refunds and unblocking stuck operations
- Intra-PSP transfers — Internal P2P settlement and TRCK002 reporting
- API reference — Full API documentation for DICT, Claims, Transactions, QR Codes, and MED operations

