Second Approval

What it does

The second-operator queue for high-value actions. When maker-checker is switched on, these stop executing on the spot and land here instead: cashback, commission rebate and affiliate payouts and rejects, birthday bonus approvals, Coin Shop order approvals and domain affiliate bindings. A different operator has to confirm each one before it runs.

This is a safeguard: the person who requests a payout can never be the person who approves it. Two staff must agree before the money leaves.

Where to find it

Transaction → Second Approval

Common tasks

Open the queue — it shows Pending requests by default. Change the Status filter to see Confirmed, Rejected, or Expired items.
Read each row: the Type of request, how many Items it covers, who Requested it, and when it Expires.
To approve, click Confirm on the row and review the dialog, then Confirm & Execute. The request runs immediately; for a payout, the money moves.
To decline, click Reject, optionally add a Reason, and confirm. Nothing is carried out.

Who can confirm

The operator who requested an action cannot confirm it - someone else must. They can, however, Reject their own request to cancel it.
Confirming a payout needs the same permission as making that payout directly. If you can pay cashback, you can confirm a queued cashback payout.

Expiry

Each pending request has an Expires time. Once it passes, the request can no longer be confirmed - trying to do so fails and marks it Expired. Queue the action again from its source screen if it’s still needed.

Turning maker-checker on or off

The Require second-operator approval switch at the top of the screen controls whether these actions queue here at all. The agent owner sees it, and so do staff whose role has Turn second approval on or off.

On - payouts and the other actions above wait for a second operator in this queue.
Off - they execute immediately, as they did before.