Affects
Teams that create holder-owned Midaz accounts, configure Fees Engine, or use the Midaz CRM and fee documentation in deployment and operating runbooks.
What changed
The enterprise-model guide now uses
POST /v2/organizations/{organization_id}/ledgers/{ledger_id}/holders/{id}/accounts to create a holder-owned account. CRM and Fees Engine are integrated Midaz components, not standalone products or optional plugins. Fees are applied while Midaz creates a transaction; the fee-estimate operation remains a separate, package-specific preview.
These are documentation corrections that align the guides with the implemented contract. They do not announce a runtime release.
Impact
Classification: Action required. Automation that uses the former holder-account
/v1 route must move to the documented /v2 route. Deployment and setup material must not treat Fees Engine as a plugin to enable.
What you need to do
1
Replace the former holder-account
/v1 call with the documented /v2 route, including its ledger identifier.2
Review setup and deployment runbooks: configure Fees Engine fee packages in Midaz rather than enabling a Fees plugin.
3
Use the estimate operation only to preview a specific package; validate fee application through transaction creation.