A customer downgrade should lower future affiliate payouts, not create a cleanup project for finance. Rewardful partner downgrades work best when Stripe remains the billing source of truth and Rewardful calculates commissions from paid invoices.
Don’t change partner rates every time a customer moves plans. In most cases, Rewardful already handles the result. Your automation should record the plan change, confirm when it takes effect, and watch the next paid invoice.
HOW REWARDFUL PARTNER DOWNGRADES WORK
Rewardful is built for subscription businesses that use Stripe. It tracks referred customers through the referral value in Stripe customer metadata, then creates recurring commissions when those customers pay eligible invoices.
A downgrade changes the customer’s future bill. If your campaign pays a percentage commission, the next commission falls with the amount collected. Rewardful calculates the commission from the amount the customer actually paid, not the plan’s old list price.
Rewardful’s affiliate commission payment flow covers this model. Stripe sends billing data, Rewardful identifies the referral, and an eligible paid invoice creates the commission.
A downgrade does not always take effect today
Stripe can apply a plan downgrade immediately or at the end of the current billing period. That timing controls the commission result.
An immediate change can create a prorated invoice or credit. A downgrade scheduled for renewal leaves the current invoice unchanged. The lower commission starts when the lower-priced invoice is paid.
Treat the paid invoice as the financial record. A subscription update tells you what may happen. It does not confirm the final commission amount.
Keep campaign rules simple
Rewardful campaigns can pay recurring commissions until a referred customer cancels. You can also limit the number of commission-generating payments for each customer. Review the current campaign settings before you add custom logic.
For example, a 20% recurring campaign pays $20 on a $100 invoice. If the customer later pays $50 per month, the future commission becomes $10. No partner-level rate change is required.
BUILD THE DOWNGRADE AUTOMATION WORKFLOW
Rewardful handles invoice-based commission calculation. Your external workflow handles policy, records, alerts, and exceptions.
1. Define the commission policy first
Write one rule your support, finance, and partner teams can use:
- Future commissions follow the amount collected on each eligible Stripe invoice.
- Existing commissions remain in the record unless the related payment is refunded or reversed.
- A scheduled downgrade takes effect on the invoice date, not the date a customer clicks “change plan.”
- A plan-specific exception needs a documented owner and approval path.
This prevents a common mistake. Teams see a customer move down a plan and immediately reduce an already-earned commission.
2. Capture the Stripe subscription change
Send Stripe’s customer.subscription.updated event to Zapier, Make, n8n, or your own webhook endpoint. Store the event before you change anything.
Record the Stripe customer ID, subscription ID, old and new price IDs, effective date, current subscription status, and event ID. Use the event ID as an idempotency key so retries don’t create duplicate records.
Your minimal workflow logic can look like this:
- If a subscription changes to a lower-priced item, create a
downgrade_pendingrecord. - If the change is scheduled for period end, set the review date to the next renewal.
- If it takes effect now, flag the next invoice for review.
- When the related invoice is paid, compare the collected amount with the expected plan price.
- Let Rewardful create the normal recurring commission, then store the commission ID and state.
Do not build against an assumed Rewardful subscription.downgraded event. Rewardful webhooks are for Rewardful records, while Stripe is the system that reports subscription changes. Rewardful’s webhook request documentation shows that its endpoint payloads are JSON POST requests with object, event, and request root fields.
3. Match the invoice to the affiliate record
When the invoice clears, query or review the Rewardful commission record. Keep these values in your internal table:
- Stripe invoice ID and amount paid
- Stripe customer and subscription IDs
- Rewardful affiliate ID and campaign
- Rewardful commission ID, amount, currency, and state
- Downgrade effective date and review outcome
Rewardful commission states include pending, due, paid, and voided. The Rewardful REST API overview is useful when your team needs reporting or reconciliation access.
FUTURE COMMISSIONS VS PREVIOUSLY EARNED COMMISSIONS
A customer downgrade changes future commissions. It does not rewrite the original sale.
If the affiliate earned a commission from a $100 invoice last month, keep that commission visible. The customer was on the $100 plan and Stripe collected that amount. A lower plan next month creates a lower future commission.
Refunds are different. Rewardful can recalculate commissions when a related Stripe payment is partially or fully refunded. Its automated refund handling is separate from ordinary plan downgrades.
Do not overwrite financial history
Keep an adjustment row when a commission changes. Do not replace the original amount and remove the reason.
Your record should show the original commission, the later refund or reversal, the date, the linked invoice, and the person or workflow that approved the action. This gives finance a clean audit trail when a partner asks why a future payout changed.
A commission marked due is not the same as cash already sent. Keep earned, payable, paid, refunded, and voided amounts separate in internal reports.
HANDLE PARTNER-SPECIFIC EXCEPTIONS CAREFULLY
Some programs promise different rates by partner, customer segment, or plan tier. That policy needs more control than a standard recurring campaign.
Rewardful’s documented campaign settings support commission percentages and fixed amounts at the campaign level. The public API documentation does not show a partner-specific commission-rate endpoint for changing one affiliate’s rate after enrollment.
Do not edit a shared campaign because one referred customer downgraded. That can affect more than the one relationship you intended to change.
Use a controlled exception path
For a special agreement, create an exception record with the affiliate, customer, plan, effective date, contract rule, and approver. Then decide whether the correct action is a campaign change, a manual commission review, or a separate payout adjustment.
If engineering, finance, and partnerships need one approved process before launch, Book A Call to map the workflow and ownership rules.
TEST THE WORKFLOW BEFORE YOU SCALE
Run controlled tests using an internal referral or low-risk subscription. Test one immediate downgrade, one period-end downgrade, one partial refund, and one failed webhook retry.
Check that each case creates one internal downgrade record. Confirm the next paid invoice amount. Then confirm the Rewardful commission matches the collected amount and remains tied to the correct affiliate.
Review failures by record, not by dashboard totals. A useful support case includes the Stripe customer ID, subscription ID, invoice ID, Rewardful affiliate ID, commission ID, date range, expected result, and screenshots.
FINAL CONTROL
Rewardful partner downgrades do not need a rate-change bot. For standard recurring campaigns, the lower paid invoice produces the lower future commission.
Keep Stripe plan changes, Rewardful commission records, and your exception log connected. **Preserve past commissions, verify future invoices, and adjust only when a real refund or approved policy requires it.
