Iaptic allows you to chose between different entitlement strategies for associating purchases with your application users.
What is an entitlement strategy?
It defines which user have access to a particular purchase.
Why do we need this?
Sometime, the same App Store or Google Play account is used on many devices. In other cases, a device is shared by different persons. As such, many of your users might present the same purchase receipt. The entitlement strategy defines which of those users have access to the content: all of them, only the first or last to present the receipt.
What are the possible entitlement strategies?
In short:
- ALL - All claiming users have access to the feature.
- FIRST - Only the first claiming user has access to the feature. Any later claims will be ignored.
- LAST - Only the last claiming user has access to the feature. The previously entitled user loose access.
A claiming user is a user that presents a valid receipt for a purchase through a receipt validation request.
More details below on the different strategies.
All Claimers
This is the default strategy. Anyone presenting a valid receipt for a purchase becomes entitled to it. There is no limit to the number of entitled users for a purchase.
First claimer
With this strategy, only the first user who presented a valid receipt is entitled to the purchase. Subsequent receipt validation requests won't change the entitled user, so you can think of it as a non transmissible entitlement.
The only way to change the user associated with the purchase is to make a manual purchase association request. When using this endpoint, the last request will always have priority. So you can keep changing the associated user many times.
Last claimer
With this strategy, only the last user who presented a valid receipt is entitled to the purchase. Subsequent receipt validation request will always update the entitled user (when it's different from the active one), so you can view it as automatically transmitted entitlement.
You can also change the user associated with the purchase by making a manual purchase association request. Those requests have a higher priority, thus, after you've done this with a purchase, subsequent receipt validation request won't update the entitled user anymore.