Payouts, alerts, and fraud review

Steps

Step 1.

Open Payouts and review Request Queue.

Step 2.

Approve or decline requests after checking method readiness, request status, and any payout availability banners.

Step 3.

Switch to Payout History when you need processed payout records.

Step 4.

Use Record Manual Payout when you need to record a direct payout handled outside automated gateways.

Step 5.

Review Merchant Alerts for operational warnings and required actions.

Step 6.

Review Fraud Alerts for suspicious activity and record the final review decision.

Settings explained

• Request Queue is for partner-initiated payout requests that still need merchant action.
• Payout History is for completed or previously recorded payouts.
• Gateway banners warn you when automated approvals are blocked or when one automated payout method is temporarily unavailable for the current shop.
• Approval Simulation can appear in test mode so merchants can simulate success or failure without calling live gateways.
• Merchant alerts cover important account, workflow, or system warnings.
• Fraud alerts focus on suspicious orders or attribution behavior that may need action or dismissal.

Example

A merchant sees a pending payout request, notices a banner that PayPal is unavailable for the current shop, reviews the fraud event tied to the same partner, and then decides whether the Stripe request should move forward or be declined.

Tips and limits

• This page is an overview. Use the detailed payout, merchant alerts, and fraud pages for exact workflows.
• Do not approve payout requests until payout settings show the merchant account is ready.
• Review fraud warnings before approving unusual payout activity.
• Add notes whenever you decline or manually process a payout so the history stays understandable later.