Approving transactions

Edit online

Review and approve pending transactions that require policy approval.

View pending approvals

When a transaction triggers a policy that requires approval, it enters a pending state until the required approvers take action. This guide describes how to view, review, approve, or reject pending transactions.
Dashboard
  1. Select Activity in the sidebar.
  2. Filter by Pending Approvals to view transactions that require your action.
  3. Review the list of pending items. Each item shows:
    • Transaction type, such as transfer, transaction, or signature.
    • Wallet involved.
    • Amount and recipient.
    • Policy that triggered the approval.
    • Time remaining if an auto-reject timeout is configured
Notifications
Depending on your organization settings, you may receive notifications when approvals are required.
  • Slack or Teams.
  • Webhooks. The policy.approval.pending event is sent when approval is needed.

Review a pending transaction

Before approving, review the transaction details.
  1. Select the pending approval to open its details.
  2. Confirm the following information:
    • Initiator. The user who created the transaction.
    • Wallet. The wallet used for the transaction.
    • Type. Transfer, transaction, or signature.
    • Recipient. The destination address.
    • Amount. The amount being transferred.
    • Policy. The policy that required approval.
    • Other approvers. Additional approvers required for multi-signature policies.
Always verify the recipient address and amount before approving. Attackers may use similar-looking addresses to trick approvers. This method is known as address poisoning.

Approve a transaction

  1. Open the pending approval.
  2. Review all transaction details.
  3. Select Approve.
  4. Sign the approval with your passkey.
After you approve:
  • If the quorum is met, for example, 2-of-3 approvals, the transaction executes.
  • If more approvals are required, the transaction remains pending.
  • The initiator cannot approve their own transaction unless the policy explicitly allows it.

Reject transaction

If a transaction appears incorrect or suspicious, reject it.
  1. Open the pending approval.
  2. Review all transaction details.
  3. Select Reject.
  4. Provide a reason for the rejection (optional).
  5. Sign the rejection with your passkey.
After rejection:
  • The transaction is cancelled.
  • The initiator receives a notification.
  • The rejection and any provided reason are logged for audit purposes.
Whenever possible, provide a reason for the rejection. This helps the initiator understand what went wrong and prevents repeat mistakes.

Approval timeouts

Policies can specify an auto-reject timeout. If no approver acts before the timeout expires:
  • The transaction is automatically rejected.
  • No manual action is required.
  • The remaining time is displayed on the pending approval.

Quorum requirements

Some policies require a specific number of approvals. This is known as the quorum.
Quorum Meaning
1-of-2 One approval required from two users
2-of-3 Two approvals required from three users
3-of-5 Three approvals required from five users
The approval status displays:
  • How many approvals are required.
  • How many approvals have been received.
  • Which approvers have already approved.

Multiple approval groups

Some policies require approvals from multiple groups. For example:
  • One approval from Operations, and
  • One approval from Compliance.
Both conditions must be met before the transaction can execute.