An affiliate click is not a commission. A Paddle affiliate dashboard works only when referral data, checkout records, subscription events, and payouts agree.
There is one hard limit in August 2026. Rewardful connects with Paddle Classic, not Paddle Billing. Confirm that boundary before you configure campaigns, invite partners, or write a line of checkout code.
START WITH THE PADDLE COMPATIBILITY CHECK
Rewardful’s current Paddle integration requirements apply to Paddle Classic. Paddle Billing is Paddle’s newer billing product, and it uses a different checkout, API, and webhook setup.
REWARDFUL ONLY CONNECTS TO PADDLE CLASSIC
Check the product name in your Paddle account and in your current checkout implementation. A Paddle.Checkout.open() flow with Paddle Classic settings is the supported path for Rewardful.
If your SaaS runs on Paddle Billing, stop here. Don’t paste Billing credentials into Rewardful or try to adapt a Billing checkout to a Classic integration. The referral data will not have a supported path through the system.
Choose a tracking tool that supports Paddle Billing, or keep the affiliate program on hold while you review your billing setup. A dashboard that cannot receive valid revenue events will create payout disputes.
KEEP MERCHANT-OF-RECORD AND AFFILIATE WORK SEPARATE
Paddle’s merchant-of-record role covers checkout and the payment, tax, and compliance duties Paddle accepts under your agreement. Rewardful handles referral attribution, campaign rules, affiliate records, and commission reporting.
Those are separate jobs. Paddle doesn’t decide whether an affiliate followed your program terms. Rewardful doesn’t replace your tax, legal, or customer-refund obligations.
Write program terms that state what counts as an eligible sale, when a commission can reverse, and when payouts are due. Keep those rules under your control.
SET THE PREREQUISITES BEFORE YOU CONNECT ACCOUNTS
Set access, campaign rules, and checkout ownership before opening the integration screen. This avoids a common failure, marketing creates a campaign while engineering cannot pass the referral into checkout.
GET THE RIGHT ACCESS AND ASSETS
You need access to your Rewardful account and Paddle Classic account. You also need a developer who can edit the page that opens Paddle Checkout.
Prepare these items before setup:
- The Paddle Classic public key from Developer Tools.
- Access to Paddle Classic webhook settings.
- The live website location where the Rewardful JavaScript will load.
- Ownership of the checkout code and deployment process.
- A test affiliate account and a test purchase process.
Keep one named owner for Paddle settings, one for Rewardful campaigns, and one for payout approval. A shared admin login creates confusion when an event fails or a commission needs review.
WRITE THE CAMPAIGN RULES FIRST
Create the commercial rules before affiliates see a signup page. Decide whether rewards are a percentage of collected revenue, a fixed amount, or recurring commissions.
Also define your eligible products, attribution period, coupon policy, refund window, payment threshold, and payout schedule. State whether self-referrals, paid search bidding, cashback sites, or unsolicited email are allowed.
Don’t calculate commission from a public list price when the buyer used a discount or account credit. Your payout record should match the amount the customer actually paid.
An affiliate link records referral intent. A paid Paddle event is the record that supports a commission.
CONNECT PADDLE CLASSIC TO REWARDFUL
The connection has two parts. Rewardful needs your Paddle Classic public key, then Paddle Classic needs Rewardful’s webhook endpoint.
ADD THE PADDLE CLASSIC PUBLIC KEY
Create or open your Rewardful account and select Paddle as the payment processor. In Paddle Classic, open Developer Tools, then Public Key.
Copy the entire public key. Keep the BEGIN and END markers when you paste it into Rewardful. Removing those lines can break validation.
Follow Rewardful’s current Paddle Classic connection steps rather than relying on an old screenshot or copied implementation. Paddle Classic settings and account menus can differ from Paddle Billing.
Create your first Rewardful campaign after the key is accepted. Use a clear internal name, such as “SaaS Partner Program, Recurring Revenue,” so finance can identify it later.
SEND PADDLE EVENTS TO REWARDFUL
Copy the webhook endpoint URL shown in Rewardful. In Paddle Classic, open Developer Tools, then Events, and add that URL under the webhook receiver settings.
Select the events required by Rewardful’s current setup instructions before you save. Don’t guess at the event list from an old implementation.
Paddle webhooks are server-to-server notifications. They record events that a browser cannot prove, including payment and subscription changes.
After you save, document the endpoint owner, date added, Paddle account, and linked Rewardful campaign. That record cuts investigation time when someone changes a checkout or webhook configuration later.
PASS REFERRAL DATA THROUGH PADDLE CHECKOUT
The public key and webhook are not enough. Your checkout must send the Rewardful referral ID into Paddle Classic as passthrough data.
INSTALL REWARDFUL BEFORE CHECKOUT OPENS
Install the Rewardful JavaScript on the pages where visitors arrive and purchase. When a visitor follows an affiliate link, Rewardful creates a referral identifier in the browser.
Your Paddle Classic checkout code must pass that identifier when it calls Paddle.Checkout.open(). Rewardful’s documented pattern stores the referral under a rewardful.referral field inside the JSON-encoded passthrough value.
Use the official checkout passthrough example as the implementation source. Put the referral capture before the checkout action, not on a thank-you page after payment.
PROTECT EXISTING PASSTHROUGH DATA
Many SaaS teams already use passthrough data for plan IDs, account IDs, trial details, or internal order references. Merge the Rewardful referral field into that object.
Don’t replace the full passthrough object with a new one. That can remove account data or silently drop the referral ID.
Rewardful uses Paddle events to create referred customer and sale records. Its explanation of how Paddle account events are used makes the order clear: browser attribution starts the trail, while Paddle payment activity confirms it.
A Paddle affiliate dashboard should show both layers. Clicks help you assess partner traffic. Paid and approved sales tell you what you owe.
BUILD THE PADDLE AFFILIATE DASHBOARD IN REWARDFUL
Rewardful’s campaign is the operating layer for your affiliate program. Keep the first version narrow. Invite a small set of known partners before you open applications broadly.
CONFIGURE A CLEAR PARTNER EXPERIENCE
Create one campaign with a simple offer and a defined audience. Give partners one approved landing page, current product positioning, brand rules, and a support contact.
Keep the first campaign separate from future experiments. Don’t change a live commission rate without recording the effective date and the affected affiliates.
Use affiliate applications or manual approval when brand risk matters. Review the partner’s website, promotion method, geographic focus, and existing audience before you provide a live referral link.
A high-traffic partner with misleading claims creates support tickets, refunds, and compliance risk. Affiliate volume is not the same as affiliate quality.
TRACK APPROVED COMMISSIONS, NOT CLICKS
Your Rewardful dashboard is useful for daily management. It should not be your only payout ledger.
Maintain a fixed reconciliation record for each affiliate and reporting period.
| Record | What to review | Why it matters |
|---|---|---|
| Referral clicks | Traffic source and landing page | Shows partner interest |
| Pending sales | Paddle event and customer status | Shows possible liability |
| Approved commissions | Paid amount and program terms | Sets payout amount |
| Reversals | Refunds, cancellations, disputes | Removes invalid rewards |
| Paid commissions | Payout date and reference | Closes the record |
Keep the original Paddle event unchanged. Store corrections, manual approvals, and reversal reasons in separate fields with a date and owner. A later adjustment should not erase the evidence behind an earlier payout decision.
TEST THE FULL REFERRAL AND PAYMENT FLOW
Run a controlled test before you invite affiliates. Test the same route that a real visitor will use, including the live landing page, browser script, checkout, webhook, and Rewardful campaign.
RUN A CONTROLLED AFFILIATE TEST
Start with a clean browser profile. Open a test affiliate link, visit the product page, and complete a test purchase using the test method available in your Paddle account.
Then confirm each result:
- The affiliate referral is present before checkout opens.
- Paddle Classic receives the passthrough value.
- Rewardful receives the relevant Paddle webhook event.
- The referred customer and sale appear under the correct campaign.
- The calculated commission matches the collected amount and campaign rules.
Test a refund, cancellation, or other lifecycle change before your first payout cycle. You need to know how the program handles reversals before a partner asks why a reward disappeared.
CATCH THESE FAILURES BEFORE LAUNCH
The same setup errors appear in most broken affiliate programs:
- The team uses Paddle Billing while following Paddle Classic instructions.
- Someone pastes an incomplete public key into Rewardful.
- The webhook URL exists, but the required Paddle events are not selected.
- The Rewardful script loads after checkout code runs.
- A code update overwrites the existing passthrough object.
- Finance pays pending commissions before refunds and reversals settle.
- The team measures completed checkouts but never reconciles actual payouts.
Run a small approved batch of partner tests before you forecast revenue or monthly affiliate costs. Measure accepted commissions and paid results, not dashboard activity alone.
SECURE THE PROGRAM AND PREPARE THE LAUNCH
Affiliate tracking touches customer purchases, partner payment details, and revenue records. Treat the setup as a finance workflow, not only a marketing campaign.
RESTRICT ACCESS AND RETAIN AN AUDIT TRAIL
Give Paddle developer access only to people who need it. Use separate individual accounts, multi-factor authentication, and approved secrets storage for credentials that are not meant for the browser.
Don’t place private keys, account passwords, or payout details in front-end code, shared documents, or chat threads. Review access when an employee or contractor changes roles.
Follow current Paddle developer documentation for your account’s security and integration requirements. Keep Rewardful payout access separate from campaign editing where your process allows it.
For tax forms, contractor classification, withholding, and record retention, use advice that applies to your business location and affiliate arrangement.
USE THIS CONCISE LAUNCH CHECKLIST
Before you announce the program, confirm that:
- Your payments run on Paddle Classic, not Paddle Billing.
- Rewardful has the complete Paddle Classic public key.
- Paddle Classic sends required webhooks to Rewardful.
- Checkout passes the Rewardful referral through
passthrough. - A test referral produces the correct customer, sale, and commission.
- Refunds and cancellations create the expected reversal process.
- Commission terms and prohibited promotion methods are published.
- One owner approves payouts and keeps a reconciliation record.
- Your team knows who investigates a failed webhook or missing referral.
If your team has multiple checkouts, product catalogs, payout markets, or complex exception rules, Book A Call before you allow automated payout decisions.
FINAL THOUGHTS
A working Paddle affiliate dashboard starts with product compatibility, then depends on disciplined checkout attribution and Paddle-backed payment records.
Rewardful can manage the affiliate layer for Paddle Classic. It cannot turn a Paddle Billing checkout into a supported integration.
Launch with a small partner group, reconcile every payout against real subscription activity, and keep corrections separate from the original financial record.
