Subscription
Pronunciation: sub-SKRIP-shun
Definition
A subscription is an agreement that gives a customer continuing or repeated access to a product, service, or entitlement under defined terms. It usually has a start date, plan, price, billing interval, renewal behavior, and cancellation rules, but payment and access do not always change at the same moment. Reliable systems track the subscription lifecycle separately from invoices, payment attempts, customer balances, and product access.
Overview
A subscription is an agreement that gives a customer continuing or repeated access to a product, service, or entitlement under defined terms. Its practical use in billing and recurring commerce depends on a clearly defined scope, authoritative record, responsible owner, and connection to the underlying customer or commercial obligation.
A subscription can remain active while an invoice is open, and a payment can succeed without proving that the correct entitlement was granted. A subscription differs from Subscription Payment, which is one collection event, and from Billing Plan, which defines reusable pricing and timing rules. For clearer boundaries, compare Subscription Payment with Billing Plan; they may share identifiers while representing different stages or responsibilities.
Reliable systems track the subscription lifecycle separately from invoices, payment attempts, customer balances, and product access. Operational data should preserve plan versions, effective dates, billing cycle, payment method references, invoices, retries, credits, proration, renewal notices, cancellation requests, and entitlement changes. Clear state ownership, customer communication, audit history, and reconciliation between billing and product systems reduce those risks.
Common failures include unintended renewal, stale pricing, duplicate billing, delayed cancellation, access continuing after entitlement ends, or access being removed after a temporary payment failure. Clear state ownership, customer communication, audit history, and reconciliation between billing and product systems reduce those risks.
Governance for Subscription should assign ownership for pricing, calculation, collection, entitlement, communication, and accounting. Teams should test retries, corrections, cancellations, upgrades, downgrades, refunds, provider outages, and events arriving after a billing period has closed, while preserving the evidence behind each adjustment. The audit scope should also preserve its distinguishing context: A is an agreement that gives a customer continuing or.
Key Takeaway
A subscription is a customer-specific lifecycle agreement, so billing, payment, renewal, cancellation, and access states must remain distinct and traceable.
Sources
- How Subscriptions Work — Stripe (2026-08-02)
- Subscription Analytics — Stripe (2026-08-02)