A referred customer can move to a lower plan while your dashboard still shows the original commission history. If you don’t record the change correctly, finance forecasts too much revenue and partners receive confusing payout updates.
Rewardful partner downgrades need a controlled workflow. Stripe remains the billing record. Rewardful adjusts commissions based on billing activity, while your team needs a separate record of what changed, when it changed, and who reviewed it.
Start by defining the downgrade, then build a process that preserves the first result and every later correction.
Define What Counts as a Downgrade
In this workflow, a partner downgrade means a customer referred by an affiliate or partner moves to a lower-value subscription. It does not mean the partner’s own account changed.
A downgrade can reduce monthly recurring revenue, commission value, or both. The change may apply immediately, at the next renewal, or after a scheduled plan switch.
Separate a real downgrade from similar billing changes
Do not label every lower invoice as a downgrade. A coupon, proration credit, failed payment, partial refund, or reduced usage can lower an invoice without changing the customer’s long-term plan.
Check these fields before you create a downgrade record:
- The old and new Stripe price or plan reference.
- Subscription quantity, billing interval, and recurring amount.
- Effective date for the change.
- Whether the change is immediate or scheduled for renewal.
- The Stripe customer and subscription IDs.
- The affiliate or partner attribution linked to that customer.
A customer moving from a $199 monthly plan to a $99 monthly plan is a clear downgrade. A $199 renewal with a one-time $50 credit needs a different label.
A lower invoice is evidence to review. It is not proof that the subscription was downgraded.
Keep Stripe as the Billing Source of Truth
Rewardful syncs with Stripe for customer, invoice, and refund activity. Its commission calculations adjust for upgrades, downgrades, cancellations, free trials, and refunds based on what the customer actually pays. Review how Rewardful pays affiliate commissions before you build custom adjustment rules.
Your internal system should not try to replace either platform. It should connect the billing change to the partner record and create an audit trail.
Use a source hierarchy
Use the same order every time a record conflicts:
| Question | Source to check first | Record to retain |
|---|---|---|
| Did the subscription change? | Stripe subscription record | Subscription ID and change timestamp |
| When did billing change? | Stripe invoice or payment record | Invoice ID and amount paid |
| Which partner referred the customer? | Rewardful referral data | Partner and referral reference |
| What happened to commission? | Rewardful commission view or export | Original and revised commission values |
| Has money already been paid out? | Payout history and finance ledger | Payout ID, date, and status |
This order prevents a common reporting error. Your team might see a lower plan in Stripe, then assume a commission has already changed in Rewardful. Check the actual commission record before you send a notice or adjust a forecast.
Store an append-only history
Never replace the original commission row with a new amount. Keep the original result, then add an adjustment record.
For each adjustment, store the original commission amount, revised amount, adjustment amount, reason, effective date, source IDs, reviewer, and payout impact. Add a workflow run ID if automation created the record.
For example, a referred customer drops from $200 to $100 per month. If the partner earns 20%, the expected recurring commission moves from $40 to $20. Your ledger should show the original $40, the new $20, and a negative $20 adjustment. It should not erase the first $40.
How to Track Rewardful Partner Downgrades
The reliable workflow starts in Stripe and ends in your reporting ledger. Rewardful should receive the billing changes through its Stripe connection, while your automation records the operational details your team needs.
Rewardful describes its Stripe connection as a two-way Stripe sync. That sync helps keep affiliate records aligned with billing activity. It does not remove the need for your own review controls.
1. Capture the subscription change
Configure your Stripe subscription webhook process to receive subscription updates. Stripe’s subscription webhook guidance explains how subscription lifecycle changes, payment failures, and invoice activity reach your endpoint.
When your endpoint receives a relevant update, capture the raw event before any transformation. Store the Stripe event ID, subscription ID, customer ID, event timestamp, old plan reference, new plan reference, and current subscription status.
Do not invent a Rewardful event name for this step. Rewardful provides webhooks, but do not build production logic around a downgrade-specific event name unless it appears in current Rewardful documentation for your account.
2. Compare the old and new recurring value
Calculate recurring value using the recurring price and quantity, not a one-time invoice total.
A monthly plan that drops from $300 to $150 is straightforward. An annual plan that shifts to monthly billing needs more care. The immediate invoice may be lower, but the comparison must use a common monthly value.
Flag the record when one or more of these conditions applies:
- The recurring plan amount falls.
- The subscription quantity falls.
- A scheduled update will reduce future recurring value.
- A plan change creates a lower commission basis.
- The subscription becomes canceled instead of active.
Write the result as Detected first. Do not label it confirmed until your process checks attribution and billing timing.
3. Match the customer to the Rewardful referral
Use a durable customer mapping. The safest keys are Stripe customer ID, Stripe subscription ID, and your internal account ID. Add the Rewardful partner or referral reference once you identify it.
Do not match records by email alone. Emails can change, duplicate across test accounts, or belong to a billing contact rather than the product user.
If no Rewardful referral appears, mark the record Needs Review. Do not assign a partner based on a guessed name, campaign, or last browser session.
Validate Commission Impact Before You Report It
A detected downgrade is not always an immediate commission reduction. Timing matters.
Rewardful’s Stripe integration adjusts commissions for billing changes, but the amount should match the billing result. The Rewardful listing in the Stripe Marketplace also states that commissions adjust for downgrades, upgrades, cancellations, refunds, and trials.
Check the effective billing date
An immediate downgrade can create a prorated invoice or credit. A scheduled downgrade may leave the current commission unchanged until the next paid renewal.
Use these review states:
Detectedmeans Stripe shows a lower future subscription value.Pending Billingmeans the plan change exists but no affected invoice is final.Confirmedmeans the revised billing outcome and referral match.Correctedmeans a prior commission or forecast required an adjustment.Heldmeans the payout impact needs finance review.
This structure stops revenue operations from treating a scheduled change as a completed loss.
Compare plan values with paid invoices
Plan value explains the expected direction. The paid invoice explains the financial result.
Check discounts, credits, taxes, proration, and refunds before you calculate a commission difference. A percentage-based commission should follow collected revenue under your program terms. Fixed rewards need a written policy because partial plan changes may not map cleanly to a fixed amount.
Keep a separate field for expected commission impact and confirmed commission impact. That distinction protects your forecast from early assumptions.
Notify the Right Team at the Right Time
Not every downgrade deserves an affiliate email. Too many alerts create questions before the billing result is final.
Route the record based on its status and financial impact.
Give each owner one job
Revenue operations owns record quality. It checks the Stripe change, partner mapping, duplicate controls, and reporting status.
Finance reviews any downgrade tied to a paid commission, a negative partner balance, or a manual recovery decision. Do not assume a commission already paid to a partner will reverse automatically.
The affiliate manager handles partner communication. Customer success or the account owner may need visibility when a high-value referred customer downgrades, but they should not edit the commission record.
A clear internal alert includes the partner name or ID, customer account ID, old and new recurring values, effective date, referral reference, commission status, and assigned owner.
Send partner updates only after confirmation
When a confirmed downgrade affects a future payout, send a short notice. Include the affected billing period, revised commission amount, and the rule that caused the change.
Do not expose customer details the partner does not need. Do not say a payout was reduced because a customer “could not afford” a plan. State the billing outcome and the commission calculation.
If the commission was already paid, send no recovery notice until finance approves the action under your affiliate terms.
Stop Duplicate and Misleading Updates
Webhook systems retry. Subscription changes can also arrive close together, especially when a customer changes plans, receives a credit, and then cancels.
Without controls, one downgrade can create three internal records and three alerts.
Use idempotency controls
Store every Stripe event ID you process. Before writing a new record, check whether that event ID already exists.
Also create a business-level deduplication key using the subscription ID, effective change date, old plan reference, new plan reference, and change type. The event ID blocks technical duplicates. The second key catches repeated business updates from different events.
Keep raw events separate from approved records. A raw event log is evidence. An approved downgrade record is a finance and partner operations decision.
Correct records instead of hiding mistakes
If a later invoice proves your first estimate wrong, add a correction entry. Include the original record ID, new amount, reason, source invoice, reviewer, and notification status.
This matters most when a partner asks why a projected $40 commission became $20. Your team should be able to show the original subscription state, the later billing change, and the final calculation.
Rewardful partner downgrades become misleading when reports mix projected reductions, confirmed invoice changes, and paid payout corrections in one number. Keep those stages separate.
Troubleshoot Common Downgrade Tracking Problems
Most issues fall into one of four categories: missing attribution, duplicate events, timing differences, or payout status.
The Stripe change has no matching partner
Check whether the Stripe customer was linked to Rewardful at the original conversion. Review your tracking setup, referral metadata, and customer mapping rules.
Rewardful’s explanation of how it uses a Stripe account can help you confirm the billing connection. Do not manually attach a partner without evidence from the original referral.
The same downgrade appears twice
Check the Stripe event ID first. Then compare the subscription ID, effective date, and plan references.
If the records describe the same change, mark the later entry as duplicate and retain it in the raw log. Do not delete evidence or send a second partner notice.
The expected and actual commission differ
Review the paid invoice, not only the displayed plan price. Proration, a partial refund, a coupon, or a delayed effective date can change the result.
If the customer has not reached the affected billing date, keep the downgrade in Pending Billing. If a completed payout is involved, move it to Held for finance review.
Final Control for Reliable Downgrade Reporting
A downgrade workflow works when it preserves facts instead of overwriting them. Stripe confirms the subscription and invoice change. Rewardful reflects the commission adjustment. Your ledger connects both records to the correct partner and payout decision.
Track Rewardful partner downgrades as detected, confirmed, and corrected records. That gives finance accurate numbers, gives partners clear answers, and gives your team a record it can reproduce.
