Decision & policy control
Move from blockchain signals to an auditable banking decision.
ChainGuard applies each institution's own versioned banking policy to risk, customer context, Travel Rule status, wallet ownership and flow intelligence. The result is a canonical, explainable decision.
Policy
The policy is yours, and it is versioned.
A policy an institution cannot inspect, change under control, and point to afterwards is not a banking policy. These four properties are what make it one.
Versioned banking policies
Each institution runs its own policy version. Changes are tracked and attributable, never silently mutated.
Allowlisted typed conditions
Policy conditions are assembled from a controlled, typed set, not from arbitrary code executed against your data.
Explicit missing-data behaviour
A policy states what happens when a required input is absent, instead of defaulting silently to permissive.
Severity and priority
Every triggered rule carries a severity and a priority, and both feed the decision rather than a single opaque score.
Decision
One outcome, five possible verdicts, full history retained.
- Allow
Policy conditions satisfied
- Hold
Blocked pending resolution
- Review
Routed to an analyst
- Reject
Declined under policy
- Escalate
Raised to a senior approver
Maker / checker
Sensitive policy and decision actions require a second, independent approval before they take effect.
Recorded policy evaluation
The full evaluation, including inputs, triggered rules and result, is retained as a first-class object rather than a log line.
One canonical decision
Each case resolves to a single canonical decision at a time, with an unambiguous outcome.
Replay and successor decisions
New evidence produces a successor decision. The prior one is retained, never overwritten.
Example
A sanitized decision, end to end.
What an analyst and, later, an auditor actually sees: the verdict, the policy version behind it, the rules that fired, and what was still pending.
- Policy version
- deposit-policy v4.2
- Priority
- Medium
- Severity
- Elevated
- Triggered rules
- VELOCITY_24H, UNVERIFIED_SOURCE
- Missing data
- None
- Maker / checker
- Pending checker approval
This policy evaluation produced a canonical decision. A successor decision can be issued if new evidence arrives; prior decisions are retained, not overwritten. The compliance outcome is recorded independently of whether operational execution has occurred.
Operational execution remains separately controlled. A compliance decision does not itself trigger financial movement.
Configure banking policy that matches your institution's risk appetite.
Map ChainGuard to your institution’s transaction, policy and evidence workflows.