Back to integrations

Paddle affiliate tracking

Build a Paddle affiliate program around MoR revenue events, not cookie guesses.

Paddle is a strong billing fit for EU SaaS teams. RefCampaign does not yet expose a native Paddle connector as generally available, so this page defines the event model to use when you evaluate or plan the integration.

Implementation notes

1

What to capture from Paddle

Capture the customer identity, product or price, transaction amount, currency, subscription status and refund outcome. The affiliate click should be resolved server-side before revenue is credited.

2

How it differs from Stripe-native tracking

Stripe can be consumed directly by RefCampaign today. Paddle requires an explicit mapping layer so the same attribution and clawback rules can be applied without pretending the connector is already native.

3

Where to be strict

Make transaction IDs idempotent, keep test-mode events out of payout calculations and require refund events to update commission state before the next payout cycle.

Common questions

Does RefCampaign have a native Paddle connector today?

Not as a generally available product connector. The Stripe-native path is the primary integration today; Paddle support should be evaluated through a mapped event model first.

Can Paddle still work for affiliate tracking?

Yes, if checkout, subscription, refund and cancellation events are mapped into a clean server-side attribution flow with idempotent transaction IDs.