Subscription guide
HISE Subscription Access
Validate recurring entitlement separately from account browsing.
Check the relevant access period
A subscription record and its products determine the recurring access being validated. My Products may show a subscription while the runtime still needs a current product access decision. Store browsing is not an audio license.
Exercise supported checkout, renewal, cancellation, and expired-access states against the exact HISE variant and exported build. Do not infer every refund or failed-payment edge case from the source workflow alone.
Offline and rejected access
HISEScript grace requires prior valid state and follows its configured/server expiry limits. A confirmed expired or revoked state must not become offline-valid. Native HISE follows its own generated contract; do not copy a HISEScript or JUCE rule across variants.
Recurring access versus earned ownership
A subscription bundle can use access fulfillment or keep_products fulfillment. Access follows the current recurring entitlement. Keep-products ownership is earned from eligible verified paid invoices and the products in each payment's catalog snapshot; an unpaid trial does not grant permanent ownership.
Stopping future renewal can leave previously earned ownership intact. Refunding an eligible initial payment or reconciling a dispute affects rights attributable to that payment, not unrelated purchases or independent grants. Check the product entitlement returned by validation rather than locking every product just because one subscription is canceled.
Validate access after renewal or recovery
An unpaid renewal has a 14-day recovery window. At an unresolved rental deadline, the license is suspended while the subscription and billing continue. Reconciliation of all outstanding payments is required for restoration; a newer paid invoice does not clear older arrears. A keep-your-products plan can end while products already earned from unreversed qualifying payments remain owned. Read the returned product entitlement rather than locking every owned product because one subscription has a payment issue.
Billing recovery and offline permission are different. JUCE 0.7.3 uses verified signed offline grace or successful online renewal at startup. HISEScript grace needs prior valid access within its allowed expiry; a confirmed denial never becomes offline-valid. Native HISE follows the generated native contract.
SoundSync
Recurring billing details
Renewals and recovery
Pricing notices, saved payment updates, reminders, and customer cancellation.
Permanent gifts and paid subscription ownership
A timed manual keep-products grant gives the customer permanent ownership of the products included when the developer makes that grant, without a payment. That original product snapshot remains owned after subscription cancellation, expiry or incomplete billing setup. Explicit developer access removal can revoke the grant. New products added later are not retroactively included.
A lifetime manual grant instead provides complimentary ongoing subscription access; it is not the timed-grant ownership model or evidence of a paid invoice. Ordinary access-only grants and unpaid checkout trials also do not create paid ownership.
Paid keep-products invoices establish their own product snapshots. Refunding or reversing a paid purchase affects that purchase, not an independent manual ownership grant. Future paid subscription benefits still require the separate billing setup, preview and customer confirmation; a gift is not permission to charge a card.
