No action
Matcher v4.3.0 — AI-assisted ingestion, discovery connectors, and Console rebrand
What changedMatcher adds AI-assisted document extraction, field-mapping proposals, and match-rule suggestions — each with a human-in-the-loop review step before anything is applied. A new discovery-connector platform onboards sources from aggregators (Pluggy, Belvo), file formats (CNAB240, CNAB400, OFX, camt.053 preview), and SFTP. API error responses are now a consistent problem shape (type, title, status, detail). The Console adopts the new ink-blue theme with refreshed navigation and breadcrumbs. Seven customer-facing reliability fixes are included.Who is affectedTeams using Matcher for reconciliation — operators uploading and mapping statements, teams building match rules, and integrations that parse Matcher API error responses.What you need to doReview the new AI extraction, mapping, and rule-suggestion flows and assign an owner to the approval step. Explore the discovery connectors if you onboard sources via aggregators or files. Confirm that any code parsing Matcher error responses handles the new problem shape. No migration is required for existing integrations.New reference: Receiving Midaz events — RabbitMQ vs Streaming Hub
What changedA new reference guide, Receiving events from Midaz, documents the two supported ways to consume the Midaz event stream — binding your own queue directly to Midaz’s RabbitMQ (AMQP 0-9-1) topic exchanges, or subscribing through Lerian’s managed Streaming Hub (Webhook, Pull, SQS, RabbitMQ, or EventBridge) — with a side-by-side comparison to help you choose.Who is affectedTeams integrating with Midaz that react to ledger events — reconciliation, notifications, downstream projections, and analytics — instead of polling the REST API, including both self-hosted deployments and external / SaaS integrators.What you need to doNo migration is required. No endpoints, event schemas, or delivery behavior changed. Self-hosted teams should review the RabbitMQ direct section and self-hosted environment flags; external consumers should review the Streaming Hub section and pick a delivery transport.New documentation structure — journey-first navigation
What changedThe documentation portal moves to a journey-first information architecture. Tabs now follow how you work — Fundamentals, Guides, API Reference, Platform, and Lerian Console — rather than splitting by product first. API Reference is regrouped by product, and product guides now cross-link to their matching API reference so you can move between a concept and its endpoints in one step. Every previous URL keeps working through redirects, so existing bookmarks and shared links resolve automatically to their new locations.Who is affectedAnyone using the Lerian documentation portal — no product, API, or runtime behavior changes.What you need to doNothing. Browse the new tabs at your own pace; old links redirect to their new locations. Update saved bookmarks whenever convenient — there is no deadline and nothing breaks if you don’t.Expanded API Reference — Pix — Direct via JD, the Midaz ledger, and Pix Automático
What changedThe API Reference gains substantial new coverage — all of it documentation, with no product, endpoint, or runtime behavior change:- Pix — Direct via JD is published for the first time, with 97 operations rendered end to end.
- The Midaz ledger reference is expanded with the holders and billing domains — 31 additional operations.
- Pix Automático payer-side operations are added to the Pix — Indirect via BTG reference.
- The former CRM reference is retired into the Midaz ledger section, where holders and related parties now live. Previous CRM reference links redirect automatically.
- The Reporter, database connections, Access Manager, and Tracer references are refreshed to match their current operations.