The in-app purchase experience for a customer (HTML)
This topic describes how an in-app purchase looks to a customer.
Note The process and screenshots in this topic refer only to the in-app purchase experience that the Windows.ApplicationModel.Store API provides. Other, third-party commerce APIs might provide a different experience. If you use a third-party commerce API for in-app products, be sure to review our certification requirements.
For your customer, the purchase of an in-app product starts when your app prompts the user with the available offers. When you design your app, you decide where you want to present products for purchases so that products are easy to browse and purchase within available UI components.
When the customer picks a product to purchase from your app, the Windows.ApplicationModel.Store queries the Store for the current info.
Then it displays the confirmation prompt.
The description that the confirmation prompt displays is the description that you entered in the Description page for the in-app product. For more info about this description, see What to include in your app's description.
After the customer clicks Yes, the customer must sign in to their Microsoft account to confirm their identity. The customer must do this for each in-app product to prevent fraudulent and unintentional purchases.
After the purchase and the customer's identity have been confirmed, payment for the product is processed using the customer's default payment method. The customer configures their default payment method in their Store settings.
And, the transaction completes. The customer returns to their app after they click Close.