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.