Insightful tripled their affiliate revenue after switching. Free white-glove migration; your affiliates keep their links.

Migrate for Free
Works with Paddle via the Payments API

Affiliate program software for Paddle-billed SaaS.

Reditus has no native Paddle integration, and you do not need one. Forward your payment events to the Reditus Payments API (about four hours of developer time) and run the same program Stripe users get: real-time tracking, automated recurring commissions, refund handling, and a 26,000+ B2B SaaS affiliate network.

14-day free trial · No credit card required

Best if you're already running an affiliate program

How the setup works with Paddle

Honest estimate: about 4 hours of developer time

1

Install the tracking script

One script in your site header (Google Tag Manager works). It places the attribution cookie when someone clicks an affiliate link. No cookie consent banner needed: it is an attribution-only cookie, no PII.

2

Add the sign-up snippet

One line at your registration step registers the referral, using the customer email or a unique ID.

3

Forward payments via the API

Send Paddle payment events to the Reditus Payments API from your backend. Reditus does the matching: if the payment belongs to a referral, a commission is generated; everything else is ignored. Test safely first on the sandbox at app.getreditus.net.

How Reditus works with Paddle, honestly

We will not pretend there is a one-click Paddle integration; there is not. What there is: a Payments API that customers use in production today to run affiliate programs on processors other than Stripe. The simplest path is forwarding all payments to Reditus with the customer email or a unique ID attached; Reditus only acts when the payment belongs to a known referral.

Want to share as little data as possible? Use the minimal-data mode: query the API for which referrals exist, then send payment data only for those customers. You can operate entirely on unique identifiers without ever sharing your customer database. For a merchant-of-record setup like Paddle, that data-minimal, GDPR-friendly design tends to be exactly what your DPA reviewer wants to hear.

Refunds are covered too: send refund data to the refund endpoint and the full commission is rejected automatically, no manual step. One honest limitation to know upfront: coupon-code tracking is Stripe-only, so on Paddle your affiliates promote with tracked links.

The exact endpoints live in the developer documentation, and the step-by-step walkthrough is in our payment-processor setup guide.

Related reading: what a merchant of record changes for your affiliate program, affiliate tracking without sharing your customer data, and switching payment processors without breaking your program.

Everything your Paddle affiliate program needs

Real-time revenue tracking

Sales and payments appear the moment your payment data reaches Reditus, so commissions are always calculated on real revenue.

Recurring commissions, automated

Set the percentage and the commission length once. Reditus calculates every recurring commission from your subscription payments.

Refunds handled automatically

When a payment is refunded, the related commission is rejected automatically before payout. Nobody gets paid for refunded revenue.

GDPR-friendly by design

The API path works with unique identifiers instead of full customer data. Some customers choose it over the native Stripe connection for exactly that reason.

Fraud detection built in

Self-referral detection and automatic rejection of referrals generated through paid ads on your brand terms, on every plan.

A network of 26,000+ B2B SaaS affiliates

Reditus is more than tracking: AI discovery finds affiliates who already promote products like yours, and the network brings them to you.

Works with your billing stack

Stripe connects natively. Paddle, Chargebee, PayPal, and any other processor that can send payment data work through the Reditus Payments API.

Stripe · native connectionPaddle · via the Payments APIChargebee · via the Payments APIPayPal · via the Payments API

Frequently asked questions

Does Reditus integrate natively with Paddle?

No, and we say that upfront. Reditus works with Paddle through its Payments API: your backend forwards payment events, and Reditus handles matching, commissions, refunds, and payouts. Customers run programs this way in production today.

How long does the API setup take?

About four hours of developer time is an honest estimate for forwarding all payments, depending on your setup. A sandbox environment at app.getreditus.net lets you test the full flow before going live.

Do we have to send Reditus all our customer data?

No. The simplest path forwards all payments with an email or unique ID, but you can also query the API for which referrals exist and send payment data only for those, working purely with unique identifiers.

What happens with refunds?

Send refund data to the refund endpoint and the full commission is rejected automatically before payout. Partial refunds are not supported: any refund rejects the entire commission, which also protects you from buy-then-refund fraud.

Can affiliates use coupon codes on Paddle?

No. Coupon-code tracking is exclusive to the Stripe connection. On Paddle, affiliates promote with tracked links, which cover the full attribution flow.

Can we migrate an existing affiliate program while on Paddle?

Yes. Migrations are free and white-glove, your affiliates keep their existing links, and the payment side runs through the API from day one.

Launch your Paddle affiliate program

  • 14-day free trial
  • No credit card required
  • Honest estimate: about 4 hours of developer time
Paddle Affiliate Program Software | Reditus