Affects
Teams evaluating or building Indirect Pix (BTG) on Midaz — institutions that connect to BACEN’s Pix infrastructure as indirect participants through BTG Pactual’s Banking as a Service offering, and anyone integrating Pix transfers, DICT operations, QR codes, collections, refunds, or dispute flows. This is a documentation availability change only. The Indirect Pix plugin and its behavior are unchanged; the reference and guide pages that describe it are now available.
What changed
The complete Indirect Pix (BTG) documentation set is now published and readable by everyone. Previously access-limited, these pages are now part of the public documentation.
Guides now available
- What is Indirect Pix (BTG)? — BTG’s role as a direct participant, the split of responsibilities, and why BTG.
- DICT operations — Pix key lookups, registrations, and claim resolution at the BACEN directory level.
- Pix transfers — initiating and processing Pix payment messages through SPI.
- QR codes — static and dynamic QR code generation and decoding.
- Collections — immediate and due-date charges.
- Refund operations — full and distributed partial refunds.
- MED 2.0 funds recovery — tracking fraudulent fund movements and coordinated recovery.
- Intra-PSP (P2P) transfers — internal transfers reported to BACEN via TRCK002.
- Webhooks — real-time event callbacks with mTLS security.
- Integration — connecting your institution to BTG’s Pix APIs.
Impact
This is an informational change. No product behavior, endpoint, or API contract changes. Nothing to migrate and no action is required to keep existing integrations working. Classification: Informational. The change is that this documentation is now openly available for reference and evaluation.
What you need to do
1
If you are evaluating Indirect Pix (BTG), start with the overview to understand the indirect-participant model.
2
Teams already integrating can reference the DICT, transfers, QR code, collections, refund, MED 2.0, intra-PSP, and webhook guides directly.
3
Use the Indirect Pix API reference for endpoint-level details.

