Affiliate tracking breaks when checkout, billing, and commission records sit in separate systems. A Stripe Rewardful integration connects those records, so attributed Stripe payments can create and update affiliate commissions without manual spreadsheet work.
The connection is simple on paper. The details matter once you add Payment Links, custom checkout, subscription renewals, refunds, and cancellation rules.
Set up the payment path first. Then test every event before affiliates send real traffic.
HOW THE STRIPE REWARDFUL INTEGRATION WORKS
Rewardful connects to your Stripe account and monitors payment activity tied to referred customers. It tracks commissions when invoices are paid, then adjusts those records as subscription billing changes.
A typical path looks like this:
- An affiliate shares a Rewardful referral link.
- A visitor lands on your site and the tracking script stores the referral.
- Your checkout passes the referral into Stripe.
- Stripe creates the customer, payment, or subscription.
- Rewardful matches the customer and billing activity to the affiliate.
- Rewardful creates or updates the commission record.
STRIPE IS THE BILLING RECORD
Stripe remains your payment source of truth. It holds the customer, invoice, subscription, refund, and payment status.
Rewardful uses that billing activity for affiliate attribution and commissions. Its two-way Stripe sync can also write limited metadata back to Stripe customers and invoices. That gives your team a way to reconcile a commission with the payment that created it.
REWARDFUL IS THE AFFILIATE RECORD
Rewardful holds the affiliate, campaign, referral source, commission status, and payout workflow. Its commission states include pending, due, paid, and voided.
Do not treat an affiliate click as revenue. Do not treat a pending commission as a completed cost. Stripe payment status and Rewardful commission status can change later.
CONNECT STRIPE AND CREATE THE CAMPAIGN
Start in Rewardful. Create your account, then use “Connect with Stripe” to authorize access to the Stripe account that receives customer payments.
Rewardful’s current setup guidance focuses on connecting Stripe, then creating your first campaign. The available official documentation does not list a required Rewardful plan tier or fixed price for the Stripe connection. Check your current account plan before launch, especially if you need multiple campaigns, team access, or payout features.
BUILD THE CAMPAIGN BEFORE INVITING AFFILIATES
Create a campaign with rules that match your actual billing model. Decide whether affiliates earn:
- A percentage of each paid invoice.
- A fixed amount for a new paid customer.
- A first-payment commission only.
- Ongoing recurring commissions for active subscriptions.
Keep the offer simple. A 20% recurring commission needs a clear duration, such as 12 months or the life of the subscription. Write the rule before anyone promotes it.
Rewardful supports subscription businesses on Stripe and states that it calculates commissions when invoices are paid. That makes the campaign configuration more important than a polished affiliate signup page.
A recurring commission is tied to paid billing activity, not to the day an affiliate sends the referral.
DO NOT BUILD DUPLICATE WEBHOOK LOGIC
Rewardful describes its Stripe connection as automatic. Its published guidance says you do not need to configure separate webhook mappings for the standard integration.
Your product may still need Stripe webhooks for provisioning, failed-payment handling, access control, and internal reporting. Stripe explains that a webhook endpoint receives events that happen outside the immediate checkout flow in its webhook documentation.
Keep those responsibilities separate. Let Rewardful track affiliate commissions. Let your application handle product access and customer lifecycle actions.
PASS ATTRIBUTION INTO YOUR CHECKOUT FLOW
The connection alone cannot fix a checkout flow that loses the referral ID. Your setup method depends on how customers pay.
STRIPE CHECKOUT NEEDS THE REFERRAL ID
For a client-side Stripe Checkout flow, Rewardful documents passing the referral through clientReferenceId. For a server-side Checkout flow, pass it through Stripe’s client_reference_id.
That value links the browser referral to the checkout session. If your development team creates Checkout Sessions on the server, tell them not to drop this field during a checkout rebuild.
Use the Rewardful server-side Checkout instructions for the documented implementation path. Do not invent a custom parameter name because it looks cleaner in your codebase.
PAYMENT LINKS REQUIRE A STRIPE CUSTOMER
Stripe Payment Links can work with Rewardful, but the setup has one condition. In Stripe, enable “Save Payment Details for Future Use” on the Payment Link.
Rewardful relies on Stripe Customer objects to attribute referrals correctly. For an existing link, Stripe documents editing it through the Payment Links area and advanced options. Rewardful’s Payment Links integration guide covers this setting.
If you skip the customer-creation setting, a paid transaction may exist in Stripe without a customer record Rewardful can match. That is an attribution failure, not a commission calculation problem.
API-BASED BILLING NEEDS CUSTOMER METADATA
Some SaaS products do not use Stripe Checkout or Payment Links. They create customers directly through the Stripe API.
In that setup, retrieve Rewardful.referral from the tracking script and store it in Stripe customer metadata with the key referral. This gives Rewardful a customer-level attribution record.
Do not assume a referral cookie will survive every path. Cross-device journeys, blocked scripts, ad blockers, cleared cookies, and a later affiliate click can change the result. Test the exact route your customers use.
HANDLE SUBSCRIPTIONS, REFUNDS, AND CANCELLATIONS
A Stripe Rewardful integration is not a one-time setup task. Billing events continue after the first conversion.
SUBSCRIPTIONS CREATE RECURRING COMMISSION EVENTS
A new paid subscription can create the first commission. Later paid invoices can create recurring commissions if your campaign rule allows them.
Upgrades and downgrades need review. Rewardful states that it automatically adjusts commissions for subscription changes, cancellations, and trials. Still, check a sample against the Stripe invoice amount after you change pricing or introduce annual plans.
Stripe’s subscription webhook guidance is useful for your product team. It covers events for payment failures, subscription status changes, trials, and customer authentication requirements.
REFUNDS AND CANCELLATIONS ARE DIFFERENT
A cancellation stops future billing. It does not always reverse a payment that already succeeded.
A refund returns money from a completed payment. It can change the affiliate commission tied to that payment. Review your campaign terms for timing and approval rules before commissions become due.
Keep an adjustment record instead of overwriting history. If a customer pays a $1,000 invoice and the affiliate earns 20%, the original commission is $200. If you later issue a $250 refund, record the $50 negative adjustment separately.
This gives finance a clear audit trail. It also prevents duplicate payouts after a refund.
TEST THE FULL PAYMENT PATH BEFORE LAUNCH
Do not invite affiliates after only checking that the Stripe connection says active. Test the full attribution route.
RUN A CONTROLLED REFERRAL TEST
Open a private browser window with no ad-blocker extensions. Visit a test referral URL, such as one using ?via=install, and let the landing page fully load.
Then complete your approved Stripe test flow. Verify each record in both systems:
- The referral appears in Rewardful.
- The Stripe checkout includes the referral value or customer metadata.
- Stripe creates the expected customer and payment record.
- Rewardful assigns the conversion to the correct affiliate and campaign.
- The commission amount matches the campaign rule.
Do not create fake live purchases or cancelable subscriptions to test a production program. Use Stripe test mode where your flow supports it, or run a controlled internal payment with finance approval.
TEST THE EVENTS THAT COST MONEY
Run more than one test. A first payment proves only the first payment.
Test a renewal or recurring invoice. Test a failed payment. Test a partial or full refund. Test a cancellation before renewal. Also test a direct visit with no referral.
Stripe publishes a full list of event types. Your application may react to many of them. Your affiliate program only needs the events that affect attribution, earned commissions, reversals, and payouts.
If a test fails, stop the automatic approval process. Fix the checkout route, rerun the test, and keep the result with the release record.
RECONCILE COMMISSIONS AGAINST STRIPE
Your dashboard is the operating view. A spreadsheet, database, or finance system is the historical record.
Review a small sample every week. Compare the affiliate, Stripe customer, paid invoice, commission amount, and refund status.
Use a fixed commission record:
| Field | What to store |
|---|---|
| Customer and invoice | Stripe customer ID and paid invoice reference |
| Attribution | Affiliate, campaign, referral link, and channel marker |
| Commission | Original amount, status, and due date |
| Adjustments | Refund, cancellation, void, or manual correction |
| Review evidence | Date range, reviewer, and report export |
MEASURE CONFIRMED VALUE, NOT ACTIVITY
Clicks show attention. Attributed customers show that the checkout path worked. Paid invoices show billing activity. Due or paid commissions show the cost you can act on.
Track reversal rate and manual review time. A system that creates many commission records but requires hours of correction work is not working well.
Keep the last trusted export before each payout review. If a checkout release causes missing attribution or duplicate claims, pause automatic approvals and use manual review until the issue is fixed.
For a complicated migration, multi-product billing model, or internal reconciliation process, Book A Call to map the payment and affiliate workflow.
KEY TAKEAWAYS
- Connect Stripe in Rewardful, then create a campaign that matches your real commission rules.
- Pass referral data through Checkout, Payment Links, or Stripe customer metadata.
- Enable “Save Payment Details for Future Use” for Stripe Payment Links.
- Track recurring payments, refunds, and cancellations as separate billing outcomes.
- Test attribution, payment, renewal, refund, and cancellation paths before affiliates promote the offer.
- Preserve original commissions and add adjustment records when results change.
FINAL THOUGHTS
The strongest affiliate program is not the one with the most clicks. It is the one where every approved commission traces back to a valid Stripe customer and paid invoice.
Set the rules, protect referral data at checkout, and review exceptions before they become payout errors. Accurate attribution is what makes recurring affiliate commissions manageable.
FAQ
DOES REWARDFUL REQUIRE MANUAL STRIPE WEBHOOK SETUP?
Not for Rewardful’s standard Stripe connection. Rewardful describes the sync as automatic and does not require separate webhook configuration or event mapping for affiliate tracking.
Your application can still use Stripe webhooks for product access, billing notices, and internal systems. Keep that logic separate from Rewardful commission tracking.
CAN I USE REWARDFUL WITH STRIPE PAYMENT LINKS?
Yes. Enable Stripe’s “Save Payment Details for Future Use” setting on the Payment Link. Rewardful needs the Stripe Customer object for reliable referral attribution.
Also confirm that the Rewardful tracking script loads on the page where the visitor first arrives through the affiliate link.
WHAT HAPPENS TO COMMISSIONS WHEN A CUSTOMER CANCELS?
A cancellation usually stops future subscription billing. It does not automatically mean a previously paid invoice was refunded.
Rewardful states that it adjusts commissions for cancellations and other subscription changes. Check your campaign rules and retain the Stripe invoice history before you approve a payout.
DO REFUNDS REVERSE AFFILIATE COMMISSIONS?
Refunds can reduce or void the commission tied to the refunded payment. Record the original commission first, then add a separate negative adjustment for the refund.
Do not overwrite the original result. The original payment, refund, and commission adjustment should remain visible to finance and support.
