Chargebee, Recurly & Paddle Affiliate Tracking (2026)

If your affiliate platform only knows about the first sale, your recurring-commission program is running blind. In SaaS, the commission-relevant truth lives in the billing system, not the checkout page: the customer upgrades, downgrades, pauses, churns, fails a payment and recovers through dunning, or disputes a charge — and every one of those events should move a commission accrual. The job of integrating affiliate tracking with a subscription-billing platform is to make that billing truth flow into your commission engine in real time, so partners are paid on MRR that actually exists, not on a conversion snapshot from ninety days ago.

This guide covers how to wire affiliate tracking to the major subscription-billing platforms — Chargebee, Recurly, Paddle, and Stripe Billing — using webhooks and postbacks. We'll map which billing events matter for commission, how to handle upgrades and downgrades, and how churn and chargeback events should trigger automatic clawback. It builds on the program mechanics in our recurring-commission program design guide, which defines the commission rules these integrations enforce.

Why billing events are the source of truth

A conversion pixel fires once, at signup. But SaaS revenue is a stream, and commission on that revenue has to follow the stream. The billing platform is the only system that knows the true state of every subscription — current MRR, plan, proration, payment status, and lifecycle stage. Each of these platforms emits that knowledge as webhook events: Chargebee's event notifications, Recurly's webhooks, Paddle's events, and Stripe's webhooks. The integration pattern is consistent: listen for the events, map each to a commission action, and post the result into your affiliate platform.

The critical design decision is what counts as the commissionable event. Paying on subscription_created the moment a trial converts is the simplest model, but it pays before the first invoice clears and exposes you to dispute risk. Paying on invoice.paid — the first successful charge — is safer and the most common choice, because money has actually moved. For RevShare programs, every recurring invoice.paid is itself a commission event, which is exactly why a webhook integration (rather than a one-time pixel) is mandatory: there's no other way to learn that month two's charge succeeded.

The carry-the-click-ID problem

The hardest part of any billing integration isn't the webhook — it's preserving the affiliate identity from click to recurring invoice. When the affiliate platform issues a click ID, that ID must survive the trip through signup and be stored against the customer record in the billing platform, typically in a custom field or metadata attribute. Chargebee, Recurly, Paddle, and Stripe all support custom metadata on customers and subscriptions; the integration writes the click ID there at subscription creation, and every subsequent webhook carries that metadata so the postback can attribute the recurring charge to the right partner.

Mapping billing events to commission actions

Each lifecycle event maps to a specific commission action. A first paid invoice triggers the initial CPA or first RevShare accrual. A recurring paid invoice triggers the next RevShare installment. An upgrade increases the commissionable MRR going forward; a downgrade decreases it. A payment failure should pause accrual until dunning recovers the charge. A cancellation stops future accruals, and a refund or dispute should trigger clawback of commission already paid on the reversed amount. Getting this mapping right is what makes the difference between commissions that track real MRR and commissions that drift away from reality within a quarter.

Handling upgrades, downgrades, and proration

Plan changes are where naive integrations leak money in both directions. When a customer upgrades mid-cycle, the billing platform issues a prorated charge for the delta; your commission should accrue on that actual charged amount, not on the full new plan price. When they downgrade, future RevShare should drop to the new MRR, but you generally shouldn't claw back installments already correctly paid on the higher plan. The subscription lifecycle each platform documents — Chargebee, Recurly, and the others — exposes these transitions as discrete events, so a well-built integration accrues on the prorated reality rather than guessing from plan list-price.

Churn, dunning, and automatic clawback

Clawback is the reason billing integration is non-negotiable rather than nice-to-have. When a charge is refunded, disputed, or charged back — and Stripe disputes can arrive up to 120 days after the charge — the corresponding commission must reverse automatically. Dunning adds nuance: a failed payment isn't necessarily lost revenue, because the billing platform will retry. The correct behavior is to pause accrual on payment_failed and resume on successful recovery, rather than immediately clawing back a charge that dunning will likely recover within days. Wiring these events into the commission-management layer lets reversals and resumes happen automatically, before the next payout run releases money you'd otherwise have to recover by hand.

Integration comparison: Chargebee, Recurly, Paddle, Stripe Billing

All four platforms support the webhook-plus-metadata pattern, but they differ in ways that affect integration design. Paddle acts as a Merchant of Record, meaning it handles tax and chargebacks on your behalf — which changes who owns the dispute event and how clawback is triggered. Stripe Billing gives you the most granular event catalog and raw control, but you own tax and dispute handling yourself. Chargebee and Recurly sit between, offering rich subscription-management abstractions with strong lifecycle events. The table below summarizes the integration-relevant differences.

• Propagate the affiliate click ID from click into billing-platform metadata at subscription creation.
• Pay first commission on the first successful invoice (invoice.paid), not on pre-payment signup events.
• Treat every recurring invoice.paid as a RevShare accrual event for MRR-accurate payout.
• Accrue upgrades and downgrades on the prorated charged amount, not on plan list-price.
• Pause accrual on payment failure and resume on dunning recovery instead of immediate clawback.
• Trigger automatic clawback on refunds, disputes, and chargebacks before the next payout run clears.
• Verify webhook signatures and process events idempotently to prevent injected or duplicated commissions.

Integrating affiliate tracking with your billing platform is what turns a recurring-commission program from a promise into accurate accounting. When Chargebee, Recurly, Paddle, or Stripe Billing events flow into your commission engine in real time, partners are paid on the MRR that actually exists — through every upgrade, downgrade, churn, and chargeback. Track360 ingests these webhooks natively and ties them to its tracking and commission layers, so you don't have to build and maintain the reconciliation plumbing yourself.