Chargebee affiliate program software, gateway-agnostic and refund-aware.
Chargebee is subscription billing that runs on top of the payment gateway you already use, and Rekomi supports it natively: paste your site name and a Read-Only API key, add one webhook in Chargebee with the credentials Rekomi generates, and from then on payments, subscription renewals, refunds, and Chargeback Management chargebacks credit and debit the right affiliate automatically, with no relay code to write or maintain.
Connect the site, stamp the referral, let the webhooks flow.
Enter your Chargebee site name and a Read-Only API key; Rekomi validates the pair live against your site. Then add one webhook in Chargebee with the URL and Basic Authentication credentials Rekomi generates for you: API version V2, card data excluded, subscribed to the payment, subscription, and credit-note events Rekomi uses.
Chargebee hosts the checkout, so the referral travels on the subscription. Install the head script, then pass window.Rekomi.getReferral() as meta_data.rekomi_ref on API-created subscriptions, or stamp a cf_rekomi_ref custom field onto hosted-page URLs and the drop-in script with a copy-paste snippet.
The first successful payment books the conversion, and signups tie the customer to the affiliate at $0 before any money moves. Every renewal accrues recurring commission, and refunds and Chargeback Management chargebacks claw back proportionally in the same audit trail.
Unsigned webhooks, authenticated anyway.
Chargebee does not support webhook signing, and the honest response is to engineer around that rather than gloss over it. Rekomi generates Basic Authentication credentials and authenticates every delivery before anything is processed; the per-workspace URL is unguessable, V1 payloads are rejected, and retries are de-duplicated by event id so Chargebee's two-day redelivery window never double counts a sale. The Read-Only API key is health-checked continuously, and because Chargebee keys never expire, a failed check always means something real: you get an email the moment the connection needs attention.
Chargebee affiliate tracking, built for real subscription billing.
Gateway-agnostic by design
Chargebee sits on top of the payment gateway you already run, and Rekomi listens to Chargebee, the billing source of truth, not the gateway underneath. Whichever gateway processes the card, the same webhooks report the payment, and your payment routing does not change.
Honestly secured webhooks
Chargebee does not support webhook signing, so this page says so. Rekomi mints Basic Authentication credentials, authenticates every delivery before processing, rejects V1 payloads, and stores the credential and your Read-Only key encrypted at rest.
Renewals on autopilot
Every successful renewal payment records a recurring conversion, and the referral set at signup stays on the subscription, so revshare keeps accruing for the life of the customer with no further work.
Chargeback-aware clawbacks
Refunds, full or partial, claw commission back proportionally, and chargebacks handled through Chargebee's Chargeback Management feature arrive through the same pipe and claw back too, all in the same audit trail as the original conversion.
No key-expiry surprises
Chargebee API keys never expire, so the connection has no built-in time bomb. Rekomi still health-checks the key continuously; if it is ever deleted or disabled you get an email, and reconnecting preserves your history.
Part of a bigger stack
Stripe, Paddle, Braintree, and more are native alongside Chargebee, and any other gateway attributes through the HMAC-signed S2S API.
All integrationsFlat plans plus 3% of payouts. No revenue cut.
For solo founders running a focused campaign.
For SaaS scaling beyond one campaign.
For mature SaaS with serious affiliate ambitions.
14-day free trial on every plan · 3% of affiliate payouts (2.5% on Enterprise), payouts and tax handled · Full pricing
Common Chargebee questions.
Is the Chargebee integration native?
Yes. You paste your Chargebee site name and a Read-Only API key, then add one webhook in Chargebee using the URL and Basic Authentication credentials Rekomi generates for you. Payments, subscription renewals, signups, refunds, and Chargeback Management chargebacks are all recorded automatically, with no relay code to write or maintain. Rekomi also health-checks the connection and emails you if the key ever stops validating.
Which payment gateways does it work with?
All of them, because Rekomi listens to Chargebee, not to the gateway. Chargebee sits on top of the payment gateways you already run (Stripe, Braintree, PayPal, and the rest), and its webhooks report every payment the same way regardless of which gateway processed the card. You keep your gateway setup exactly as it is; nothing about your payment routing changes.
How are the webhooks secured if Chargebee does not sign them?
Plainly: Chargebee does not support webhook signing, so Rekomi does not pretend otherwise. Rekomi generates Basic Authentication credentials for you, and every delivery is authenticated against them before anything is processed; deliveries that fail the check are rejected. The credentials and your Read-Only API key are stored encrypted at rest and never returned by the API, the per-workspace URL is unguessable, everything travels over HTTPS, and Rekomi accepts V2 payloads only.
Most affiliate platforms I looked at skip Chargebee. Which support it?
Chargebee is reasonably well covered: FirstPromoter, Tolt, PartnerStack, and Tapfiliate all ship Chargebee integrations. Rewardful does not; it supports Stripe and Paddle. If you are comparing affiliate software for Chargebee and came from a platform whose list of Chargebee integrations came up empty, that is the gap Rekomi covers: native Chargebee support alongside Stripe, Paddle, Braintree, and more, with recurring commissions, refund-aware clawbacks, and done-for-you payouts.
How do affiliates get credited when Chargebee hosts the checkout?
The referral travels on the subscription. The Rekomi head script captures the affiliate click in a first-party cookie; API-created subscriptions pass window.Rekomi.getReferral() as meta_data.rekomi_ref, and hosted pages or the drop-in script use a cf_rekomi_ref custom field stamped onto checkout URLs with a copy-paste snippet. Rekomi reads the referral from the subscription first, then falls back to the customer, in both renderings.
Are subscription renewals, refunds, and chargebacks handled?
Yes. Every successful renewal payment records a recurring conversion, so revshare keeps accruing for the life of the subscription, and signups are recorded as zero-value events that tie the customer to the affiliate before the first payment. Refunds, full or partial, claw commission back proportionally in the same audit trail, and chargebacks handled through Chargebee's Chargeback Management feature arrive the same way and claw back too. One honest caveat: disputes settled directly at your payment gateway, outside Chargebee, do not generate Chargebee events, so those you adjust manually.
Can I run Chargebee alongside another billing connection?
No; Rekomi enforces one conversion source of truth per workspace so the same sale is never recorded twice. Pick one rail for Chargebee sales and keep it; if you genuinely sell on two platforms, run them as separate workspaces.
Selling somewhere else too? Also covered.
Ten minutes to first click.
Connect your Chargebee site with a Read-Only key and one webhook, and payments start crediting affiliates today. 14-day free trial, no card.
- 14-day free trial
- Cancel anytime, $0 charged