Billing integrations

Track affiliate revenue around the billing stack your SaaS actually uses.

RefCampaign is Stripe-native today. This hub documents how Paddle and Chargebee teams can model affiliate tracking, revenue attribution and payout controls before a native connector is promoted as generally available.

Start with the billing system that owns your revenue events

Each page shows the events to capture, the attribution risks to avoid and how the approach differs from RefCampaign's Stripe-native path.

Implementation notes

Start with the billing system that owns your revenue events

Each page shows the events to capture, the attribution risks to avoid and how the approach differs from RefCampaign's Stripe-native path.

Merchant of Record fit

Paddle affiliate tracking

Use a MoR-friendly event model for SaaS teams that need affiliate tracking across checkout, subscription and refund signals.

Explore Paddle tracking
Subscription billing fit

Chargebee affiliate programs

Plan recurring commission attribution around subscription lifecycle events, plan changes and cancellation signals.

Explore Chargebee tracking

When Stripe owns billing, use the native path.

Stripe remains the most complete RefCampaign integration path today: server-side conversions, refund clawback, recurring commission windows and Connect payout workflows are documented in the Stripe-native cluster.

Read the Stripe-native page

Evaluate the approach, not only the logo grid.

For affiliate tracking, the hard part is not naming the billing provider. It is deciding which revenue events count, how refunds reverse commission, and how duplicate webhooks stay idempotent.

RefCampaign vs Rewardful