***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.***
SUBMITTING SUBSCRIPTIONS CONTENT TO THE VDC PORTAL
***NOTE: Effective November 1st, 2012, the VDC no longer accepts new app Verizon App submissions. Additionally, on December 1st, 2012, final billing for all existing Subscriptions apps will occur, and all subscription apps will be removed from the catalog. Customers will receive a final full month of use & access, before Verizon Apps begins its complete shutdown on Jan 7th, 2013.
For additional details, please review the Verizon Apps Notice amd Verizon Apps Transition Timeline.***
In order to submit applications that are enabled with the In-App Purchase SDK you will follow the standard submission process with a few core differences. The next sections outline the submission flows through the VDC Portal for Subscriptions and In-App Purchases. The entire end-to-end process is not shown, only the key parts that are different from the standard flow in order to enable In-App Purchases for your application. Please refer to the following links on the VDC portal for questions related to submission that aren’t covered here.
After stepping through the first submission screen you’ll be presented with the following:
If you intend to release your app with In-App support you should select “Yes” to the question “Does the app support In-App purchases?” otherwise make sure “No” is selected. It is important to note that you will not have the ability to offer every parent app purchase model if you are enabling your app for In-App purchase content; the only parent app purchase options are: Free, One-time Paid Download (unlimited re-downloads), One-time Paid Download (paid re-downloads).
The In-App Purchase API performs the lookup of the license that corresponds to your application by using the unique keyword assigned to your app. These keywords are provided by the developer or auto-generated by the system during the initial concept submission of the application. Make sure you note the keyword for your app and it must be unique – the system will prevent the use of non-unique keywords.
The In-App Purchase SDK uses encryption to validate licenses and as a result you must make sure that you select ‘Yes’ to the question ‘Does your app use encryption?’on the “Before We Get Started” page. Failure to select ‘Yes’ here will result in the inability to add Subscription and In-App content in the VDC portal.
Since you’re submitting an app for Subscriptions, on the ‘Technical Questions’ page you must make sure you select ‘Yes’ for the option ‘Does this application use the Subscriptions API’, refer to the screenshot below.
As with the previous encryption question, if you do not select yes to this question you will not have the option for Subscription pricing options at the parent app level.
On the final submission screen for “Pricing” you are free to select a single price option or multiple pricing options; a single app can offer all five of the parent price models detailed in Section 2 if the developer chooses. Please note that if you would like to use In-App as well as Subscriptions API, you are limited to One-Time Download (Unlimited Re-downloads) and Per Download (Paid Re-Downloads). Refer to the screenshot below:
Finally, because you indicated that the app contains encryption you must the complete the Export Compliance form, refer to the screenshot below.
The In-App Purchase SDK uses encryption and thus any app that incorporates the SDK in code must also comply with Export Control laws. Download and complete the Export Compliance form from the link on this page. Refer to the example form below:
If your app uses only the In-App Purchase SDK and no other encryption of any kind, answer the first three questions and submit the completed form into the portal. If your app does use encryption other than the In-App Purchase SDK you must answer the remaining questions to the best of your ability and submit.
Verizon Wireless cannot give recommendations to developers on how to answer questions other than as they relate to using the In-App Purchase SDK. It should be noted that developers should divulge all encryption used in their apps, even if it is as basic as HTTPS usage. Verizon will review the forms and if there are questions, will directly contact developers.