Entitlement

Definition

An entitlement is a normalized, server-side record that answers one question: "Does this user have access to this feature?" It decouples the store's purchase model (one-time, subscription, consumable) from your app's feature-gating logic. When your backend verifies a Google Play purchase token or an Apple JWS transaction, it stores the result as an entitlement — usually with a state (active, expired, grace period) and an expiry date.

Entitlements are the foundation of server-side purchase verification. Instead of trusting the client to report whether a user paid, your backend checks the entitlement record on every gated request. This eliminates class of attacks where a modified client fakes a "verified" response.

Examples

• A user subscribes to "Pro Monthly" on Google Play. Tierux verifies the purchase and creates an entitlement pro with state active and an expiry date 30 days from now. Every backend API call for gated features checks this record.
• An iOS user buys a "Remove Ads" one-time product. The entitlement no_ads is set to active with no expiry — it lasts forever.
• A subscription lapses due to a failed payment. The store sends a webhook; Tierux marks the entitlement as expired. The next time the user opens the app, premium features are gated.