Subscriptions and Recurring Access

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.

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.

Check access in the customer's actual package

Billing confirmation, paid-through access, and permanently earned products are distinct. Verify the final HISE/JUCE or custom client against the intended subscription type. A payment record does not prove that every older offline build has already refreshed its entitlement.

Renewal prices and customer control

Monthly and annual plans renew at their regular list price. A subscription promotion discounts the initial payment only. Supported price increases require at least 30 days of advance notice before taking effect; decreases do not require that waiting period. Applicable checkout tax is recalculated for renewals using the configured tax rules.

Customers can update payment details, cancel at the end of the paid period, and reactivate an eligible plan before it expires. Standalone subscriptions and subscription bundles have distinct account actions. Independent plans can coexist when their product access does not conflict; overlapping plan changes are checked before confirmation.

Manually granted access is not permission to start charging a customer. Converting a manual grant to billing requires the supported payment setup, preview, and explicit confirmation.

A fixed payment-recovery window

An unpaid renewal starts a 14-day recovery episode. Reminder opportunities fall on days 0, 5, 10, and 13, subject to eligibility and delivery readiness. Customers can update their payment method from their account. Eligible automatic collection attempts remain subject to provider limits and the current payment state; this is not a promise of a charge attempt every day.

Access at the end of recovery

If payment remains unresolved at the deadline, unpaid recurring access is canceled. An access/lease subscription stops providing access; products already earned under a keep-your-products plan remain owned unless their qualifying payment is reversed. No new permanent products are earned from an unpaid invoice.

A pending or uncertain payment is reconciled before another charge is requested. Retry, cancellation, and a new checkout must not be used to charge the same renewal twice. Plugin enforcement follows the installed package and its online/offline rules, not an instant remote change to every previously distributed binary.