Transaction Policies

Transaction Policy lets you create policies that decide what happens to each outbound transaction from your team wallet: allow it, require approval, or block it. Every transaction is checked against your policies from top to bottom, and the first policy that matches decides the outcome, so the order of your policies matters.

You can set up your policies under your team’s “…” menu, in Security, then Transaction Policy. Only owners can create or change policies; other members, such as Authorized Signers and Requestors, cannot. Changing it is governed by your team quorum, so edits may need owner approval.

Each policy has matching conditions and an outcome. Conditions decide which transactions the policy applies to. Leave a field as Any to match everything, or set it to narrow the policy:

• Blockchain: which network
• Token: which asset
• From: the sending wallet
• To: the destination
• Transfer Limit (USD): an amount, for example transfers above a set value

Outcome decides what happens when a transaction matches:

• Allow: the transaction proceeds. You pick the Designated Signer, who can sign it.
• Require Approval: it needs sign-off first. You pick the Designated Approver, the Approver Threshold (how many approvals), and the Designated Signer.
• Block: the transaction is rejected.

1. Step 1From your team home, tap the “…” menu, then under Security tap Transaction Policy.
2. Step 2Tap Add Policy and name it. The policy type is set to Transfer by default, with Bridge, Swap, and more coming soon.
3. Step 3Set the conditions: Blockchain, Token, From, To, and Transfer Limit. Leave a field as Any to match everything.
4. Step 4Choose the outcome: Allow, Require Approval, or Block. Pick the Designated Signer, and for Require Approval, the approver and threshold.
5. Step 5Tap Confirm & Submit. If approval is required, the new policy appears greyed at the bottom of the list as pending until another owner approves.

1. Step 1When another owner adds, edits, reorders, or deletes a policy, you get a notification and a Pending Action. The pending policy shows greyed at the bottom of the list.
2. Step 2Open the request to see what’s changing, who asked, and when.
3. Step 3Tap Approve to apply it, or Reject to decline. You can add a reason when rejecting.
4. Step 4On approval the change applies for the whole team. On rejection nothing changes. Either way it’s recorded in your notifications log.

• Put specific policies above general ones. Since the first match decides the outcome, a broad allow-anything policy near the top can override stricter ones below it.
• Use Require Approval with a threshold for high-value transfers, so large transactions need a second owner’s sign-off.
• Start broad, then tighten your policies as your team and usage change.
• Make policy changes while owners are available, since they may need approval.