***This page has been removed from the VDC due to the Verizon Apps shutdown. Feel free to browse our other development areas, devices, APIs and Tools.***
***NOTE: Effective November 1st, 2012, the VDC no longer accepts new Verizon App submissions. Additionally, beginning December 2012, final billing to customers for all existing Subscriptions and In-App Purchase apps will occur, and all paid Subscriptions and In-App Purchase API apps will be removed from the catalog on November 1st, 2012. Customers will receive a final full month of use & access, before Verizon Apps begins its complete shutdown in January 2013.
For additional details, please review the Verizon Apps Notice and Verizon Apps Transition Timeline.***
The sections below provide a high-level overview of how the In-App Purchase SDK works from both the end user and developer perspectives. Details include how end-user PINS work to complete purchases, communication back to Verizon servers,and the flow of making an In-App purchase.
The Verizon Apps client runs a service on the device that performs the communication to Verizon backend systems. This service communicates two ways with the In-App Purchase API in order to retrieve In-App submissions and validate purchases. Additionally, the service will provide a final message to the end user in the form of a pop-up within the developer application context to confirm the In-App purchase.
In order to hook into the service, developers must extend the InAppActivity class that is part of the API and override the onPurchaseResult method to receive callbacks from the service. Make sure to plan architecture around extending the InAppActivity. Refer to the In-App API Coding Recommendations page
When calls are made to purchase items from within developer applications the Verizon App store client will overlay confirmation windows within the application context to confirm purchase. Verizon Wireless customers using Verizon Apps will be able to setup their four-digit PIN and manage their account using their MyVerizon credentials. The account owner can then approve any numbers that are under their account for in-app purchase functionality.
Every purchase that is made within the app that is enabled with the In-App Purchase SDK will require the end user to enter the PIN to confirm and complete the transaction. The purpose of the PIN functionality is to prevent unwanted purchases from within applications such as children purchasing excessive amounts of In-App goods unknowingly.
SETTING UP THE PIN
Refer to the screenshots below to see the flow for a customer setting up the initial device PIN within the Verizon App Store client.
End users will have to enter their PIN in order to complete any In-App purchase from within an app. Refer to the series of screenshots below demonstrating an in-app purchase as well as the overlay screens from within an example app, Music ID:
Note that the two screens after the purchase option are overlaid on top of developer applications by the Verizon Apps client for the end user to enter the PIN and subsequently confirm to them that the transaction is successful.
If developers have properly extended their activities that perform In-App purchases with the InAppActivity from the SDK, this functionality is transparent and the app will receive a callback from the Verizon Apps client indicating success/failure of the purchase. Refer to In-App API Coding Recommendations.