Stripe, Paddle, Lemon Squeezy, Polar, Chargebee and Recurly walk into a webhook.
AffiliateTracking has affiliate tracking integrations for 6 billing tools: Stripe, Paddle, Lemon Squeezy, Polar, Chargebee and Recurly. Your billing tool reports each sale, renewal and refund. AffiliateTracking works out who sent it and what they're owed.
StripeA script tag and one key
PaddleOne line at checkout
PolarA script tag
Lemon SqueezyA script tag
ChargebeeOne custom field
RecurlyOne custom fieldWhat each billing tool needs from you. The setup for each is below.
Billing tools
Each one gets its own setup guide, with every event it sends and what AffiliateTracking does with it.
One script tag on your site and one restricted key. Payment Links, the Pricing Table and the Buy Button need nothing else.
Your checkout passes the affiliate's token to Paddle in one line. After that, Paddle's webhook does the rest.
The script adds the token to your checkout links as custom data. Orders, renewals and refunds all report back.
The script adds the token to your Polar checkout links as reference_id. Add one webhook and paste its secret.
Save the token in one customer custom field at checkout. Every paid invoice after that credits the same affiliate.
Chargebee setupSave the token in one account custom field when you create the account. Renewals, refunds and voids follow.
Recurly setupThe same questions for each billing tool, answered the same way.
| Billing tool | How the first sale finds its affiliate | Renewals | Refunds | Connect on cloud | Webhook address |
|---|---|---|---|---|---|
| Stripe | The script, or your Checkout Session | Yes | Yes | One restricted key | /webhooks/stripe |
| Paddle | custom_data.token at checkout | Yes | Yes | One API key | /webhooks/paddle |
| Lemon Squeezy | checkout[custom][token], added by the script | Yes | Yes | One API key | /webhooks/lemonsqueezy |
| Polar | reference_id, added by the script | Yes | Yes | Webhook and its secret | /webhooks/polar |
| Chargebee | The cf_aff_token customer field | Yes | Yes | Webhook and a password | /webhooks/chargebee |
| Recurly | The aff_token account field | Yes | Yes | Webhook and a password | /webhooks/recurly |
Whichever tool sends it, an event takes the same path before any affiliate earns a cent.
A signature or password check runs before anything touches the database. A forged event goes nowhere.
Billing tools resend events. The same event arriving twice changes nothing the second time.
Rules like self-referral, coupon hijack and bot traffic hold a sale with the evidence, before the payout run.
Each sale is a journal whose lines sum to zero, so balances can't drift.
A refund takes back the same share of the commission. Already paid? It comes off the next payout.
The first affiliate to bring a customer keeps them, so every renewal after credits the same person.
Other ways in and out, plus what isn't on the list.
Each paid sale becomes a journal in the partner's ledger, in the sale's own currency. A refund adds a second journal that takes the share back. Nobody edits a journal after the fact.
Two billing tools at once? They write to the same ledger, so a partner has one balance per currency. How the ledger keeps every cent.
Stripe, Paddle, Lemon Squeezy, Polar, Chargebee and Recurly, on cloud and on self-host. Other checkouts, like Shopify, can't report sales to it yet.
Not for Stripe Payment Links, the Pricing Table, the Buy Button, Lemon Squeezy links or Polar links. The script handles those. Paddle, Chargebee and Recurly need one line or one field in your checkout code. The rest happens in settings.
No. Every billing integration is on every cloud plan and in self-host.
In your workspace settings, under Connect your billing. Stripe, Paddle and Lemon Squeezy connect with one key, and AffiliateTracking adds the webhook for you. Polar, Chargebee and Recurly show their webhook address and a field for the secret or password.
Yes. Each one has its own webhook address, and they all write to the same ledger.
Self-host for free: the code is open source. Or let us run it for you.
