In this guide 7 sections
Subscription e-commerce needs a system that handles plan changes, pauses and cancellations, and retries failed recurring payments with a clear customer message. It also keeps the pick list, the invoice and the login entitlement in step with the current subscription state. Most of the real complexity sits in renewals that do not go smoothly, so design and test those first.
Plan rules: renewal, pause, cancellation and entitlement
Settle renewal rules before coding. A renewal can keep the same plan and price, apply a scheduled price rise or prorate a mid-cycle upgrade, and each option rewrites the invoice logic and anchor date. Pausing is a business decision with technical consequences: the maximum pause length, the grace period for payment, and whether the subscription resumes or auto-cancels when the pause ends.
Entitlement is what a customer may actually use right now, such as service access or the next box in the schedule. Tie it directly to subscription state, never to a nightly spreadsheet export that can drift away from billing and leave paying customers locked out.
Recurring payment and notification requirements
Recurring payments in India fall under the Reserve Bank of India’s E-mandate Framework for Digital Payments, 2026, as described in the notification verified on 2026-09-08. Registering a mandate needs additional factor authentication, and so do recurring debits above ₹15,000 per transaction, which is a real constraint on how you price monthly plans. The higher ₹1,00,000 exemption threshold applies only to categories such as insurance premiums and mutual fund payments, not to general subscription billing.
Check current rules with a chartered accountant or legal adviser before you fix the price tiers or design the payment screens. Find the limit before launch. The same framework is described as requiring a pre-debit notification at least 24 hours before each recurring charge, so choose email, SMS or WhatsApp early. Build it in from day one.
Failed collections, retries and mid-cycle changes
A failed renewal should not cancel a subscription on the first attempt, because the cause is usually an expired card, a reissued card number or a thin balance. Involuntary churn is not intent. Run a retry schedule of three attempts spaced over a week, and send a dunning email at each stage with a link to update the card on file.
Mid-cycle changes include upgrades, downgrades and a new delivery address on a physical box, and each needs pro-rata credit rules and a courier cut-off date built into the system. Agents should not improvise credits. Manual handling stops scaling.
Fulfilment, invoices and access in sync
For physical subscriptions, a successful renewal charge should trigger the pick list, the SKU-level stock deduction and the courier label with no manual step in between. Invoices are generated per billing cycle, flow into the accounting system and show what was actually charged, including any discount or proration, rather than the plan’s list price.
Access-based subscriptions, such as software, content or a service tier, need entitlement to change the moment payment status changes, with no hourly or nightly delay in between. Delays lock out paying customers. It can equally leave a lapsed customer with access that nobody is billing for, which quietly costs revenue every month.
Testing the entire lifecycle, not just the happy path
Test the full lifecycle: signup, first charge, successful renewal, failed renewal with retry, pause, resume, cancellation and any refund or proration case. Several interact in awkward ways. Two worth testing explicitly in a sandbox are a cancellation during an active retry window and a pause requested right after a declined card.
Take a coffee roaster shipping monthly bags. If a renewal fails on the charge date, three decisions must be made together: the retry sequence, the customer message, and whether that month’s bags ship or wait. Case by case is the trap.
Subscription lifecycle state diagram
A state diagram covering signup, active, paused, past-due (with retry attempts), cancelled and resumed states. The billing, notification, fulfilment and entitlement action triggered at each transition is marked explicitly. A build plan can then be checked against every real path a subscriber might take.
Open a blank worksheet to printQuestions owners ask
What happens when a renewal payment fails?
It triggers a defined retry sequence and a customer message, never an instant cancellation or a silent failure that nobody notices until the monthly revenue report looks wrong. Choose the retry window and the channel deliberately. Default gateway behaviour rarely matches what your customers expect, so write the rule down and test it against a card that really does decline.
Can customers pause subscriptions?
Pausing is a commercial choice, not a technical limit, and many subscription businesses offer it as a cheaper alternative to losing the customer entirely. Build the rules in early. Set a maximum pause length and decide what entitlement the customer keeps during the pause and what happens automatically when it ends.
Should invoices follow the plan’s list price?
No, invoices follow the amount actually charged. Each one should include any discount or proration applied that cycle, so the accounting reconciliation matches the payment gateway statement line for line. Chargebacks start with confusing invoices.
Sources
- Reserve Bank of India — Digital Payments – E-mandate Framework, 2026 — verified 8 Sept 2026