Affects
Teams integrating with Midaz CRM or Fees APIs, deploying Midaz with Helm, or using Tracer with Midaz v4.
What changed
The Midaz v4 reference now identifies Ledger
/v2 as the current API surface for Core, CRM, and Fees. Ledger /v1 remains available only for compatibility. The standalone Fees Engine reference was retired; its legacy URLs redirected to their Midaz destinations until September 10, 2026 (see Page URLs now mirror the navigation).
CRM and Fees run as modules of the unified Midaz Ledger runtime; they are not standalone deployments. CRM account associations use Instruments, and the Fees error reference uses the canonical numeric codes.
Tracer is source available under ELv2 in the Midaz v4 repository, but remains a separately deployed service. Its public HTTP API is /v1. Ledger /v2 can opt in to the reservation integration; Ledger /v1 does not use it.
Impact
Classification: Action required.
What you need to do
1
Move active CRM and Fees integrations to the Ledger
/v2 reference, and treat /v1 as a compatibility surface.2
Update Helm values and runbooks so CRM and Fees are deployed with Midaz, not as standalone services. Validate any Tracer reservation integration against the v4 deployment guidance.