Purchase of content built into an app

The following diagram illustrates the purchasing process for items that are built-into an app and protected by Nokia using DRM. The green color indicates the secure payment process, which is executed by the in-app purchase API. The diagram does not include a back-end server of your own, which you can use, for example, to gather statistics, verify the purchase, or provide other services.

The purchasing process with DRM protected content is the following:

1. To be able to display the purchasable items to the consumer, the app must know the IDs of the products that are available for purchase. Before you code the app, you use Nokia Publish to identify in-app purchase items. Nokia Publish returns IDs for these items. Use the in-app purchase API to get descriptions for purchasable items, using IDs to identify items.

2. Nokia Store returns the product metadata (name, price, and description) for the given product IDs.

3. The app displays the items to the consumer, using the metadata received.

4. The consumer selects which item they want to purchase.

5. The app triggers a payment using the in-app purchase API.

6. Nokia Store processes the payment, and completes the transaction. The process includes prompting the consumer for their Nokia account password, if the consumer is not yet signed in.

   Note: If Nokia Store notices after the sign-in that the consumer actually has a right to restore this item without any cost, it switches from a purchase process to a restoration process.

7. Nokia Store delivers the DRM key to unlock the protected content on the device.