Rewardful Custom Affiliate Links for Stripe Checkout

A Stripe checkout URL can take payment without recording the affiliate who sent the buyer. That gap creates disputes, missed commissions, and campaign reports you can’t trust.

Rewardful custom affiliate links fix the attribution path when the link, browser cookie, and Stripe checkout flow all use the same referral data. Build the path before you give affiliates a URL.

Start by separating the links in your setup. They don’t do the same job.

Separate the four URLs before setup

Stripe doesn’t create affiliate links. Rewardful creates the referral identity, while Stripe collects the payment.

URL type	System	Main job
Affiliate link	Rewardful	Identifies the individual affiliate who referred a visitor
Campaign link	Rewardful	Applies the campaign’s cookie and commission rules
Stripe Payment Link	Stripe	Opens a reusable hosted payment page
Checkout Session URL	Stripe	Opens a hosted Checkout page for one session

A campaign link is the affiliate-facing tracking URL in Rewardful. The campaign controls the commission terms, cookie window, and eligible affiliates.

A Stripe Payment Link is a shareable checkout destination. It has no native affiliate field. A Checkout Session URL also isn’t an affiliate link. It is a payment URL created by your Stripe Checkout flow.

Campaign membership controls the commission

Set the campaign before you distribute any links. An affiliate’s campaign determines the commission rule behind their referral.

Use separate campaigns when partner terms differ. You might have one program for customer referrals, one for integration partners, and one for content affiliates. Rewardful lets campaigns use different commission structures and cookie windows, as covered in its guide to working with multiple campaigns.

Don’t move an affiliate between campaigns without checking the effect on existing terms and reporting.

Create Rewardful custom affiliate links for each destination

Create the campaign, connect Stripe, install the Rewardful tracking script, then add or approve the affiliate. Rewardful assigns the referral identity that the affiliate link uses.

The custom part is usually the destination page. You can send a partner’s audience to pricing, a feature page, a webinar page, or a product-specific landing page.

Use a tracked page you control

Choose a page where the Rewardful script loads. Then add the affiliate’s assigned token through the via query parameter.

For example, an affiliate might share:

https://www.example.com/pricing?via=alex

The same affiliate can use a different destination:

https://www.example.com/teams?via=alex

Keep the token from the Rewardful-generated referral link. Don’t type a new token based on an affiliate’s name. A small mismatch can send credit to nobody, or to the wrong partner.

If your destination URL already has parameters, add the referral token with &via=alex, not a second question mark.

Keep the destination and referral identity separate

A landing page change should not require a new affiliate record. Update the destination path, preserve the valid referral token, and test again in a private browser.

Don’t send partners a bare buy.stripe.com URL when your attribution depends on the first visit to your website. That visitor skips the page where Rewardful reads the referral token and writes its browser cookie.

Promotion codes can support affiliates who need a code for podcasts, live events, or offline mentions. Rewardful can assign codes to affiliates for promotion-code referral tracking. A code is useful backup attribution, not a reason to skip link testing.

Configure Stripe Payment Links without losing attribution

A Stripe Payment Link is a public URL for a hosted payment page. Create the link in Stripe for the right product or price, then use it behind a tracked page on your site.

For Rewardful’s documented Payment Links setup, enable “Save Payment Details for Future Use” on the Payment Link. Rewardful uses Stripe Customer objects to match the referral with later billing activity.

Use client_reference_id for the referral value

Stripe supports URL parameters on Payment Links. Its client_reference_id parameter helps reconcile a payment with a value from your system. It does not become an affiliate program by itself.

On the page that contains your Payment Link button, use Rewardful’s client-side approach to append the current Rewardful.referral value as client_reference_id. Rewardful documents this flow in its Stripe Payment Links method.

The resulting Payment Link follows this shape:

https://buy.stripe.com/your_payment_link?client_reference_id=<Rewardful referral value>

Your page code supplies the live referral value. Don’t hard-code alex, a campaign name, or one static ID into the Stripe link. Every affiliate would then share the same reference.

Keep UTM reporting separate from commission attribution

Add UTM parameters if you need channel reporting in Stripe or analytics tools. For example, utm_source, utm_medium, and utm_campaign can show which newsletter or partner placement sent traffic.

UTMs describe the source. Rewardful referral data identifies the partner eligible for commission. Keep both when you need both reports.

Handle custom Stripe Checkout URLs in your app

A custom Checkout integration follows the same principle. The buyer first arrives through a Rewardful referral link. Rewardful stores the referral in the browser. Your checkout flow passes that referral value into the Stripe session flow.

Don’t replace this with a raw query parameter copied from the incoming URL. The Rewardful script and referral value are the source of truth after the landing page loads.

Pass the referral through your Checkout implementation

Install the Rewardful script on the marketing and signup pages that receive affiliate traffic. When your app creates or redirects to Stripe Checkout, follow Rewardful’s custom Stripe integration method.

The important sequence is simple:

1. The affiliate sends a visitor to your tracked site URL.
2. Rewardful detects the referral and stores the browser attribution.
3. Your Checkout flow uses the current Rewardful referral value.
4. Stripe creates the payment or subscription record.
5. Rewardful matches the billing activity to the referral.

Keep test and live Stripe environments separate. A test subscription should not appear as a real affiliate payout obligation.

Don’t confuse a success URL with tracking

A success_url sends the buyer to your confirmation page after Checkout. It is useful for account activation, order confirmation, and internal reconciliation.

It does not capture the original affiliate click. Stripe’s custom success page guidance explains how to pass the Checkout Session ID back to your site when you need post-payment verification.

Treat the success page as a confirmation step. Capture referral attribution before Checkout starts.

Test attribution before you launch

Test the full buyer path. A link that lands on the right page can still fail to create a commission.

Use a private or incognito browser window. Existing cookies can hide a broken setup by crediting an old referral.

Run Rewardful’s installation check

Open your tracked page with ?via=install in a private browser. Let the page load fully, then return to Rewardful and refresh the setup check.

This confirms that the tracking script can see the referral visit. It doesn’t confirm that Stripe received the right reference or that a commission will appear.

A completed click proves navigation. It does not prove that the Stripe customer, subscription, and affiliate commission are connected.

Test the actual payment result

Run a controlled test for every important route, including pricing pages, product pages, and campaign-specific landing pages.

Check these results after the test:

• The private browser visit appears as a referral for the intended affiliate.
• The Payment Link or Checkout flow receives the current referral value.
• The Stripe payment or subscription is tied to the expected customer and product.
• Rewardful records the referral and applies the intended commission rule.
• A second visit without the affiliate URL does not overwrite attribution unexpectedly.

Record the test date, affiliate token, campaign, destination URL, browser, payment path, and outcome. That record makes later debugging faster.

Keep cookies, redirects, and recurring rules aligned

Rewardful’s default cookie window is 60 days. You can change it under the campaign’s Cookie window setting.

Choose the period based on your normal sales cycle. A low-cost self-serve product may need a shorter window. A B2B SaaS deal with demos and approvals may need longer.

Configure cross-domain journeys

Rewardful custom affiliate links only work when the tracking flow can follow the buyer through the domains you control.

A common route looks like this:

www.example.com/pricing?via=alex -> app.example.com/signup -> Stripe Checkout

Install the Rewardful script where needed and configure cross-domain tracking with its data-domains setting. Add domains you own. Don’t try to add Stripe’s hosted checkout domain.

A redirect must preserve the referral parameter until the first tracked page loads. If a redirect strips via=alex before Rewardful sees it, no browser cookie is created.

Browser privacy settings, blocked scripts, private windows, and cross-device purchases can also break cookie-based attribution. Test the routes your real buyers use.

Set the recurring commission limit before payouts

For subscriptions, decide whether affiliates earn on all invoices or only a defined number of invoices. Rewardful supports both commission models at the campaign level.

Match that setting to your partner agreement. A 20% recurring commission for 12 invoices is not the same offer as 20% for the life of the customer.

Also test trials, coupons, upgrades, cancellations, refunds, and failed payments. These events can change what your team considers a qualified commission.

Operate the link system like production infrastructure

Don’t judge this setup by affiliate clicks alone. Measure accepted attribution, meaning paid customers and commissions your team can verify.

Keep a route register with the campaign, affiliate token, approved destination, Stripe payment path, last test date, and owner. Update the register before changing redirects, domains, checkout buttons, or pricing pages.

Pilot a small approved set of routes

Start with the highest-value affiliate paths. Include one standard Payment Link, one custom Checkout route, one cross-domain signup, and one recurring plan.

Keep the last trusted URL and checkout configuration. If a release breaks attribution, you need a known-good version to restore.

Track failed tests, missing referrals, duplicate attribution, review time, and corrected links. A setup that creates more clicks but more commission disputes has failed its business test.

Measure confirmed outcomes

Review the ratio of affiliate clicks to attributed checkouts, then compare attributed checkouts with approved commissions. Large gaps usually point to browser, redirect, cookie, or checkout handoff issues.

If your flow spans several domains, products, or partner tiers, Book A Call to map the attribution path before affiliates promote it.

Final checks before affiliates receive links

Rewardful custom affiliate links work when every system has one clear job. Rewardful identifies the affiliate and applies campaign rules. Your website captures the referral. Stripe processes the payment.

Test the full path in a clean browser, confirm the Stripe handoff, and verify the commission after checkout. A verified attribution record is worth more than a long list of links that only look correct.