Payout operations

Steps

ScreenshotSteps 1-3

Local image

ScreenshotSteps 4-5

Local image

Step 1.

Open Payouts and start in Request Queue.

Step 2.

Use Queue Status, Search, and row selection to narrow the request list before taking action.

Step 3.

Approve or decline one request at a time, or use Approve Selected and Decline Selected when several pending requests are ready together.

Step 4.

Switch to Payout History to review completed, failed, processing, or reversed payouts with status, method, and search filters.

Step 5.

Use Record Manual Payout when the payout happened outside the automated request flow. Search the partner first, then enter amount, reference number, method, notes, and an optional HTTPS proof-of-payment URL.

Settings explained

• Request Queue is where partner-initiated requests wait for merchant review. Submission transactionally reserves the exact commission rows, preventing duplicate requests for the same earnings. Rejection or partner cancellation releases the reservation.
• Gateway blocking banner appears when no automated provider is runnable for the shop. Stripe Connect is the implemented live provider; PayPal Payouts remains unavailable until platform OAuth and permissions are configured.
• Partial availability banner appears when one automated method is unavailable. In that state, requests for other runnable methods can still be approved.
• Approval and execution are separate stages. Approval creates a durable execution job; Stripe processing is idempotent, and webhooks plus reconciliation update settlement status.
• Operational health shows runtime state, live preflight, execution jobs, attempts, provider references, and errors. Investigate the cause before using the safe retry action on a dead-letter job.
• Test mode still exercises reservation, approval, durable jobs, settlement, ledger, and balance behavior; only the external provider call is mocked.
• Payout History stores processed payout records and supports History Status, History Method, and Search filters.
• Record Manual Payout stores a payout that was completed outside the automated request flow. It is for documentation and reconciliation, not for pushing funds through Stripe or PayPal.

Example

A merchant filters Request Queue to pending items, approves two ready Stripe requests, reviews their execution jobs, and records an external bank transfer with a reference and proof URL.

Tips and limits

• Review fraud warnings before approving unusual payout activity.
• If a request cannot be approved, confirm that the request method is still enabled and connected for the current shop.
• Do not approve live payout requests until Payout Settings shows the shop is ready for the method you expect to use.
• A normal request moves through pending → under review → approved → processing → paid; alternate outcomes include rejected, cancelled, failed, and reversed.
• Add clear notes and reference numbers when using Record Manual Payout so the history remains understandable later.