Concept/how-to
Subscriptions and Recurring Access
Configure recurring products, customer access, payment state, and supported bundle changes.
Recurring payment and recurring entitlement
Subscriptions connect monthly/yearly pricing and Stripe checkout to ongoing product access. A customer library can show the recurring products and supported account actions. Plugin validation must use the current entitlement state rather than a one-time stored purchase boolean.
Subscription checkout currently uses Stripe, not PayPal. Trials, grace, cancellation, and access timing depend on the configured product/bundle and supported lifecycle. Do not assume all products share one policy.
SoundSync
Lifecycle distinctions
| State or action | What to check |
|---|---|
| Active / renewed | Provider confirmation and the current paid access period |
| Failed payment / grace | Configured grace and provider events; not permanent offline access |
| Cancellation | Effective date and whether access continues through the paid period |
| Expired / revoked / refunded | Product entitlement and package-specific enforcement |
| Plan change | Preview, conflicts, proration, immediate/scheduled effect, and confirmation |
| Manual grant | Access grant versus customer-authorized billing setup; not permission to charge silently |
Bundles and installments are different
A subscription bundle groups the permitted recurring products under its versioned offer and supported plan-change flow. A one-time product bundle is another commerce model. Rent-to-own is an installment agreement and currently cannot start production live checkout.
Paid products, subscriptions, and bundles must remain at least $9.99 after discounts, before tax. Free claims follow the redemption model rather than a discounted paid checkout.
Test each transition
Exercise new checkout, renewal, failure/grace, cancellation/reactivation, scheduled changes, refunds, and package access in the actual environment. This source audit does not certify every provider/host lifecycle.
SoundSync