Version compatibility

This page helps you understand which plugin versions are compatible with Midaz Core and Midaz Console, so you can plan upgrades safely and avoid runtime issues.

Compatibility table

Plugin	Midaz v2 Compatibility	Midaz v3 Compatibility	Notes
Access Manager	✅ v1	✅ v2	Each Midaz version requires a specific plugin version
CRM	✅ All versions	✅ All versions	Fully compatible across all versions of Midaz
Fees Engine	❌ Not supported	✅ Supported	Only available starting from Midaz v3
Smart Templates	✅ v1 and v2	✅ v1 and v2	Depends on which fields are used in the template

Smart Templates compatibility

Smart Templates v1 and v2 are compatible with both Midaz v2 and v3 — but their compatibility depends on the fields used in your templates, not just the plugin version.

❗️
Important
Some fields were removed or changed in Midaz v3. Templates using deprecated or removed fields will only work with Midaz v2.

Key compatibility rules

If your template uses only fields that exist in both Midaz v2 and v3, it will run on both versions.
- If your template includes fields deprecated or removed in Midaz v3, such as scale, it will only work with Midaz v2.
- If your template uses fields introduced in Midaz v3, such as value, it will only work with Midaz v3.

✅
Tip
To ensure compatibility across versions, use only the fields supported by both Midaz v2 and v3, and avoid deprecated ones like scale.

Midaz Console and the plugins

All plugins are only compatible with Midaz Console v3. Earlier versions of the Console do not support them.

Upgrade recommendations

Always upgrade Midaz Core first, then the plugins.
CRM and Smart Templates offer the most flexible versioning, but still require payload compatibility.
Fee Engine and Access Manager must match the Midaz version exactly.
Always test new combinations in staging before deploying to production.