A subscription is a recurring obligation, not a checkout discount. This article covers lifecycle, collection, failure, proration, cancellation, refunds, tax invoicing and measurement, and gives you a model checklist before the build.
A subscription is not a discount on the checkout page. It is a recurring obligation: an amount charged on a date, a possible failure, a plan change, a cancellation, a refund, an invoice, and a record that has to match the accounts. Starting from the storefront produces a beautiful snapshot of a model that has not been decided, then every question about access, billing and cancellation returns to a decision nobody made.
In Saudi Arabia the model adds layers: card payment and 3-D Secure, a correct tax invoice, a clear cancellation policy, and possibly an annual plan or a free trial. Each choice changes the states of the system, and each state has to be explainable to the customer, the accountant and support. An interface that does not show those states clearly creates support tickets that only a developer can close.
A subscription is a state, not a button
Before designing the pricing page, draw the subscription lifecycle. Which states can it be in? Trial, active, past due, grace, paused, cancelled, expired. Every state needs an access rule, a message, and an accounting action. A system that knows only two states treats the rest as errors and fixes them by hand every month.
Entitlement is not the same as state. A subscription can be active with a limited entitlement, or cancelled with access that continues to the end of the period. Separate what the customer paid for from what they can use, and write the rule down. That separation stops support from granting manual access every time, and stops the system from cutting off a customer who has paid.
Recurring collection
Do not store card data. Use a token issued by the payment provider, and store the token rather than the number. 3-D Secure adds a step on renewal or when the card changes, and it needs a path that returns the customer to the subscription after verification rather than to an error page. Test that path on mobile, because many renewal attempts happen in an app or an embedded browser.
Failure is not an exception; it is an expected state. Define the number of attempts, the intervals, the messages, the grace period, and when access is suspended. Dunning is not a repeated email; it is a sequence of decisions: what we send, when, what we grant, and when we stop. Make card updates possible before failure, not only after it, because a customer who is travelling or changing banks needs a clear route.
Proration and change
Proration is the most underestimated part. If a customer upgrades mid-month, what do they pay? Do they get access immediately? Is the adjustment a credit note or an extra invoice? If they downgrade, do they keep access until the end of the period? Set the policy before the build, because every choice changes the invoice and revenue recognition.
Do not confuse a discount with a credit note. A discount changes the selling price; a credit note reverses an issued invoice. In tax invoicing, each has its own document and effect. Write the tree: event, document, entry. Test it with the accountant, not only with the developer, because an error that appears in the financial report does not appear in the customer interface.
| Event | What the customer sees | What the system must do | Accounting effect |
|---|---|---|---|
| Trial start | Temporary access, no charge | Store the card or defer it, and start the clock | No revenue yet |
| Renewal | An invoice and continued access | Attempt collection, issue the invoice, update the state | Revenue and a tax invoice |
| Failed payment | A notice and a chance to correct | Retry, grant a grace period, suspend gradually | Amount pending |
| Card update | A new method saved | Secure token, verification, next retry | No effect |
| Upgrade | Immediate access and a prorated difference | Calculate the difference, issue an invoice or a credit note | Additional revenue or credit |
| Downgrade | Access until the end of the cycle | Schedule the change, do not refund the difference in cash | Deferred credit |
| Cancellation | Access until the end of the period | Stop renewal, do not delete immediately | Deferred revenue |
| Refund | Money returned | Credit note, state update | Revenue reduction |
Cancellation, refunds and entitlements
Cancellation is a customer decision, not a technical event. Define when renewal stops, when access ends, whether unused amounts are refunded, and what happens to data after cancellation. Immediate cancellation that cuts access mid-period punishes the customer; access that continues beyond the paid period complicates the accounts. A clear policy protects both sides from personal interpretation.
A refund needs a policy and a document. A full refund, a partial refund and a credit each have a different effect. Entitlements should be withdrawn by the same policy: what happens to additional users, storage, reports and integrations? Write it on the pricing page and in the contract, and do not leave it to support judgement. A customer who knows what they lose on cancellation trusts you more, not less.
From reading to shipping
Want this built, not just explained?
Bring us the problem behind the article. We will tell you what it takes, what it costs, and whether we are the right team.
Accounting and tax invoicing
E-invoicing makes the invoice a system event rather than a file created by hand. Every cycle has an invoice, every credit note has a document, and every adjustment has a reason. Tie the subscription to the invoice and to revenue recognition, and define when an amount is deferred revenue and when it becomes recognised revenue. These are not finance details left to the end; they are the shape of the data model.
Work with the accountant before building the model. Questions such as revenue timing, free-trial treatment, tax on an upgrade and refund handling are not solved in code. The system executes the policy; it does not invent it. If the policy changes, the configuration should change rather than the system being rebuilt. Also review the e-invoicing readiness guide before the rules harden in code.
Measurement, and platform versus custom
Measure a subscription with more than one number. Cancellation rate alone is not enough: separate voluntary from involuntary churn, separate customer loss from revenue loss, and track upgrades and downgrades. The cohort that started in the same month shows what an overall average hides, because first-month behaviour differs from second-year behaviour.
A ready platform fits standard billing: a monthly plan, simple access, and built-in reports. A custom build fits complex entitlements, usage-based access, and deep integration with your product. The question is not which is stronger, but where the platform stops expressing your model. Review SaaS platform engineering, and the earlier post on multi-tenant SaaS architecture, before you decide.
Even a subscription starts with a payment form. Baymard's 50-study average puts cart abandonment at 70.19%, 22% of users have abandoned because checkout was too long or complex, and the average form has 11.3 fields. A subscription does not exempt you from that rule: every extra field before sign-up is a chance to lose the customer before the relationship begins.
The model checklist before the build
Use this list in the first meeting with product, finance and support. If a line has no written answer, the model is not defined yet.
The lifecycle: draw every subscription state, its message and its access rule.
Entitlement: separate it from payment state, and write what the customer can use.
The token: use the card token, and never store card data in your system.
Failure: define attempts, intervals, messages, grace and suspension.
Proration: write the upgrade and downgrade policy and the document each produces.
The invoice: tie every cycle to a tax invoice and a credit note when needed.
Cancellation: define the stop time, the refund and the entitlement withdrawal.
Measurement: separate voluntary from involuntary churn and revenue loss.
Frequently asked questions
Does every subscription need 3-D Secure? It depends on the payment provider, the transaction type and the requirements. Test the full path on renewal and on a card update, and do not assume it works because the first payment succeeded.
Do we issue an invoice for every renewal? Usually yes, because every collection needs a document. Review the issue timing and credit-note handling with your accountant before the build.
What do we do when payment fails? Retry on a defined sequence, send a clear message, grant a grace period, then suspend access. Do not delete the account immediately.
Do we refund on cancellation? That is a policy decision, not a system decision. Write it clearly, apply it consistently, and show it before purchase.
Do we build or use a platform? If plans and entitlements are standard, a platform is faster. If access is tied to usage or to your product, a custom build may be clearer.
Sources
- Baymard: cart abandonment rate — the 50-study 70.19% average.
- Baymard: checkout usability — 11.3 fields on average, and 22% who abandoned because checkout was too long or complex.
- Rasad SaaS platform engineering — scope, architecture and delivery.
- Multi-tenant SaaS architecture — how data and entitlements are separated.
- Rasad's published price bands — the figures this article works from.
Cover image: Artem Beliaikin from Moscow, Russia, CC BY 2.0, via Wikimedia Commons.

