If your team uses Paddle Billing, stop before wiring anything. Rewardful’s current Paddle integration supports Paddle Classic, not Paddle Billing. That distinction decides whether Paddle coupon tracking can create a commission record or only a discount record.
A discount can reduce the checkout price without identifying the affiliate who drove the sale. Build the attribution path first. Then test the paid transaction, not only the coupon field.
Paddle coupon tracking starts with product compatibility
Check the Paddle product in your account before you create affiliate codes or promise commission terms. Paddle Classic and Paddle Billing use different checkout and event models. One code path does not bridge them.
Rewardful supports Paddle Classic
Rewardful’s documented Paddle connector requires Paddle Classic. Connect the Paddle account in Rewardful, then add the Paddle Classic public key in the Rewardful integration settings.
Use Rewardful’s Paddle Classic integration guide as the setup reference. Do not put a Paddle API key in browser code. Rewardful asks for the public key, which is the correct configuration value for this connection.
Rewardful also lists coupon code tracking as an option for influencer and non-link promotion. That does not remove the need to verify the referral data that reaches the Paddle Classic checkout.
Paddle Billing discount events are separate
Paddle Billing can create customer-facing discount codes. Its discount configuration documentation covers code-based discounts at checkout.
That is useful for pricing. It is not a documented Rewardful attribution path.
Paddle Billing can also emit discount-related events, such as checkout.discount.applied. The event confirms that a discount was used. It does not create a Rewardful affiliate sale or commission.
If your account is Paddle Billing only, do not build an undocumented workaround around browser events or custom webhook forwarding. Pick an affiliate platform that documents Paddle Billing support, or keep coupon performance separate from affiliate reporting.
Configure the documented Paddle Classic path
The Paddle Classic flow has three moving parts: browser referral capture, checkout passthrough data, and Paddle payment notifications. Each part needs a clear owner.
Browser-side tracking carries the referral
The Rewardful script runs in the visitor’s browser. It identifies an affiliate referral after someone lands through an affiliate link. Your Paddle Classic checkout implementation must then include that referral value in its passthrough data.
Use this configuration map before you publish the checkout:
| Layer | Configuration | Result to verify |
|---|---|---|
| Browser | Rewardful script loads before checkout opens | A valid referral value is available |
| Paddle Classic checkout | Passthrough includes the referral attribute | The referral reaches Paddle’s event data |
| Rewardful | Paddle Classic account and public key are connected | Referral becomes a lead and later a sale |
If your backend creates the checkout configuration, preserve the browser referral value when it builds passthrough data. A backend update that replaces the full passthrough object can drop the referral without showing an error.
The browser records intent. It does not confirm revenue.
Webhooks create the financial record
Paddle’s server-side notifications are the proof point. Rewardful uses Paddle notifications when a referred customer creates a subscription and when a payment succeeds.
According to Rewardful’s Paddle event handling details, a valid referral attribute lets Rewardful create the referred customer record. Rewardful checks the referral again on successful payment before recording the sale.
The sale amount should match what the customer actually paid after discounts or account credits. Do not calculate affiliate commission from the list price if the coupon changed the collected amount.
Verify revenue records, codes, and exceptions
Coupon attribution needs the same review discipline as any payout process. Clicks show interest. A completed checkout can still fail attribution. A paid sale with an approved commission is the record that matters.
Run a controlled checkout test
Use a test affiliate, a known referral link, and a low-risk Paddle Classic test purchase. Run the sequence in a clean browser profile so an old referral cookie does not hide a setup problem.
- Open the affiliate link and confirm the Rewardful script loads before checkout.
- Apply the intended coupon code during the Paddle Classic checkout.
- Inspect the checkout data and confirm it includes a valid
referralpassthrough attribute. - Complete the subscription and confirm Rewardful creates the referred customer record.
- Wait for the successful payment event, then confirm the sale and commission appear.
- Compare the Rewardful sale amount with the amount paid after the coupon discount.
- Test a cancellation or refund path and record the final commission status.
- Run a coupon-only purchase separately if you plan to credit sales without an affiliate link.
Keep a fixed record for each test and live exception. Store the affiliate ID, coupon code, Paddle checkout ID, order ID, discount value, amount paid, commission status, reversal, and payout reference. Do not overwrite the original transaction when a refund occurs. Add a correction record instead.
Catch the common failure causes
Most failures are simple. The account uses Paddle Billing. The Rewardful script loads after checkout. The referral attribute is missing. A backend process replaces passthrough data. The team checks a discount event but never confirms the successful payment.
Another mistake is treating a Paddle coupon as a double-sided incentive. Rewardful’s double-sided incentive feature is not available for Paddle customers. Keep the customer discount and affiliate commission rules separate.
A coupon displayed at checkout is not a confirmed commission. Reconcile against the paid transaction and its final status.
Final check
Paddle coupon tracking works with Rewardful when the account is on Paddle Classic, the referral reaches checkout passthrough data, and Paddle’s successful payment notification creates the sale record.
The coupon controls the price. The referral attribute connects the customer to the affiliate. The paid amount is the figure you reconcile before approving commission.
