Payout and contract issues

Steps

1. Confirm whether the issue is about account linking, active method selection, request eligibility, merchant review status, or contract signing.
2. Check the current status badge before trying to fix the problem.
3. Review the connected settings page or contract detail before taking a new action.
4. Confirm whether the problem belongs to the partner side or merchant side.

Common causes

• Missing payout request action usually means the active method is not automated, the linked account is not verified, the threshold is not met, or another request is pending, under review, approved, or processing.
• Stripe says Connect Stripe first means the Stripe account-linking step is not finished yet. Setting the method active does not create the Stripe connection.
• Method shows unavailable usually means the merchant has not enabled or connected it. Stripe Connect is the implemented live automated provider; PayPal Payouts is unavailable until platform OAuth and permissions are configured.
• Merchant cannot approve a request usually means the method is not runnable or a production preflight check is failing.
• Pending payout means the merchant still needs to review the request.
• Cancelled request releases the exact commission rows reserved when the request was submitted.
• Failed or dead-letter payout needs review of execution attempts, provider references, errors, and operational health before a safe retry.
• Reversed payout requires reconciliation because a previously recorded settlement was subsequently reversed.
• Voided or expired contract means that version cannot be signed anymore.
• Viewed but unsigned contract means the partner opened the agreement but has not finished signing yet.

Example

A partner cannot request payout, checks the page again, and finds that Stripe still says Connect Stripe first. The next step is to finish the Stripe linking flow for the current store instead of retrying Set as active.

Tips and limits

• Check the status before retrying a payout or signing action.
• Merchants should review payout readiness before troubleshooting partner-side request errors.
• Partners should confirm the active store before assuming a payout or contract record is missing.
• The personal threshold override currently applies across store contexts because it is stored on the creator profile.
• Live execution fails closed when the safety gate, encryption, Stripe platform credentials, webhook secret, worker authorization, or production runtime is not ready.

Common fixes