App Setup
The settings in your app define how receipts are processed and user inventory is saved by your app. App settings are available by navigating to Apps > App Options > Edit
. For field definitions please see the list below.
Header
Field | Description |
---|---|
ID | Auto-generated on app creation. 16 alphanumeric characters uniquely identifying your app. |
General
Field | Description |
---|---|
Name | App name. Used for display purposes in your dashboard and apps list. |
User Behaviour | Disabled : Purchase history is not tracked. Use this if you only need server validation on purchase and handle user inventory yourself. Should not be used when offering subscriptions. Transfer : A purchase is linked to the original user. The purchase can be transferred to a different user with a cooldown period of 5 days. Block : A purchase can only exist on the original user. Sending the same receipt from a different user will be blocked. Alias : Multiple users can be associated with one purchase, for a total of 1 original user + 5 alias users. Subsequent alias requests will be blocked. |
Webhook | Paid plan : your server endpoint called on each successful validation. More details in the Server Webhook documentation. |
caution
You should avoid changing the User Behaviour
option in production apps. When using the Block
mode, your app should provide a login system for users to restore their original user ID and associated purchases.
Platform Settings
Field | Description |
---|---|
Bundle ID | Your unique application bundle identifier registered on the App Store. |
License Key | Exported private key for accessing store validation API. More details in the Store documentation. |
Account ID | Account identifier or service account. More details in the Store documentation. |
danger
Always keep the bundle identifier and other platform settings up-to-date, otherwise all incoming receipt validation attempts will fail!