Policy Engine
Your rules, enforced before signing.
Set rules for who can move funds, how much, to which addresses, and when — enforced before a transaction is signed, no app-layer bypasses.
How it works
Every transaction passes through three gates
The policy engine sits between your application and the signing layer. Transactions cannot reach signing without passing every applicable rule.
Transaction submitted
A transaction is initiated — by a user, an automated system, or an AI agent. It enters the policy engine with its full context: sender, recipient, amount, token, chain, and time of day.
Rules run in order
Each rule is evaluated against the transaction context, cascading from most restrictive to most permissive. The first match determines whether to approve, reject, or escalate the transaction.
Outcome enforced
Approved transactions proceed to the signing layer. Rejected transactions are blocked instantly with an alert. Escalated transactions are held pending approvals from the configured quorum.
One engine, total control
Set per-asset spending limits, daily caps, and velocity controls. Transactions that exceed your thresholds are held or rejected automatically — before they ever reach the signing layer.
Configure multi-signature approval flows that reflect your real organizational structure. High-value transfers can require sign-off from a CFO, a risk officer, and an operations lead — all enforced before the transaction reaches the signing layer.
Manage every rule, role, and approval policy from a single console. One engine governs all your wallets and chains, so policy stays consistent no matter where assets move.
Every control you need, out of the box
Pre-built controls you can combine into policies as granular as your operations require — no custom code.
Velocity caps
Limit how many transactions can occur within any time window — stopping sweeping attacks and unusual automation in their tracks.
Address whitelists
Only permit outflows to pre-approved addresses. New destinations require explicit approval before funds can flow there.
Role-based approvals
Assign approval authority by organizational role. CFOs, risk officers, and operations leads each have defined scope and signing power.
Per-token rules
Apply different policies to different assets. BTC, stablecoins, and DeFi tokens can each carry their own controls and limits.
AML / KYT integration
Block outflows to flagged addresses automatically. Chainalysis and Elliptic risk scores are available as conditions in any rule.
Full audit trails
Every policy decision — approval, rejection, or escalation — is logged with full context and exportable for compliance review.
Put the policy engine to the test.