PROBLEM · PAID, BLOCKED
Paid, but blocked. The most expensive kind of silence.
A paying customer who cannot use the product churns quietly. The billing system says active. The product says free. Nobody notices until the ticket arrives.
What this problem looks like
The subscription is active or trialing in Stripe. The entitlement record in the application is missing, disabled, or set to a lower tier. The customer experiences a paywall or a degraded experience despite having paid.
- Webhook delivery failed or was delayed
- Entitlement provisioning logic changed during a deploy
- Customer-to-user mapping broke after an account merge
- Manual override was removed during a cleanup
- Trial-to-paid transition did not update access
How to detect it reliably
Compare the billing snapshot against the entitlement snapshot using a stable identifier. A finding is raised when an active or trialing subscription has no matching active entitlement. The finding carries both identifiers and both snapshot times.
- Use a stable customer or account identifier, not email alone
- Require complete snapshots on both sides before comparing
- Apply an explicit policy for trials and grace periods
- Record the snapshot times so the comparison is reproducible
What to do next
Verify the entitlement mapping for the affected customer. Restore access if the mapping is correct, or correct the subscription record if the billing state is wrong. No automatic change is made by the tool.
Frequently asked
Is this always a bug?
No. It can be a grace period, a manual grant, or an intentional hold. The point is to surface it for review, not to assume.
How often should I check?
On a schedule that matches your sync cadence. The cron-sync function iterates connected workspaces and reconciles after each sync.