Skip to content

Approval Requests

The second-operator queue for high-value money actions. When maker-checker is switched on, releases (cashback, commission rebate, referral, affiliate, and EXP-redemption approvals) stop executing on the spot and land here instead — a different operator has to confirm them before any money moves.

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

Transaction → Approval Requests

  1. Open the queue — it shows Pending requests by default. Change the Status filter to see Confirmed, Rejected, or Expired items.
  2. Read each row: the Type of release, how many Items it covers, who Requested it, and when it Expires.
  3. To approve, click Confirm on the row and review the dialog, then Confirm & Execute. The release runs immediately and the money moves.
  4. To decline, click Reject, optionally add a Reason, and confirm. Nothing is released.
  • The operator who requested a release cannot confirm it — someone else must. They can, however, Reject their own request to cancel it.
  • Confirming a release needs the same permission as making that release directly. If you can release cashback, you can confirm a queued cashback release.

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 release again from its source screen if it’s still needed.

The Require second-operator approval switch at the top of the screen controls whether releases queue here at all. It is visible only to the agent owner.

  • On — releases now wait for a second operator in this queue.
  • Off — releases execute immediately, as they did before.