An affiliate program can bring paid users and still fail finance. Stripe may show a paid invoice while the referral is missing, the commission rule is unclear, or a payout is released before a refund arrives.
Your Stripe affiliate dashboard needs to answer four questions: who sent the customer, what the customer paid, what the affiliate earned, and whether that commission is payable. Rewardful manages referral attribution and commission operations around Stripe payments. Stripe remains the billing record and moves the money.
Build the program in order. Set the policy, connect payments, configure tracking, test real paths, then invite affiliates.
Define the Program Rules Before You Connect
Write a one-page affiliate policy before opening Rewardful. State which products qualify, how long commissions last, which customers count, and how you treat refunds.
Decide how you handle existing customers and self-referrals. A founder using their own link to buy a plan should not create a commission by accident. The same rule should cover employees, contractors, coupon sites, and customer referral credits.
Assign clear owners before launch:
- Marketing owns affiliate recruitment, campaign terms, and content approval.
- Development owns the referral script, Checkout changes, and release testing.
- Finance owns payout approval, refund checks, and the payment record.
- Support owns affiliate questions and routes account disputes to the right person.
Don’t publish an affiliate signup page until these owners agree on the rules.
Check Rewardful Plan Limits First
Don’t design a multi-campaign program or custom portal before checking your plan. Rewardful’s Starter plan includes one campaign and up to two team members. Growth adds unlimited campaigns, unlimited team members, a branded affiliate portal, and a custom domain. Review the live Rewardful pricing and plan limits before you configure the program.
Start with one campaign if your offer is simple. Multiple campaigns make sense when partners promote different products, regions, or commission terms. They create more reporting and review work.
Connect Stripe and Choose Your Checkout Path
Sign in to Rewardful and use the Stripe connection flow to authorize the Stripe account that receives your subscription revenue. Follow Rewardful’s instructions to connect your Stripe account.
Rewardful needs access to monitor relevant Stripe activity for referral tracking and commission automation. Stripe still handles charges, refunds, disputes, and payouts. Rewardful does not control your funds.
Check that you selected the right Stripe account before moving on. This matters when a company has separate Stripe accounts for products, regions, or legal entities.
Pass the Referral ID Into Checkout
Your developer needs to identify how Checkout starts.
A client-side Checkout flow starts in the browser. A server-side flow creates the Checkout Session in your application backend. The tracking method must match the flow.
For server-side Checkout, pass Rewardful’s referral click ID into Stripe as client_reference_id when you create the Checkout Session. Rewardful documents that handoff in its server-side Stripe Checkout guide.
A payment can succeed in Stripe without this value. The customer gets access, but the affiliate may not get credit. Treat that as a tracking failure, not a finance problem.
Build a Stripe Affiliate Dashboard in Rewardful
Rewardful is the affiliate operating layer. Stripe is the payment ledger. Keep those roles separate.
Create your first campaign and give it a clear name. Use a name that tells your team what the rules are, such as “Partner Program, Monthly SaaS Plans.” Avoid vague names like “Default” or “New Campaign.”
Set the campaign commission, cookie duration, attribution method, and commission term. Add yourself or a teammate as a test affiliate before inviting anyone else.
Give Affiliates One Place to Work
Each approved affiliate gets a personal dashboard where they can create referral links and review their results. Your team can review affiliates, referred customers, sales, and commissions from the merchant side.
A good Stripe affiliate dashboard gives affiliates enough information to promote the product without exposing customer payment details. Show their links, clicks, conversions, pending commissions, due commissions, and paid history.
Keep your public program page simple. Explain the product, commission policy, approval rules, payout timing, and prohibited promotion methods.
Set Commission Rules You Can Afford
Rewardful supports percentage-based and fixed commissions. It can track recurring payments, and you can limit commissions by number of payments or months.
Base your policy on money that was actually collected. Rewardful creates commissions when Stripe invoices are paid, then adjusts them for refunds, cancellations, upgrades, downgrades, and subscription changes.
A simple SaaS policy might pay 20% of each paid Pro subscription invoice for the first 12 payments. Another program may pay a fixed amount after a customer completes a paid month. Pick the model that matches your margin and sales cycle.
Don’t promise lifetime commissions unless you can support them through pricing changes, customer migrations, and refunds.
Match the Due Date to Your Refund Policy
Commissions start as pending. Rewardful’s default due date is 30 days after the original sale, but you can change the timing.
Set the due period long enough to cover your refund window and common dispute period. Add a minimum payout threshold if small payments would create extra finance work.
Rewardful’s cookie and commission controls let you adjust these campaign settings. Document the final policy in your affiliate terms. Don’t make affiliates guess why a commission is pending.
Configure Cookies, Attribution, and Coupon Rules
Cookie length should match the way customers buy. A self-serve tool with a short decision cycle may use a shorter window. A product with demos, procurement, and several decision-makers may need more time.
Choose one attribution rule and publish it. If your program uses last-click attribution, say that. If it credits the first qualified referral, say that. Don’t change the rule after a sale without recording the reason.
Test Cross-Domain Tracking
Many SaaS sites use one domain for marketing, another for the app, and Stripe Checkout for billing. A referral can disappear when the visitor moves between those steps.
Test the full route from affiliate link to pricing page, signup, Checkout, and payment confirmation. Confirm the referral survives when a visitor starts on www, moves to app, and pays through Stripe.
A valid Stripe payment does not prove that the affiliate referral reached Checkout.
Treat Affiliate Coupons as a Separate Rule
Affiliate links and affiliate coupons can work together, but they can also conflict. Assign a coupon to one affiliate only. Decide whether a coupon overrides an existing referral cookie or follows the existing attribution rule.
Update your privacy notice and cookie consent flow as needed. If a consent tool blocks the referral script, the program may lose attribution before the visitor reaches Stripe.
Test the Full Payment Path Before Launch
Don’t test only the affiliate link. Test the outcome that finance will approve.
Rewardful’s client-side setup process recommends opening a test affiliate URL in a private browser window, such as one using ?via=install, letting the site load, then checking the setup status. Use the client-side Stripe Checkout instructions if your browser starts Checkout.
Run a Controlled Test Matrix
Use a test affiliate and record the expected result for each case.
- Open the affiliate link in an incognito window and confirm Rewardful records the visitor or referral.
- Complete a controlled signup and Checkout flow, then confirm Stripe contains the expected customer and payment record.
- Check Rewardful for the customer referral, campaign assignment, and pending commission.
- Test a trial conversion, coupon, failed payment, refund, cancellation, upgrade, and downgrade.
Keep the test customer ID, Checkout Session ID, invoice ID, affiliate ID, campaign name, and final result in a short test log. Don’t overwrite the original Stripe record to make a report look correct.
A completed test run is not enough. Finance should approve the expected commission result before you invite affiliates.
Block Fraud Before It Reaches Payout
Start with a small, approved affiliate group. Don’t open the program to every applicant on day one.
Review suspicious patterns before payouts. Watch for self-referrals, repeated customer details, sudden conversion spikes, coupon abuse, refunded purchases, and affiliates whose traffic does not match their promotion method.
Rewardful lets you mark an affiliate as Suspicious. That stops new referral, sales, and commission tracking for that affiliate. Use the status after review, not as an automatic response to one unusual sale.
Use Stripe Data as a Second Check
Compare affiliate performance with Stripe payment behavior. Stripe’s Radar analytics center can help you monitor fraud and dispute activity across your account.
Hold commissions through the pending period when a customer payment looks unusual. Review the affiliate, customer, payment status, refund activity, and referral source together.
Send every new affiliate a short onboarding email. Include their referral link, commission terms, approved promotion channels, prohibited behavior, payout schedule, and support contact. Ask them to test a click, not to buy their own product.
Review Reporting Every Week
Your Stripe affiliate dashboard should not become a report that nobody checks. Review it weekly while the program is new, then set a schedule that matches affiliate volume and payout timing.
Track Approved Commissions, Not Raw Activity
Use a simple reconciliation report before every payout.
| Metric | What to check |
|---|---|
| Referred paid revenue | Match Rewardful conversions with paid Stripe invoices |
| Pending commissions | Check refund windows, payment status, and payout thresholds |
| Due commissions | Confirm finance has approved the affiliate and sale |
| Voided or adjusted commissions | Review refunds, cancellations, disputes, and fraud decisions |
| Missing referrals | Investigate paid customers without expected attribution |
Clicks and completed workflow runs are not success metrics. Track commissions that finance accepts after payment and policy checks.
Rewardful explains how it reads Stripe payment activity and manages the commission lifecycle in its guide to affiliate commission payments.
Keep a Recovery Record
Store the original Stripe payment data unchanged. Put the referral mismatch, reviewer notes, and final decision in separate fields or a ticket.
Record the campaign version, policy change date, payout batch, reviewer, and reason for any voided commission. This gives your team a usable history when an affiliate asks about an older sale.
Create a manual fallback before launch. Name the person who exports Stripe invoices and Rewardful commissions if tracking breaks. Keep the last trusted payout report available, and pause payouts until the mismatch is resolved.
If your Checkout flow spans multiple domains, custom subscription logic, or more than one Stripe account, Book A Call before you publish affiliate terms.
Final Checks Before You Invite Affiliates
A working program is not defined by a polished portal or a high click count. It is defined by accurate referral records, commission rules your margin supports, and payouts finance can verify.
Build the Stripe affiliate dashboard around paid invoices, clear attribution, controlled testing, and a review process for exceptions. That gives affiliates a fair system and gives your team a payment record it can trust.
