Skip to content
ADVISORY RECONCILIATION · STRIPE ↔ ENTITLEMENTSRun the browser-only CSV audit

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.deleted or customer.subscription.updated webhook 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:

  1. Export all active Stripe subscriptions (status: active, trialing, past_due).
  2. Export all users with premium access from your application.
  3. Find customers where Stripe says canceled but your app says premium.
  4. 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

  1. Verify webhook delivery in Stripe Dashboard → Developers → Webhooks → Events.
  2. Check for failed or unprocessed events, especially customer.subscription.deleted.
  3. Implement idempotent webhook handling with replay protection.
  4. Add a reconciliation job that periodically compares Stripe state with app access.
  5. Set up alerts for new mismatches.

Authoritative sources