The "gate access on your database, not the redirect" point is the one that bites later. Worth deciding up front what access looks like while a subscription is past_due: Stripe keeps retrying for a while, and cutting access on the first invoice.payment_failed locks out people whose card would have cleared on the next attempt. Keeping access until the status actually moves to canceled or unpaid tends to be kinder and simpler.
Thanks, Paul — that's the failure mode we see most after the first launch week.
We treat past_due / unpaid as a soft gate: keep read access to the customer's own data, block new paid actions, and flip to hard revoke only after the last Stripe retry fails (or after an explicit customer.subscription.deleted). That way a card update during the retry window doesn't strand them behind a login wall that the webhook can't reach.
Worth deciding that matrix (active / past_due / unpaid / canceled) in the same PR as the webhook handlers, not after the first dunning email lands.
Paul Hartness
The "gate access on your database, not the redirect" point is the one that bites later. Worth deciding up front what access looks like while a subscription is past_due: Stripe keeps retrying for a while, and cutting access on the first invoice.payment_failed locks out people whose card would have cleared on the next attempt. Keeping access until the status actually moves to canceled or unpaid tends to be kinder and simpler.