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.
Paddle affiliate tracking
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
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.
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.
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.
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.
Yes, if checkout, subscription, refund and cancellation events are mapped into a clean server-side attribution flow with idempotent transaction IDs.