AxonFlow v11.2.0 Release Notes

v11.2.0 requires a coordinated license update for licensed deployments. The Enterprise Fraud & Risk Add-on also moves from FinCrime pack v2 to v3. Complete the actions below before replacing a v11.1.0 image.

Before you upgrade

1. Arrange a replacement license with AxonFlow. The v11.2.0 images trust new license verification keys. A license signed for v11.1.0 does not validate on a v11.2.0 image, and the replacement license does not validate on v11.1.0. Coordinate the license and image switch for each stack. Keep the previous license version available for rollback. Self-serve evaluation licenses also require reissue.
2. If you installed FinCrime pack v2, prepare v3 configuration with the image. Review the v3 action registry, set AXONFLOW_FINCRIME_EXPECTED_VERSION=3, mount the reviewed v3 registry, and review organization policy replacements under pack:fincrime:*. A v3 image with a v2 pin or registry refuses startup. Keep the v2 image and configuration together for rollback.
3. Verify the approval path before a payment action. The Decision API or MCP call must name an admitted organization, client, plane, server, tool, and operation, with complete versioned transaction facts. An execution may return needs_approval; it is not permission to execute. A named human reviews the hold, and the caller retries the same bound input with the approval ID. Execute only after the retry returns allow and names the consumed approval ID.

FinCrime v3

The Enterprise add-on governs exact registered payment actions across Decision API and MCP. It reads typed transaction and cohort facts, validates decimal major-unit amounts and ISO currency precision, and applies organization-specific limits and jurisdiction lists. Missing, contradictory, or unconfigured facts deny. Unrelated prose and actions on an unregistered server do not activate the pack. The decision audit records the registry digest, matched controls, and reason. See the policy pack reference and transaction context contract.

The advisory risk scoring service remains optional. Its score can cause a review hold but does not by itself block a payment. The deterministic controls still apply when the scorer is unavailable.

Payment exception example

The Enterprise payment exception example demonstrates evidence reconciliation, a constrained operator screen, a Decision API approval hold, named portal review, and a retry whose provider outcome is reconciled separately. It uses a synthetic provider and fake executor. It does not execute a real payment or claim a customer savings result.

SDKs and compatibility

Go, Python, TypeScript, and Java SDK v9.5.0, plus Rust v0.12.0, add typed target.server, request approval_id, response pending_approval, and consumed approval_id fields for the Decision API. Older SDKs continue to support existing calls but do not expose this complete approval retry contract through their typed request and response models. Raw HTTP callers may use the documented API directly.

Client versions

These are the client versions included in this release train:

Client	Version	Notes
Python SDK	9.5.0	Typed payment action and approval retry fields.
TypeScript / Go / Java SDK	9.5.0	Typed payment action and approval retry fields.
Rust SDK (preview)	0.12.0	Typed payment action and approval retry fields.
openclaw plugin	2.9.1	No plugin release in this train.
Claude Code plugin	1.13.0	No plugin release in this train.
Cursor plugin	1.9.0	No plugin release in this train.
Codex plugin	1.9.0	No plugin release in this train.
Claude Desktop proxy	0.4.0	No proxy release in this train.
n8n node	1.2.1	No integration release in this train.
Google ADK plugin	1.3.1	No integration release in this train.
LiteLLM integration	1.1.0	No integration release in this train.

Rollback

Roll back the image and its matching license together. If FinCrime was installed, restore the v2 image, pack pin, and registry together. An approval already consumed by an allowed retry must not be replayed.