Problem
Canceled subscription, but premium access remains
A customer cancels their Stripe subscription, but your application still grants premium features. This is one of the most common revenue leaks in SaaS.
Why this happens
When a customer cancels a subscription in Stripe, the subscription may retain status: active with cancel_at_period_end: true until the paid period ends. This is expected behavior — the customer paid for the full period. A genuine mismatch occurs when Stripe shows status: canceled (period ended) but your application still grants premium access.
SubSync Guard distinguishes between cancel_at_period_end (legitimate continued access) and canceled (period ended, access should be revoked). Only the latter is flagged as a finding.
Common causes
- Missed webhook: The
customer.subscription.deletedorcustomer.subscription.updatedwebhook was not delivered, was dropped, or failed silently. - Stale cache: Your application caches subscription status and does not invalidate it after a cancellation.
- Delayed processing: Webhook processing is asynchronous and may lag behind the Stripe state change.
- Grace period logic: Your application grants access until the period end, but the period end calculation is wrong.
- Multiple subscription records: The customer has multiple subscriptions and your system checks the wrong one.
How to detect it
Compare the Stripe subscription status with the application's access state for every customer:
- Export all active Stripe subscriptions (status:
active,trialing,past_due). - Export all users with premium access from your application.
- Find customers where Stripe says
canceledbut your app sayspremium. - These are your revenue leaks — customers receiving paid features without paying.
How SubSync Guard helps
SubSync Guard connects to your Stripe account (read-only) and your application's entitlement snapshots. It runs reconciliation automatically and produces advisory findings for every mismatch, including canceled-but-active access. Findings include both identifiers, snapshot times, and the policy applied.
No automatic revocation — your team decides what to change. Every finding is reviewable, resolvable, and auditable.
Recommended fix steps
- Verify webhook delivery in Stripe Dashboard → Developers → Webhooks → Events.
- Check for failed or unprocessed events, especially
customer.subscription.deleted. - Implement idempotent webhook handling with replay protection.
- Add a reconciliation job that periodically compares Stripe state with app access.
- Set up alerts for new mismatches.