The in-app purchase experience for a customer
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 your app's in-app purchases, be sure to review our certification requirements.
For your customer, an in-app purchase starts when your app prompts the user with the available offers. When you design your app, you decide where you want to present offers for in-app purchases based on the nature of your app and the offers.
When the customer picks an offer to purchase from your app, the Windows.ApplicationModel.Store queries the Windows 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 offer. For more info about this description, see What to include in your app's description and refer to the In-app offer description checklist.
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 purchase to prevent fraudulent and unintentional purchases.
After the purchase and the customer's identity have been confirmed, payment for the purchase is processed using the customer's default payment method. The customer configures their default payment method in their Windows Store settings.
And, the transaction completes. The customer returns to their app after they click Close.
Build date: 4/23/2013