Skip to main content

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.


IDAuto-generated on app creation. 16 alphanumeric characters uniquely identifying your app.


NameApp name. Used for display purposes in your dashboard and apps list.
User BehaviourDisabled : 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.
WebhookINDIE plan and higher. Your server endpoint called on each successful validation. More details in the Server Webhook documentation.

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

Bundle IDYour unique application bundle identifier registered on the App Store.
License KeyExported private key for accessing store validation API. More details in the Store documentation.
Account IDAccount identifier or service account. More details in the Store documentation.

Always keep the bundle identifier and other platform settings up-to-date, otherwise all incoming receipt validation attempts will fail!