Paying affiliates sounds trivial until month three, when refunds, chargebacks, prorations, and forty different payout preferences turn 'just send money' into a part-time job. This is the setup that stays boring at scale — all of it running through Stripe infrastructure you already trust.
The architecture in one paragraph
Affiliate software tracks who referred whom and watches your Stripe billing events; commissions accrue as invoices are paid; refunds and disputes reverse accruals automatically; once a month you approve a statement; Stripe Connect moves money to each affiliate. Attribution lives outside Stripe (Stripe has no native affiliate feature); money movement lives inside it. Keeping those layers clean is what makes the rest simple.
Step 1: Accrue on invoice events, not checkout events
The single most important design decision: trigger commissions from invoice payment webhooks rather than checkout-page JavaScript. Checkout events miss upgrades, downgrades, renewals, and failed-payment retries; invoice events capture economic reality. This is also what makes recurring commissions correct without custom code — Sentalong's Stripe integration works this way, and it's the pattern every competent tool uses.
Step 2: Automate the reversal loop
- Refunded invoice → pending commission cancels automatically.
- Chargeback after payout → negative balance on the affiliate's account, offset against future earnings, visible to them in the portal.
- Dispute won → reversal reversed. (Yes, really — rare, but your tool should handle it.)
If your current process involves a spreadsheet column called 'adjustments,' this section was written for you specifically.
Step 3: Approval gate, then Stripe Connect
Monthly rhythm: review accrued amounts (thirty seconds per affiliate normally, longer only when fraud flags exist), approve, done. Behind the scenes, payouts execute through Stripe Connect transfers — no CSV uploads to a bank portal, no PayPal mass-pay files, no wire instructions emailed around. International affiliates included; Connect handles currency and rails.
Step 4: Tax forms before money, summaries after year-end
US companies paying US persons need W-9s; non-US persons need W-8BEN/W-8BEN-E. Collect these before first payout — chasing forms retroactively is miserable. Then generate 1099-ready summaries in January instead of reconstructing history from bank statements. Both are built into Sentalong's Growth plan.
Step 5: Guardrails worth enabling on day one
- Minimum payout threshold (e.g., $50) to avoid $3 transfer fees eating micro-earnings.
- Fraud hold: flagged conversions (self-referral signals, duplicate cards, shared IPs) queue for review before entering payable balance.
- Statement transparency: affiliates see exactly which invoices produced which commissions — disputes end when evidence is shared.
That's the whole machine: invoice-event accrual, automatic reversals, monthly approval, Connect transfers, forms collected upfront. Start free and run the ugly-month test on your own data before paying us anything.
FAQ
Can Stripe itself run an affiliate program?
No — Stripe processes payments and Connect handles money movement, but attribution, commission calculation, portals, and tax forms require affiliate software layered on top. Sentalong uses Stripe for both sides: reading billing events and executing payouts via Connect.
When should affiliates be paid?
Monthly cycles dominate SaaS: accrue continuously, approve one statement, pay on schedule (e.g., the 1st). Holdback periods of 30 days past the refund window are common insurance against clawback gaps.
Want the operational layer handled for you?
Sentalong tracks commissions from real billing events, reverses refunds automatically, and pays affiliates on schedule — flat pricing, no cut of your commissions.