Affects
Teams that create, manage, or calculate Midaz billing packages.What changed
The documentation now correctly states the current Billing contract: use the ledger-scoped v2 routes for billing packages and calculations. The organization and ledger belong in the URL. Do not sendledgerId in a query parameter or request body; the body field is rejected. Midaz monetary values are decimal strings with no asset-specific scale.
This is a documentation correction of the current runtime behavior; it does not announce a runtime release.
Impact
Classification: Action required.What you need to do
Update Billing clients, examples, and deployment runbooks to use/v2/organizations/{organization_id}/ledgers/{ledger_id}/.... Remove request-body ledgerId and define display and rounding rules in your integration instead of treating Midaz values as binary floating point.