Paddle pays your company. It does not pay your affiliates.
Teams searching for Paddle mass payouts usually want one batch that turns approved Rewardful commissions into affiliate payments. That job is possible, but the payment rail matters. Rewardful’s documented mass-payout workflow uses Wise or PayPal, not Paddle.
Set the boundary before you run a cycle. Paddle handles customer billing and seller remittances. Rewardful calculates affiliate commissions. Your finance team approves, sends, and reconciles each batch.
Why Paddle Mass Payouts Do Not Run Through Rewardful
Start by separating two uses of the word “payout.” Paddle sends sales proceeds to your business under its merchant-of-record model. An affiliate payout sends your company’s money to a partner. They use different ledgers, approval rules, and payment paths.
Rewardful’s documented Paddle integration applies to Paddle Classic. It does not cover Paddle Billing. If your subscriptions run on Paddle Billing, do not copy a Classic integration guide or point Billing webhooks at Rewardful. There is no documented process where Rewardful sends affiliate money through Paddle.
A custom connector needs vendor validation, test data, and one technical owner. Do not treat a webhook event as proof that a referral, commission rule, and payment amount are correct.
Give each platform one job
Rewardful stores attribution, commission rules, affiliates, and payout history. Paddle manages customer transactions, taxes, refunds, disputes, and seller remittances. Wise Business or PayPal handles the outgoing affiliate payment after finance approval.
A Paddle payout is money Paddle remits to your company. An affiliate payout is a separate payable your company owes.
Use Paddle’s payout reconciliation reports to explain the difference between gross sales and cash remitted to your business. That report does not approve an affiliate commission or prove a partner received money.
Set Prerequisites Before You Create a Payout Batch
Do not start a payment run from clicks, a dashboard total, or one strong month. Start after the referral meets your written program rules and the commission is approved.
Confirm that each affiliate has a legal payee name, valid country, approved payment method, and any tax information your business requires. Keep Paddle account access, Rewardful access, and payment-provider access with named team members.
Create one fixed commission record
Use a spreadsheet or database with one row for every payout line. Keep the original values unchanged. Add corrections, reversals, and reviewer decisions in separate fields.
| Record area | Keep these fields |
|---|---|
| Referral source | Rewardful affiliate ID, referral ID, campaign, and content source |
| Revenue evidence | Paddle transaction ID, customer ID, invoice date, and payment status |
| Commission value | Rule version, approved amount, currency, and reversal amount |
| Payment evidence | Batch ID, provider reference, sent date, reviewer, and final status |
A screenshot can help during a review. IDs are what allow your team to match records across systems.
Write the approval rules before payment day
State when a commission becomes payable. Use the actual amount collected after discounts and refunds if that is your policy. Keep annual subscriptions separate from monthly plans when their reward rules differ.
Exclude internal accounts, test purchases, unpaid invoices, free plans, cancelled subscriptions, chargebacks, and one-time fees unless your program says otherwise. A referral click is not a payable result. A paid customer who meets the published rules is the result.
Restrict changes to payment details
Separate the person who approves commission value from the person who changes an affiliate’s payment details. This control reduces the risk of a fraudulent bank or PayPal account change.
Paddle can handle indirect sales taxes as merchant of record. That does not settle your affiliate tax reporting, contractor classification, withholding, or record-retention duties. Get qualified tax and legal advice for the countries where you operate and pay partners.
Run Rewardful Mass Payouts Through Wise or PayPal
Rewardful’s documented payout process is an export and payment-provider workflow. It is not a Paddle API workflow. Rewardful states that Wise batch payments and PayPal mass payments can handle batches of up to 5,000 affiliates at once.
Run the first cycle with a small approved group. A 25-affiliate test can include renewals, a refund, a discounted sale, and a failed payment. Fix exceptions before moving to a full monthly batch.
- Open Payouts in Rewardful and select the payment period. Review commissions that are due, then exclude items that are already paid, disputed, or under a refund hold.
- Download the Wise or PayPal payout CSV from Rewardful. Check the row count, currency, affiliate ID, payment amount, and destination details against your fixed commission record.
- Upload the file to Wise Business or your available PayPal business mass-payment workflow. Review every validation error before authorizing the batch. Do not edit payment details based on an email reply or direct message.
- Save the provider batch ID, submission date, total amount, and individual payment references. A submitted file is not proof that every affiliate received funds.
- Mark only successful payments as complete in Rewardful. Leave rejected, returned, or pending items open for review. Do not mark an entire export as paid because the file was downloaded.
Use a unique batch ID for every run, such as 2026-08-affiliates-usd-01. Never rerun the same export without comparing it to the first batch. Duplicate payouts often begin with a rushed retry.
Reconcile Affiliate Payments Against Paddle Revenue
Gross customer billings are not the amount you have available for affiliate payments. Paddle remittances can include taxes, refunds, chargebacks, retained fees, and timing differences between sales and payout dates.
For Paddle mass payouts, finance needs two separate views: customer revenue and affiliate expense. Do not merge them into one dashboard number.
Match the payout batch to source transactions
Use the Rewardful export as the commission source. Use the payment-provider confirmation as proof of affiliate payment. Use Paddle records to confirm the underlying customer transaction and later adjustments.
Paddle’s reconciliation reports break down balance movements, fees, taxes, and adjustments. Use them to explain remittance totals. Use adjustment line-item reports when you need to trace a refund, credit, or chargeback to transaction items.
Your internal calculation can stay simple:
net affiliate earnings = approved percentage commissions + approved fixed commissions - reversals
Do not calculate this from memory or from the latest Paddle payout alone.
Close each batch with payment evidence
Compare the Rewardful export total, Wise or PayPal batch total, successful payment count, rejected payment count, and final bank or provider confirmation. Record the final amount in the payment currency, not only the original commission currency.
The number that matters is the reconciled payout total. An exported commission can still be reversed, duplicated, missing a payment detail, or rejected by the provider.
Automate the Controls, Not the Payment Decision
Rewardful does not provide a documented route for sending affiliate funds through Paddle. Your automation can prepare data, flag exceptions, and create a review file. It should not turn a billing event into an unreviewed payment.
Use Paddle’s API reference to work with billing records. Keep API keys in approved secrets storage. Do not expose Paddle credentials in browser code, spreadsheets, or affiliate-facing tools.
Process webhooks once
Paddle can retry webhook deliveries. Your handler must verify webhook signatures and store each processed event ID before it creates a financial side effect. Paddle’s webhook delivery guidance recommends keeping processed event IDs to prevent duplicate actions.
Create an internal payout key with the batch ID and affiliate ID. If the same event or job runs twice, your system should return the existing payout line instead of creating another one.
Use bounded retries for temporary failures. Stop and investigate authentication failures, schema changes, and invalid payment details. A successful automation run is not proof that the payout data was accepted.
Use Paddle adjustments only for customer transactions
A Rewardful commission problem is not a Paddle adjustment. Paddle Billing uses adjustments for customer refunds and credits.
The request structure is straightforward: send POST /adjustments with an action such as refund, a transaction_id, affected line-item data, and a reason. First retrieve the transaction and its line items. Refund adjustments apply to completed transactions.
Paddle may place a live refund into pending_approval. Do not submit another adjustment for the same transaction while one remains pending. Review Paddle’s process to refund or credit a transaction before building a customer-refund workflow.
Fix Refunds, Chargebacks, and Failed Payments
A payout batch can fail after the CSV import. A customer can also receive a refund after the related affiliate has been paid. Treat these as exceptions with an owner, a due date, and a written outcome.
Check status in all three systems
Check Rewardful for commission and payout status. Check Wise or PayPal for accepted, pending, completed, returned, or rejected payment results. Check Paddle for the customer transaction status and any adjustment status.
A refund can change a commission amount. A chargeback can also reduce the related transaction and add fees to your Paddle balance. Hold future payments where your affiliate terms allow it. Do not debit an affiliate or reverse a completed payment without a written policy and evidence.
Keep an exception queue
Use a separate queue instead of hiding failed rows inside the next export.
- Route missing payment details back to the affiliate through your approved support process.
- Hold commissions linked to pending refunds, disputes, or incomplete customer payments.
- Record rejected Wise or PayPal payments with the provider reference and return reason.
- Search affiliate ID, batch ID, and transaction ID before sending a replacement payment.
Keep the last trusted reconciliation file. If a configuration change causes missing attribution or duplicate commissions, your team still has a verified record to work from.
If your program spans several entities, currencies, or a custom Paddle Billing connector, Book A Call before you deploy an automated payment write path.
Conclusion
Do not confuse Paddle seller remittances with affiliate payments. They are separate financial events with separate records.
The reliable process is simple: approve commissions in Rewardful, export a controlled batch, pay through Wise or PayPal, then reconcile every completed payment against source transactions and provider references.
Paddle mass payouts should describe the revenue context, not the affiliate payment rail. Accuracy before payment prevents most duplicate, missing, and disputed payout problems.
