Subscription billing: connect renewals, changes and cancellation

Which states must the business keep separate?

Link the subscription, billing period, invoice, payment and delivered entitlement without reducing them to one status.

Stripe’s lifecycle documentation distinguishes subscriptions, invoices and payments. With invoice-based collection, a subscription can already be active while its first invoice remains unpaid. That is a concrete reason not to interpret every active status as proof of money received.

Reference: Stripe: how subscriptions work

Describe the offer first: product or service, quantity, price, currency, start, billing interval and change policy. Record the service period and any shipping schedule separately. Monthly billing does not inherently mean one parcel each month, and a payment date need not describe the entire period the customer is entitled to use.

Retain a clear relationship between each period and its invoices, payment outcomes and delivery. Support should distinguish continuing entitlement from an unpaid collection and from a cancelled agreement. A single flag trying to represent all three will eventually give another team the wrong instruction.

What should a renewal authorise the business to deliver?

Define one release decision for each period and make repeated messages recognise the same work.

Specify when an invoice is created, when collection is attempted and which confirmed outcome permits service or dispatch. A digital entitlement and a warehouse order have different operating requirements. The release policy needs to reflect your actual agreed terms rather than a convenient event name.

A failed collection can produce several notifications and later attempts. They normally concern the same outstanding invoice, not several subscription shipments. Use stable period and delivery references so that repeated payment confirmation cannot generate a second package. Show support the relationship without requiring it to interpret raw event logs.

Include different month lengths, the agreed time zone and changes arriving near the renewal boundary. If billing and fulfillment operate in different zones, identify which timestamp determines the period. A repeatable cut-off rule is more useful than a vague promise that everything happens at midnight.

Prevent repeat payment events from creating another fulfillment order

How should upgrades, downgrades and quantity changes be charged?

Choose the effective date, calculation and collection timing as three explicit decisions.

Stripe supports proration previews, but negative prorations are not automatically paid back and positive ones are not necessarily collected immediately. Ask what a proposed change creates on the invoice and what actually moves through the payment account.

Reference: Stripe: prorations

For each change type, agree whether it applies now or next period, whether unused time is credited, and whether an adjustment is billed now or later. Decide when the customer receives the changed service. Immediate charging with delayed access is a different outcome from changing both at the next renewal.

Present the expected amount and dates before confirmation where they can be determined. Test discounts, tax, existing credits and unpaid prior invoices in the configured system. Reprocess the same change reference and verify that it does not add a second equivalent adjustment. A usable change history matters as much as a price-edit screen.

What happens when a recurring collection fails?

Coordinate retry policy, customer action and the decision about continuing service.

Stripe documents configurable retries and exceptions, including missing payment methods and certain hard declines. A generic schedule cannot recover every invoice. Verify the supported payment methods and account settings for the actual implementation.

Reference: Stripe: automate payment retries

Distinguish a temporary failure, a required customer action and an unknown result. Assign who contacts the customer, checks an updated method and decides what happens after the planned attempts end. Support and fulfillment need the same business decision even if their tools display different technical statuses.

Define whether an unpaid period allows a grace interval, pauses service or ends future delivery. Do not let an unnoticed default determine that policy. Then pay an outstanding invoice through another supported route between scheduled attempts. The later collection should recognise that the balance has already been cleared.

Separate subscription collection retries from cross-processor routing

What should cancellation do to billing and remaining service?

Record the request and effective end separately; treat refunds as their own operation.

Stripe supports immediate and scheduled cancellation. Final invoicing, proration, account credit and a refund are distinct actions. A cancelled subscription is therefore not evidence that a requested repayment has reached the customer.

Reference: Stripe: cancel subscriptions

Record the requested and confirmed end time and what the customer should receive until then. Test a cancellation near renewal, then withdrawal of a scheduled cancellation. If a parcel has already shipped, the required handling differs from stopping the next unreleased shipment.

Align the technical workflow with the terms and cancellation requirements applicable to the offer. Preserve the confirmed decision in the account and support record. Removing a stored payment method, cancelling an invoice and ending the commercial agreement must not silently become interchangeable actions.

Keep refunds distinct from order and stock adjustments

Which acceptance tests should cover the full lifecycle?

Advance through several periods and awkward timing cases instead of approving only the first purchase.

Stripe provides Billing test tools including test clocks and simulated payment outcomes. They help exercise time-dependent behaviour, but your own service and dispatch rules still need checking. Use an approved testing environment and designated test records.

Reference: Stripe: test your Billing integration

Adapt this editorial matrix and retain the period, invoice, payment state and expected customer entitlement for each case. Finance and the team delivering the product should approve their own outcomes. Keep unexplained differences visible instead of accepting the entire integration because an invoice appeared.