What the policy engine controls
The rules that are applied to every payment automatically, and where each one bites.
Version 1.0 · Last updated
When you would read this
Before you change anything in Governance › Policies, and when you want to understand why a particular payment was held.
Everyone can view your policies. Only an Admin can change them.
How policies are applied
Every payment request is checked against your policies automatically when it is created. There is no route that skips them, and no per-payment override.
A policy decides two things: whether a payment can proceed on one signature or needs your full quorum, and whether it needs anything extra from a human before it can be signed.
What you can control
Document requirement threshold. Payments above this amount require an uploaded invoice or supporting document before they can be signed.
New recipient flag threshold. First-time recipients above this amount are flagged for additional review.
External payment self-approval. Below this limit one signer can create and send a payment alone. Above it, your quorum applies. This can also be switched off entirely, so that every external payment needs at least one additional signer.
Swap self-approval. A separate per-transaction limit for swaps, which can also be switched off so all swaps need quorum.
Earn self-approval. Whether a single signer can deposit to and withdraw from Earn vaults, or whether full quorum is required.
Internal transfers. Whether moves between your own vaults are auto-approved, and up to what amount.
Strict payout mode. If a batch payout contains any address that is new to you, the whole batch is flagged for Admin review.
Solo operator safeguards. If you are the only signer, require dual verification, both authenticator code and passkey, when paying a first-time address.
Native token self-approval limits. Separate per-coin limits for native coins such as ETH, BTC and SOL, entered in units of that coin. Until you enable and configure these, native coin payments require full quorum regardless of the limits set elsewhere.
Starting templates
Two templates give you a sensible starting point: Standard, which is efficiency focused, and Strict, which is control focused. Pick one and then adjust individual controls. The Policy Summary panel restates your current settings in plain language, and is worth reading back before you publish.
What to expect
Policies are applied at the moment a payment request is created, against the rules in force at that instant. The rules that applied are stored with the transaction and appear in its evidence pack, so a decision can always be reconstructed against the rules of the day rather than today's rules.