Question 1

What is entitlement mapping?

Accepted Answer

Entitlement mapping connects store products (like com.yourapp.pro_monthly on Google Play or pro_monthly on the App Store) to a single internal ID like 'pro'. Tierux normalizes all purchases into entitlement state, so your backend checks /api/v1/entitlements/{userId}/{entitlement} regardless of which store the user bought from.

Question 2

Can one entitlement map to multiple store products?

Accepted Answer

Yes. You can map multiple Google Play products and App Store products to the same entitlement ID. This is useful for annual vs monthly subscriptions, regional pricing variants, or platform-specific product IDs — all granting the same feature access.

Question 3

How does Tierux handle cross-platform entitlements?

Accepted Answer

A user who subscribes on Android and later switches to iOS keeps their entitlement (if the same entitlement ID maps to products on both platforms). Tierux tracks the most recent active subscription across stores and returns the correct state regardless of platform.

Capability	With Tierux	Without Tierux
Product-to-entitlement mapping	Configurable server-side — one mapping per product	Custom DB tables, manual sync
Cross-platform normalization	Android and iOS products → same entitlement ID	Separate code paths per store
Multi-product entitlements	Monthly, annual, regional → one entitlement	Custom grouping logic required
Entitlement API	GET /api/v1/entitlements/{userId}/{entitlement} — one call	Build your own state machine
AI-agent configuration	`create_product_mapping`: `{ productId, entitlementId, productType, appId? }`	Manual mapping in config or code
Pricing	Flat monthly fee, no revenue tax	% of MTR or dev time

Entitlement mapping

Server-side entitlements

Purchase verification

Quickstart docs

Map products to entitlements, check access in one call