FinCrime Policy Pack Reference
The FinCrime pack is an Enterprise ADR-065 typed policy document. Version 3 evaluates validated detector facts about declared payment actions. It does not infer a payment from request text or search arbitrary MCP parameters for an amount. Pack v3 ships with AxonFlow Enterprise v11.2.0. Deployments on v11.1.0 remain on pack v2 until the image, registry, and version pin are upgraded together.
The Fraud & Risk Add-on is separately priced and currently offered through early access. It is unavailable in Community and Evaluation.
Installing the pack
Set AXONFLOW_POLICY_PACKS=fincrime, AXONFLOW_FINCRIME_EXPECTED_VERSION=3, and AXONFLOW_FINCRIME_REGISTRY_FILE on the agent. The registry is a reviewed, local JSON file mounted in the agent container. See enablement for an example. The agent refuses startup without a matching version pin, readable and valid registry, or interactive approval realm.
An existing v2 installation does not silently change meaning on image upgrade. Review organization overrides under pack:fincrime:*, configure the v3 registry, and opt in with the pin. To roll back, restore the v2 image and its configuration. Pack controls remain in the typed document; installation does not write legacy static_policies rows.
Scope and inputs
An action entry binds an admitted organization and client ID, a plane, exact server, tool, operation, and one class: execute, retry, beneficiary_change, or investigate. Decision API uses target.server and target.tool; MCP uses its connector, tool, and operation. A request to a registered payment server with an undeclared operation is denied, including when the server has entries only on another API plane. An unrelated server is outside FinCrime even if its statement quotes payment instructions. investigate is permitted only on an MCP query operation and does not need transaction facts or execution approval. Monetary MCP classes require execute; Decision API entries have no operation. The connector must enforce its read only contract.
For monetary classes, the caller supplies versioned fincrime_transaction and fincrime_cohort objects. The transaction context guide defines every required field. Amounts and thresholds are decimal strings in major units, compared as exact minor-unit integers using each configured ISO currency's precision. No FX conversion or universal USD cap is assumed. Missing or malformed required facts, missing currency configuration, and contradictory retry facts produce a deny. A valid execution or retry produces an approval challenge; changing a beneficiary is denied. The optional model score is a separate fact and can add an approval challenge, never a model-authored denial.
Controls
Every deterministic control is a typed constraint or requirement that reads a named detector fact. The public ID begins with pack:fincrime: followed by the suffix below. The v3 pack has eleven detector controls and one advisory score control.
| Control suffix | Result | Basis |
|---|---|---|
fincrime__invalid__context__block | Deny malformed, missing, contradictory, or unconfigured facts for a covered action | Required payment contract |
fincrime__prohibited__geography__block | Deny an endpoint on the organization's prohibited list | Operator reviewed jurisdiction settings |
fincrime__high__value__amount__cap | Deny at or above the configured cap for the transaction currency | Organization risk limit |
fincrime__payment__tool__authorization__gate | Deny a beneficiary change | Payment routing authorization |
fincrime__payment__execution__stepup | Hold execution and valid retries for approval | Human oversight |
fincrime__restricted__mcc__block | Deny a merchant category on the organization's restricted list | Operator reviewed merchant settings |
fincrime__velocity__frequency__stepup | Hold at cohort frequency 10 or more per hour | Velocity review |
fincrime__structuring__pattern__stepup | Hold transfers or wires in the configured review band below the cap | Structuring review |
fincrime__cumulative__exposure__stepup | Hold at cohort frequency 20 or more per hour | Exposure review proxy |
fincrime__geo__corridor__stepup | Hold receivers on the organization's high-risk list | Corridor review |
fincrime__cnp__high__value__stepup | Hold card-not-present payments at the configured currency threshold | Card review |
fincrime__ml__risk__stepup | Hold at the typed policy's score threshold, when a valid score exists | Advisory risk scoring |
Geography and MCC lists are organization configuration. They are empty in the example registry, so they require an operator's dated source review before use. No built-in list represents a universal sanctions or FATF rule. The example USD cap of 10000 is a sample business limit, not a universal reporting threshold.
Outcomes and evidence
Decision API returns deny for a constraint and needs_approval with a pending approval for a requirement. MCP denies with HTTP 403 or returns allowed: false through its check_policy tool. An approved retry is evaluated again. Its authorization binds the exact request, admitted principal, trusted registry digest, and typed policy bundle. Changed inputs or policy configuration require a new approval.
The response names matched controls and the installed pack digest. The audit's policy_details.fincrime_decision records version 3, action class, stable invalid-context reason when applicable, and the SHA-256 registry digest. The risk score has its own policy_details.fincrime_risk_score record. See pending approvals for the retry contract.
Tuning a control for your organization
An organization can publish a typed policy under a pack control's own ID to replace its effect within that policy's binding scope. A policy under another ID adds a control. Configure deterministic currency thresholds and geography or MCC lists in the trusted registry; edit the score threshold in a typed policy replacement under pack:fincrime:fincrime__ml__risk__stepup. Review existing replacements during a v2 to v3 upgrade because the existing detector IDs now read typed facts.
Limits
Cohort aggregates and retry history are supplied by the integrating payment service. The agent validates their shape and consistency but does not independently retrieve the underlying ledger state. Treat the action registry and the payment connector's read/write contract as operator controlled configuration. The approver pool named by the pack is not yet enforced; the approval queue's admitted approvers can answer a hold, subject to its separation of duties rule.
