Solution skill
Stripe event: customer.subscription.updated, the churn signal hides here
Complete solution
Shows how to fix stripe event: customer.subscription.updated, the churn signal hides here. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
This event fires on any subscription change: plan switches, quantity changes, trial to active transitions, billing tweaks. New price id means a plan change: adjust entitlements. New quantity means a seat change: adjust seats. Check cancel\at\period\_end.
When to use
You are seeing this: Most receipts are routine. Use this skill when you run into "Stripe event: customer.subscription.updated, the churn signal hides here".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
customer.subscription.updated: read what changed, especially cancelatperiod_end
This event fires on any subscription change: plan switches, quantity changes, trial to active transitions, billing tweaks. Most receipts are routine. One field is not.
What to do on receipt
- Compare against your stored copy of the subscription. What actually changed? New price id means a plan change: adjust entitlements. New quantity means a seat change: adjust seats.
- Check
cancel_at_period_end. If it just flipped totrue, the customer canceled. They keep access untilcurrent_period_end, but this is your churn moment: log it, trigger your save flow or exit survey now, not at period end. - Check
statustransitions.activetopast_duemeans the renewal payment failed; the dunning events (invoice.payment_failed) carry the detail, but this is where your entitlements logic should notice. - Persist the new subscription snapshot. Return 200.
The trap
Ignoring this event as noise. Then customer.subscription.deleted arrives weeks later and you wonder why a paying customer vanished. The cancellation happened here, weeks ago, when you could still have done something. The other trap: deprovisioning when you see cancel_at_period_end: true. They paid through period end; cutting them off early is a support ticket and a chargeback risk.
Checklist
deletedis the terminal event.updatedwith cancellation flags is the warning. Handle them as a pair.- Quantity and price changes can also arrive here from the Customer Portal. If you let customers self-serve plan changes, this handler is your entitlement sync.
Evidence
Stripe's event reference says customer.subscription.updated occurs whenever a subscription changes (e.g., switching from one plan to another, or changing the status from trial to active). Verified live at https://docs.stripe.com/api/events/types. cancelatperiodend and currentperiod_end are the documented fields for end-of-period cancellation.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_c_CGyJyvJFsEq5c0yko9eg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Stripe event: customer.subscription.updated, the churn signal hides here <span>— Vectle</span></a>