Check policy

The Check policy controls how source matches become screening decisions. Read it from GET /v1/check_policy; update it with PUT /v1/check_policy; inspect prior versions at GET /v1/check_policy/history.

Policy controls

The policy includes:

• global, per-dataset, and per-use-case thresholds;
• matcher algorithm and field weights;
• source controls and default datasets;
• weak-alias behavior;
• country and device-risk handling.

Validate changes against your compliance program before publishing them. A threshold is an operational control, not an accuracy claim.

Versioning

Every accepted write produces a new policy_version. Fidera copies the exact version and complete snapshot into each Check. Every Match links to that Check and retains its source-version evidence.

This gives historical replay a stable answer even after the tenant policy changes.

Compatibility route

The operator dashboard's legacy checks-policy endpoint remains a compatibility adapter. New integrations should use /v1/check_policy; it is the public control-plane contract and exposes version history.

Safe rollout

1. Read and retain the current version.
2. Validate the proposed configuration client-side.
3. Write the complete policy document.
4. Confirm the returned version and snapshot.
5. Run representative non-production Checks.
6. Monitor decisions and Match volume without publishing unvalidated precision or recall claims.