Payouts
Affiliate payout rules merchants should define before onboarding partners
Payout confusion is one of the fastest ways to erode trust in a partner program, even when attribution is working correctly.
Clarify when earnings become available
Partners care less about abstract payout architecture than they do about one practical question: when can I actually request my money?
That answer depends on hold periods, refund windows, and approval logic. The cleaner the explanation, the fewer payout disputes the merchant team has to manage later.
Separate readiness from approval
Being able to pay and choosing to approve a request are not the same thing. Mature programs treat readiness as a system state and approval as an operator action.
That distinction matters because it gives merchants a way to maintain control without surprising partners about how requests move through the queue.
- Readiness confirms the payout path is configured
- Approval confirms the merchant is comfortable releasing the payout
- History gives both sides a clean record of what happened
Document the edge cases before they happen
Refunds, manual payouts, minimum thresholds, and missing account details will happen. The mistake is waiting to explain them until a partner is already frustrated.
A public docs path and a clear partner-side history view dramatically reduce that friction.