Skip to content
Menu
Discuss your project

Subscription services: renewals, limits and cancellation

DevNomadPublished Updated

A subscription service needs consistent payment records, access periods and usage rules. Pay particular attention to cancellation and failed renewal. Customers should see what they bought, when access expires and how to stop future charges.

Track access and usage separately: Renewal → Access limits → Cancellation

Describe the plan in customer terms

Specify the billing period, features and limits. If you sell usage credits, explain when they are added and what happens to unused credits. Define what a mid-period plan change does.

For example, a customer uses part of an allowance and switches plans. Agree on any adjustment before building it. The plan description must match the calculation implemented in the application.

Keep payment, access and credits distinct

A payment has a status; a subscription has an access period and permissions. Storing them all as a single “active” flag makes it difficult to investigate a payment that did not extend access.

A duplicate payment notification must not credit the same usage allowance twice. Reconcile delayed notifications against the provider’s records. Keep refunds in the transaction history so changes to access or balances can be explained.

Test cancellation and failed renewal

Cancelling the next charge and ending access immediately are different actions. Explain which action the customer is taking. Show the expiry date if the paid period remains available.

Do not promise restored access after a declined payment until the relevant checks succeed. Retry schedules and any grace period depend on the provider and your own terms. Support needs a way to investigate without rewriting payment history.

Calculate costs before offering unlimited usage

If customer actions use paid APIs, measure typical and expensive tasks. Enforce usage limits on the server. Hiding a button alone does not enforce a limit.

Test exhausted credits, interrupted work and retries. Show whether credits were used and whether a result was delivered. To estimate the work, DevNomad needs your plan rules, provider and examples of actions that incur costs.

A product example: catalog access and usage credits

Our SiliconSense project offers catalog access and uses “notes” as credits for Lab tools. Its pricing page includes a one-off purchase and subscriptions with monthly note allowances. Catalog access and the number of available operations therefore need separate rules.

The product must define when the catalog opens, when credits are added and what remains after cancellation. Consult the current plan for the exact terms. This example illustrates the product structure and makes no claim about revenue or payback.