Review recommended
Pix Indirect (BTG): documentation now public
What changedThe complete Pix Indirect (BTG) documentation set — overview, DICT operations, transfers, QR codes, collections, refunds, MED 2.0 funds recovery, intra-PSP transfers, webhooks, and integration — plus the full Indirect Pix API reference, is now available.Who is affectedTeams evaluating or building Pix Indirect (BTG) on Midaz — institutions connecting to BACEN’s Pix infrastructure as indirect participants through BTG Pactual’s BaaS offering — and anyone integrating Pix transfers, DICT, QR codes, collections, refunds, or dispute flows.What you need to doNo migration is required. No product behavior, endpoint, or API contract changed — this is a documentation availability change only. Start with the overview to understand the indirect-participant model, then reference the individual guides and API reference as needed.Accounting: Accounting Routes terminology, Overdraft scenario, and navigation update
What changedThe Accounting module documentation now uses Accounting Routes as the standard term (replacing “Transaction Routing/Routes”), adds a dedicated Overdraft scenario, and reorganizes the module navigation, in EN, ES, and PT.Who is affectedAnyone reading the Accounting module documentation in the Console, including teams configuring routing rules between accounts and reviewing accounting scenarios.What you need to doDocumentation-only — no runtime behavior changed. Update internal references from “Transaction Routing/Routes” to “Accounting Routes”, review the new Overdraft scenario, and re-check bookmarks against the reorganized navigation.BR Bank Transfer: webhook API reference and signature documentation update
What changedThe API reference now documents the webhook self-service API (register, rotate signing secret, list event types), and corrects the webhook signature format and the event names.Who is affectedTeams integrating BR Bank Transfer webhooks, and anyone using the BR Bank Transfer API reference.What you need to doDocumentation-only — no runtime behavior changed. If you validate webhook signatures or subscribe to event names, review them against the corrected documentation: the signature is nowv1,sha256= computed over v1: + timestamp + body, and non-existent event names (transfer.failed, transfer.cancelled) were removed.
