4-eye approval adds a mandatory second review step to payouts. When enabled, each payout submitted by one team member is held in an approval queue and can only be processed after a second authorised user approves it. The person who initiated the payout cannot approve it themselves. This reduces fraud risk and helps ensure every payout is intentional and properly authorised.
At present, this feature applies only to Batch Payouts. It does not apply to individual crypto withdrawals, single-send payouts, or other outgoing transactions.
Roles Involved
Only the following roles are relevant to multi-approval:
| Role | Can enable/disable the feature | Can be designated as an approver | Can approve/reject batch payouts |
| Owner | Yes | Yes (always eligible) | Yes, if designated |
| Administrator | No | Yes | Yes, if designated |
| Accountant | No | Yes | Yes, if designated |
Requirements to Enable
Before you can turn the feature on, your workspace must have at least two active users who are either an Owner, Administrator or Accountant. If no such two users exist, the feature cannot be enabled - there would be nobody else to approve the initiator's own payouts.
How to Enable Multi-Approval
- Navigate to the setting - From the dashboard, go to Business Settings → Users and Security → Security tab.
- Turn the feature on - Switch on the "4-eye approval for payouts" toggle.
Once enabled, every new batch payout created in the workspace will be routed through the approval queue.
Disabling Multi-Approval
The feature can only be disabled when there are no batch payouts in draft status in your workspace. If there are drafts awaiting approval, you must first approve or reject them before disabling.
This guard exists so that payouts already awaiting approval don't silently skip the approval step when the setting is flipped off.
Managing Approvers
Approvers are managed from the same place the feature is enabled - Business Settings → Users and Security → Security tab.
Once the 4-eye approval for payouts toggle is on, an "Add approver" button appears. Clicking it opens a selector listing your workspace's current active users who are eligible for the role; pick the team members you want to designate as approvers.
Rules:
- An approver must be an active Administrator, Owner, or Accountant in the workspace.
- Removing an approver does not affect approvals or rejections they have already given.
Using the Feature
When 4-eye approval is on, every batch payout needs a second person to approve it before it is processed.
- Create and upload the batch payout as usual.
- Confirm the batch payout (2FA required).
- Designated approvers are notified by email that a payout is waiting for approval.
- The batch payout sits in the approval queue until an approver acts on it. Funds are held in the meantime so they can't be spent twice.
Approving or Rejecting
Approvers can review pending batch payouts in the Batch Payouts section of the dashboard.
- Approve - the batch payout moves to In progress and is processed normally.
- Reject - the batch payout is cancelled and the held funds are returned.
A few things to keep in mind:
- The person who created the batch payout cannot approve or reject it themselves, even if they are an approver.
- Exactly one approval from another eligible approver is enough to release the payout.
Payout Statuses
| Status | Description |
| Draft | The batch payout has been created (and possibly confirmed) but has not yet been approved. Funds are already on hold if it has been confirmed. |
| Pending approval | The batch payout has been confirmed and is waiting for a designated approver to act on it. Funds are held during this time. |
| In progress | The batch payout has been approved (or multi-approval is disabled) and payouts are being processed. |
| Completed | All send requests in the batch have been processed. |
| Rejected | An approver rejected the batch payout; funds have been returned to the source account. |
| Expired | The 5-minute confirmation window elapsed without the initiator confirming. Applicable only before confirmation. |