Auto Renewal

When subscriptions were first sold, a customer had to pay again at the end of every cycle. Even someone perfectly happy after a month had to open the checkout screen and retype a card number, so churn came from friction rather than from any change of mind.

The seller's side was no better. Every month somebody pulled a list of unpaid accounts, sent reminder mail, and locked the accounts that never answered, one by one. With 300 customers that job alone ate several days. Meanwhile customers were writing in to ask why a product they were actively using had been locked.

Auto renewal removes that step. Doing nothing becomes the path that keeps the service running, and the customer only has to act to signal the opposite.

At signup the card details go to a payment processor, and the service keeps only a token that points at that card. The real card number never sits in the product's own database; the next charge is made with the token.

When the billing date arrives, the sequence is fixed.

1. Charge the stored payment method on the expiry date.
2. On success, open the next cycle and send a receipt.
3. On failure, don't cut access immediately — enter a grace period. Most failures are a card that briefly hit its limit or a reissued card with a new number, so the charge is retried for a few days while the customer is asked to update the payment method.

Two safeguards belong alongside this: a heads-up notice sent some days before renewal, and a switch that turns the setting off at any time. Without both, auto renewal is indistinguishable from forced continuity. The stakes are highest on an annual plan. One unannounced monthly charge produces a complaint; one unannounced yearly charge produces a refund demand and a card chargeback, and handling that single case can cost more than the customer paid.

"The seven-day notice for annual renewals isn't going out. That's the first thing to fix."

Renewals without advance notice come back as refund requests.

"Auto renewal stays on by default, and the off switch goes on the first settings screen."

Keep the convenience as the default, but don't hide the exit.

"Half of this month's churn isn't cancellation — it's failed renewal charges."

We're losing customers who never meant to leave, so the retry logic needs work.

Pagedeck revisited this setting after adding an annual plan alongside the monthly one. Grace read the support tickets from the first month annual renewals ran and split the advance notice into two sends, seven days out and one day out. Sofia then checked the auto-renewal clause in enterprise contracts against what the product actually does. A contract promising 30 days' notice while the product sends it seven days out means the paper and the software disagree.