How should affiliates be credited when a customer buys multiple subscriptions?
Short answer: Keep attribution at the customer or account level, then evaluate each paid subscription transaction under a written scope rule. A second subscription does not automatically create a second customer acquisition. Some programs pay on all eligible products purchased by the referred account; others pay only on the first product or only for a fixed commission duration. Both are legitimate commercial choices when clearly disclosed.
For example, an affiliate introduces a startup to a project management SaaS. The startup first buys a $30 monthly plan, then adds a separate $80 subscription for another department. The tracking system must know whether the second purchase belongs to the same account and whether the affiliate's contract covers it. A click cookie alone cannot answer either question.
Model customer, account, subscription and invoice separately
At minimum, keep four distinct identifiers: your internal account ID, billing customer ID, subscription ID and invoice or transaction ID. A single billing customer can have multiple subscription objects; a company may also have several billing customers for different subsidiaries. Avoid joining on email address alone because staff change addresses and multiple people can buy for one organization.
| Identifier | Purpose | Typical failure if omitted |
|---|---|---|
| Partner/referral key | Original qualified source | Partner attribution disappears on upgrade |
| Internal account key | Business identity across billing changes | Same company treated as multiple acquisitions |
| Billing customer ID | Payment provider mapping | Invoice cannot be linked to the referred account |
| Subscription ID | Plan-level eligibility and duration | New subscription confused with renewal |
| Invoice or line ID | Paid revenue and idempotency | Duplicate commissions on webhook retries |
Choose one of four explicit attribution policies
- First qualifying subscription only: pay the first eligible purchase and no new acquisition reward for add-ons.
- Account-wide recurring: reward all eligible paid subscriptions owned by the referred account during the contractual term.
- Product-scoped: reward only specified products or price IDs, even if the account later buys other products.
- New product bounty: allow a distinct expansion reward for a second eligible product, but not another new-customer bounty.
Each model has a different cost profile. Account-wide recurring rewards are attractive to partners but can grow with expansion revenue. Product-scoped programs are easier to budget but need careful product catalog mapping. A new-product bounty needs anti-abuse rules to stop cancellation and repurchase from generating repeated bonuses.
Do not confuse a subscription change with a second subscription
Stripe's subscription webhook documentation includes customer.subscription.updated for plan changes and invoice.paid for paid invoices. A price upgrade on an existing subscription is not necessarily a new subscription. Stripe also supports multiple items on a subscription, as described in its Subscription Items API. Determine whether the change created a new subscription object, a new item or simply a prorated invoice.
For Paddle Billing, inspect the subscription and transaction identifiers used by the actual integration. An add-on, quantity change or separate subscription may produce different transaction structures. Do not assume Stripe and Paddle use identical object models or event names. Our Stripe plan-change guide covers the upgrade case in more detail.
Worked example: one account, two products and a refund
Suppose Partner A referred Account 500. In month one, the account pays $50 for Product Alpha. In month two, it pays $50 for Alpha and $120 for Product Beta. Assume a hypothetical 20% account-wide commission on collected eligible subscription revenue. Month one creates $10 in candidate rewards; month two creates $34, for a total of $44 before holds and adjustments.
Under a first-subscription-only policy, the Beta charge is excluded. Month two would create $10 instead, producing $20 across both months. Under a first-purchase-only bounty, month two might produce no reward at all. This difference is contractual, not a vendor tracking default.
If Beta is refunded in month two, an account-wide policy would reverse the $24 Beta-related candidate reward. The ledger must link that adjustment to the Beta invoice rather than erasing Alpha's valid commission. See our commission clawback workflow.
Handle a second affiliate and sales-assisted expansion
Consider Partner B sending a new link just before the existing customer buys Beta. Should B earn the expansion reward, should A retain account ownership, or should the sales team review the deal? The answer depends on your published account-lock, attribution-window and expansion-credit policy. Do not silently reassign all historic recurring commissions because of a later click.
For high-value B2B deals, record the opportunity owner and partner involvement in the CRM. Distinguish sourced acquisition from influenced expansion, then apply an agreed conflict resolution procedure. Our partner-sourced versus influenced revenue guide explains the terminology.
Implementation and QA checklist
- Persist the first qualified referral and its timestamp to a stable internal account ID.
- Map every billing customer and subscription to that account, including merged or migrated accounts.
- Store effective rule version, eligible product IDs, attribution duration and any customer-level lock.
- Compute one reward per eligible invoice line with a unique idempotency key.
- Test a second subscription, a new item on the first subscription and a pure plan upgrade separately.
- Test two affiliates referring the same account before and after the first purchase.
- Test canceled and restarted subscriptions without treating a returning customer as automatically new.
- Verify refunds and credit notes adjust only the matching commission records.
- Export a finance report showing customer, subscription, invoice, partner and rule version.
Frequently asked questions
Can one affiliate earn on two SaaS subscriptions?
Yes, if the contract covers both and the corresponding charges qualify. Billing support alone does not establish contractual eligibility.
Does a second subscription reset the affiliate cookie?
It should not need to. After a verified conversion, stable customer attribution is usually more reliable than repeated browser cookies.
Should an annual plan and a monthly add-on be handled together?
They may share an account attribution, but use their actual paid invoices and potentially different rates, durations and refund policies.
Sources and editorial disclosure
Sources checked 2 November 2026: Stripe subscription events and Stripe Subscription Items API. Examples and commission percentages are hypothetical. SaaSAlways has not independently tested a vendor's handling of multiple subscriptions; confirm your billing and affiliate system behavior before deploying rules.
For seat-based subscription expansion and proration rules, review our seat-based SaaS affiliate commission guide before adding a new customer bounty to every seat change.