grace-period-handling

Grace period management keeps subscriptions active during payment failures by applying a configurable window that allows continued access while Stripe retries past_due payments in the background. It automates transitions and access banners until expiry enforcement.

Automated past_due to unpaid transitions use a state machine to enforce access revocation when the grace period expires. This lifecycle management ensures users retain access during the grace window but lose it immediately upon expiry.

Automated milestone emails notify users before a subscription grace period expires by sending scheduled reminders at 7, 3, 1, and 0 days remaining. This ensures users are warned to update their payment methods before access revocation.

Grace period handling supports enterprise extension scenarios through configurable workflows and audit-ready extension logging. This allows manual extensions for enterprise customers while maintaining a complete audit trail of all changes.

Dynamic grace period end calculation integrates directly with Stripe retry schedules to adjust the expiry date automatically. This aligns the access revocation enforcement window with the actual payment retry attempts.

A past_due state requires a grace period to prevent immediate service disruption from temporary payment hiccups. Allowing continued access while Stripe retries failed charges helps recover revenue and avoids churning users over transient failures.