Paddle affiliate program software for Merchant of Record billing.
Paddle is your Merchant of Record, so the checkout, the invoice, and the refund all happen on Paddle's side of the fence. Rekomi plugs in natively: point a Paddle notification destination at your unique Rekomi URL, paste the signing secret, and every completed transaction carrying your affiliate's rekomi_ref is verified and credited. No backend relay to build.
A webhook destination, a signing secret, and one customData key.
Copy your workspace's unique webhook URL from Rekomi, create a Paddle notification destination with it, enable the transaction, subscription, and adjustment events, then paste the destination's signing secret back into Rekomi.
Install the head script so the click is captured before the buyer opens Paddle Checkout, then attach window.Rekomi.getReferral() to customData under rekomi_ref. Paddle stores it on the transaction and repeats it on every webhook.
transaction.completed books the sale to the right affiliate; adjustment.created and adjustment.updated reverse commission proportionally on refunds and chargebacks. Amounts arrive as integer minor units and are read as-is.
The referral rides inside the transaction itself.
A Merchant of Record hosts the checkout on its own domain, which is where most affiliate tools lose the thread. Rekomi threads the referral through Paddle's own customData field, so it survives the domain hop, lands on the transaction, and comes back on every webhook, including each renewal and each adjustment. Attribution and clawback both run on data Paddle itself signed.
Built for how a Merchant of Record actually behaves.
No relay service, ever
Rekomi hosts the webhook endpoint and verifies every event against your destination's signing secret, stored encrypted. Nothing runs on your infrastructure and nothing pages you at 3am.
Adjustment-driven clawbacks
Refunds and chargebacks both arrive as Paddle adjustments, and both reverse commission proportionally the moment they land. Partial refunds reverse partially, in the same audit trail.
Optional health probe
Paste a read-only Paddle API key and Rekomi actively confirms the connection is healthy. Tracking works with the signing secret alone; the probe adds peace of mind.
Currency handled correctly
Paddle sends totals as integer minor-unit strings in the order currency, and Rekomi reads them as-is. Multi-currency reporting rolls everything up without you touching a spreadsheet.
Payouts stay done-for-you
Billing through Paddle changes nothing about paying affiliates: they onboard through Stripe Express with KYC handled by Stripe, Rekomi runs the payout, and tax paperwork is handled at year end.
Part of a bigger stack
Stripe, Braintree, and more are native alongside Paddle, and any other gateway attributes through the HMAC-signed S2S API. Switch billing later without rebuilding the program.
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 Paddle questions.
Do I need to write backend code to connect Paddle?
No. Rekomi gives you a webhook URL unique to your workspace; you create a Paddle notification destination pointing at it, enable the transaction, subscription, and adjustment events, and paste the destination's signing secret back into Rekomi. Rekomi hosts the endpoint, verifies every event against that secret, and records the conversion. There is no relay service to build or maintain.
Paddle hosts my checkout. How does the affiliate get credited?
The referral travels inside the transaction itself. The Rekomi head script captures the affiliate click in a first-party cookie on your marketing site; when you open Paddle Checkout you attach window.Rekomi.getReferral() to customData under the key rekomi_ref. Paddle stores it on the transaction and includes it on every webhook for that order, which is where Rekomi matches the affiliate.
Can affiliates use coupon codes for attribution on Paddle?
No. Per-affiliate coupon-code attribution is a Stripe-specific feature built on Stripe promotion codes; there is no Paddle equivalent in Rekomi. On Paddle, attribution runs entirely on the rekomi_ref value in customData, which the head script plus a one-line stamp handles for every checkout. Affiliates share tracked links as usual.
Can I run Paddle and Stripe tracking at the same time?
No; Rekomi enforces one billing source per workspace so the same sale can never be counted twice. If you have Stripe Connect linked, disconnect it before connecting Paddle (and vice versa). If you genuinely bill on two platforms, run them as separate workspaces.
What happens on refunds and chargebacks?
Paddle reports both as adjustments. When adjustment.created or adjustment.updated arrives with a refund or chargeback, Rekomi reverses the commission proportionally and updates the affiliate's pending balance, with no extra setup and no manual bookkeeping.
Does recurring subscription revenue keep paying commission?
Yes. Every completed Paddle transaction for the subscription carries the customData from the original order, so each renewal is credited to the same affiliate under your campaign's recurring revshare terms. Subscription cancellations stop the clock automatically.
Is this Paddle Billing or Paddle Classic?
The native integration targets modern Paddle Billing (notification destinations, transaction and adjustment events). If you are still on Paddle Classic, the HMAC-signed server-to-server API can relay conversions from your backend until you migrate.
Billing somewhere else? Also covered.
Ten minutes to first click.
Point one Paddle notification destination at Rekomi and your Merchant of Record sales start crediting affiliates today. 14-day free trial, no card.
- 14-day free trial
- Cancel anytime, $0 charged