Browse documentation

Your first affiliate program

Create a product, choose commission rules, add an affiliate and test either Stripe automatic or API/SDK advanced mode.

Updated August 3, 2026

Create one AffiHQ product for each product you sell, even when several products share the same Stripe account. Each product has its own attribution rules, commission rules, currency and integration mode.

Create the product

Open Products, add the product’s public name and choose its billing model. AffiHQ supports subscriptions and one-time purchases.

Set the default attribution window, commission reward, commission duration and validation delay. These defaults can later be overridden for a specific affiliate without changing commissions that were created under an earlier rule set.

Choose the commercial rules

A reward can be a percentage of the commissionable amount or a fixed amount in the payment currency for each eligible payment. Subscription rewards can apply to the first payment, a fixed period or every eligible payment while the customer remains eligible.

Customer discounts are separate from affiliate rewards. A customer might receive a discount on the first few invoices while the affiliate earns a different rate for a defined period.

Add the affiliate and link

Open Affiliates, add the partner’s name and email address, then attach them to the product. Create a campaign and issue a link or memorable code. The generated /r/ link is the entry point you should use for the test.

Do not test by purchasing through a merchant or affiliate identity that should not receive credit. AffiHQ does not credit a self-attribution.

Choose the integration

If Stripe is the payment source, choose Stripe automatic in the product editor, select Connect Stripe, authorize the Stripe Standard account that owns the Payment Link, choose one compatible link and select Use this Payment Link. The link must be an active buy.stripe.com Payment Link with exactly one fixed-price line, quantity 1, a positive amount and one currency. It must be one-time or a monthly/annual subscription, and it must use the same Test or Live mode as the deployment.

Stripe automatic does not require AffiHQ API or SDK credentials, and your application does not forward Stripe webhooks. For custom Checkout, non-Stripe billing, pre-Checkout attribution, custom discounts or trials, onboarding or non-financial events, choose API/SDK advanced and follow the integration overview.

Run a controlled test

Use a fresh affiliate /r/ link, a new test customer identity and a Payment Link from the same Stripe Test or Live mode as the deployment. Confirm that the click reaches the intended product, the Payment Link has the expected amount/currency/cadence and the customer is attributed to the intended affiliate.

For Stripe automatic, verify that an immediate successful one-time Checkout creates one payment and one commission. For a subscription, verify the attribution at Checkout and the recurring payment after the test invoice is paid. For API/SDK advanced, verify the server attribution and the verified payment event instead.

Review the commission in AffiHQ, then repeat the test only with a new customer and a new click. Do not mix a live customer or live Payment Link into a test run.

Before you launch

Check the product’s Stripe state is Connected and Ready when using Stripe automatic. If the chooser shows no compatible links, correct the Payment Link in Stripe before sending traffic. If native state later becomes unavailable, AffiHQ safely falls back to the product’s historical destination with affihq_ref; that fallback requires the API/SDK flow to complete attribution and payment reporting.

Read Products and rules, Stripe automatic payments and Commissions and payouts before launch.