Affiliate tracking fails when the checkout loses the referral record. Paddle affiliate software built with Rewardful can work well for SaaS teams, but only if your billing setup matches the integration requirements.
As of August 2026, Rewardful supports Paddle Classic, not Paddle Billing. Check that first. A clean affiliate landing page can’t fix an unsupported billing connection.
CHECK YOUR PADDLE VERSION BEFORE YOU BUILD
Start in your Paddle account. Confirm whether you use Paddle Classic or Paddle Billing. Don’t rely on account age, old code, or a teammate’s memory.
Rewardful’s current Paddle integration is for Paddle Classic. If your product uses Paddle Billing, stop the setup and choose a tool that supports its current checkout and event model. Paddle Billing uses custom data, while Paddle Classic uses passthrough data. Rewardful’s documented flow depends on Classic passthrough.
Confirm the checkout path
A Paddle Classic implementation uses Paddle.Checkout.open() to launch checkout. Your site passes the Rewardful referral value into that checkout call.
Paddle Billing has a different workflow. Paddle’s Classic and Billing workflow mapping shows why a migration changes more than a few settings.
Check these items before opening a Rewardful account:
- Your live checkout uses Paddle Classic.
- Your developer can update the Classic checkout code.
- Your Paddle account can send the required webhook events.
- You can test a new subscription, renewal, cancellation, and refund.
A completed checkout only proves payment worked. It doesn’t prove the correct affiliate received the correct commission.
Keep the integration decision documented
Write down the Paddle version, checkout owner, webhook owner, and affiliate program owner. Store the date you confirmed the setup.
This prevents a common failure. A developer migrates billing later, checkout still works, and affiliate attribution stops without anyone noticing.
SET UP PADDLE AFFILIATE SOFTWARE WITH REWARDFUL
Rewardful manages the affiliate program layer. Paddle remains the billing and checkout system. The connection between them is the referral value and Paddle’s event data.
Connect your Paddle account details
Create your Rewardful account and select Paddle as the payment processor during setup. Rewardful’s Paddle integration overview describes the current connection flow.
Rewardful asks for your Paddle public key. In Paddle Classic, this has appeared under Developer Tools and Public Key. Interface labels can change, so use the current Paddle and Rewardful instructions instead of an old screenshot.
Next, copy the webhook endpoint generated by Rewardful into Paddle’s webhook configuration. Paddle sends payment and subscription activity to that endpoint. Rewardful uses those events to create sales and commission records.
Don’t paste private credentials into project documents, chat tools, or affiliate briefs. A public key is designed for browser use. Authentication secrets and webhook credentials need tighter access controls.
Pass the referral value to Paddle checkout
Rewardful gives each affiliate a unique referral link. When a visitor arrives through that link, Rewardful records a referral ID in the browser.
Your developer must pass that referral ID to the Paddle Classic checkout through the passthrough value. Rewardful’s implementation documentation shows the referral value coming from window.Rewardful.referral before checkout opens.
The flow is simple:
- An affiliate sends a prospect to your site with a Rewardful link.
- Rewardful records the referral ID.
- Your checkout code sends that ID to Paddle Classic as passthrough data.
- Paddle sends transaction and subscription events to Rewardful.
- Rewardful matches the event to the affiliate and records the commission.
If step three fails, your Paddle affiliate software may show clicks but no payable sales. Ask your developer to test the full path, not only the affiliate link.
KNOW WHAT REWARDFUL AND PADDLE EACH HANDLE
Teams create reconciliation problems when they treat both products as one system. They are connected, but they have separate jobs.
| System | What it handles | What it does not replace |
|---|---|---|
| Paddle | Checkout, customer billing, subscription activity, refunds, and event delivery | Affiliate terms and commission rules |
| Rewardful | Affiliate links, referral attribution, campaigns, commission records, and affiliate program operations | Paddle’s billing records and customer payment status |
| Your team | Terms, fraud review, approval decisions, partner communication, and financial reconciliation | Automated judgment on disputed activity |
Paddle is the source of the billing event. Rewardful reads that event and applies your affiliate rules. A Rewardful commission record is not proof that a payout should go out without review.
Treat refunds as a billing event, not a spreadsheet task
Rewardful receives Paddle webhook activity for successful payments and refunds. Its Paddle account event documentation notes that full and partial refunds trigger webhook requests.
Set a written rule before launch. For example, a fully refunded purchase may remove the commission. A partial refund may reduce it. Your policy should say what happens before your finance team sees the first exception.
Rewardful has also described support for subscription changes, cancellations, and refunds in its Paddle integration update. Test each event against your own campaign terms.
WRITE COMMISSION TERMS BEFORE INVITING AFFILIATES
A referral link is easy to create. Clear commission terms take more care. Affiliates need to know what counts as a qualified sale and when money becomes payable.
Choose a commission model you can audit
Common SaaS structures include a fixed bounty for a paid new subscription, a percentage of the first payment, or recurring revenue share for a defined period.
For example, your terms could offer “$30 for each new paid subscription after the 30-day refund period.” Another program may offer “20% of net subscription revenue for the first 12 paid months.”
Don’t publish either example without defining the details. State whether the commission uses gross revenue or net revenue. Explain how taxes, discounts, refunds, chargebacks, upgrades, downgrades, and currency conversion affect the amount.
A short rule like “20% recurring commission” leaves too much room for disputes.
Define attribution and payout conditions
Your terms should explain who gets credit when more than one affiliate reaches the same customer. They should also explain whether a customer can refer themselves, use their own link, or earn commission on a company they control.
Set a payout review period that gives billing events time to settle. Then reconcile approved Rewardful commission records against Paddle transaction records before payment.
Affiliates also need a disclosure rule. Require a clear statement near a recommendation that they may earn a commission. Don’t hide it in a profile page or the last line of a long video description.
TEST REFERRALS, RENEWALS, AND REFUNDS
Run a small internal pilot before promoting the program. Use employees, contractors, or a few trusted partners. Don’t start with a public signup form and hundreds of unknown referrals.
Use a controlled test set
Create a test record for each case. Include the affiliate ID, customer email used for testing, Paddle transaction ID, expected result, actual result, and reviewer decision.
Test these cases:
- A new customer buys through an affiliate referral link.
- A visitor buys without a referral link.
- The referred customer renews a subscription.
- The customer upgrades, downgrades, or cancels.
- A full refund is issued.
- A partial refund is issued.
- A blocked self-referral or duplicate account attempts purchase.
Use a test environment when your Paddle setup supports it. If you must use live payments, use internal cards and make the smallest permitted transactions. Never test with a real prospect’s card or personal data.
Review accepted records, not browser activity
A test can show green check marks while producing the wrong finance record. Your team should compare Paddle’s event history with Rewardful’s attributed sale and commission result.
Track accepted commission records, missing attribution, duplicate attribution, refund adjustments, failed webhook deliveries, and reviewer time. Keep the original billing record unchanged. Store the expected result and final decision separately.
A process that saves ten minutes of development work but creates thirty minutes of commission corrections has failed its business test.
CONTROL FRAUD, DISCLOSURES, AND CUSTOMER DATA
Affiliate programs attract real partners and opportunists. Your controls need to handle both.
Block activity that breaks your terms
Ban self-referrals, fake leads, misleading claims, unauthorized coupon pages, and paid ads that misuse your brand name. Don’t wait until payout day to review suspicious activity.
Look for patterns such as a sudden cluster of purchases, repeated customer details, unusual refund rates, or affiliates whose referrals cancel after the first payment. Pause payment on questionable commissions until the underlying Paddle activity is reviewed.
Keep a named owner for each exception. One person should decide whether the commission is approved, rejected, reduced, or held for more evidence.
Minimize the data you expose
Rewardful referral data can connect to customer and transaction data. Treat that mapping as business-sensitive data.
Give team members only the access they need. Limit export permissions. Remove former employees and agencies quickly. Keep a record of who can view affiliate, customer, and payout information.
Your privacy notice should explain the tracking used for affiliate attribution. If you sell into regions with consent or privacy requirements, have the wording and tracking approach reviewed for those markets.
LAUNCH WITH A SMALL PARTNER GROUP
Your first launch should be controlled. Invite five to ten trusted affiliates who already understand your product and audience.
Give them approved positioning, brand rules, disclosure requirements, landing page links, and one support contact. Don’t ask them to invent product claims or promise features your team can’t support.
Measure the program after each payout cycle
Review performance after each cycle, not only at quarter-end. Track:
- Approved affiliate sales and commissions.
- Missing or duplicate referral records.
- Refund, cancellation, and chargeback adjustments.
- Fraud reviews and payout holds.
- Human review time per accepted commission.
- Support issues caused by unclear terms.
Keep the last trusted reconciliation file. If a webhook change, checkout update, or migration creates bad data, you need a known-good record to compare against.
Paddle affiliate software removes the need to build tracking from scratch. It does not remove the need for financial controls, written terms, and regular review.
FINAL CHECK BEFORE YOU OPEN THE PROGRAM
Rewardful and Paddle Classic can give your SaaS team a practical affiliate system without custom tracking software. The setup depends on a working referral passthrough, active webhooks, clear commission terms, and tested refund handling.
Launch with a small approved group. Reconcile each payout cycle against Paddle records. Accurate attribution before payout is the control that protects both your affiliates and your business.
