At high level application lifecycle includes development, submission, certification, publishing, purchase and deployment steps.
During the development phase application testing on a Developer Kit requires application whitelisting that will enable app to connect to 3rd party cloud services.
Whitelisting of an app takes place by documenting the URLs the application uses to connect to external services in the App Submission Form in the Developer Central. The Developer Central will use this information to configure the sandbox environment in the Entitlement Services to allow the application running on a DevKit device to access external services. Entitlement Services uses the app ID and version to map whitelisted URLs to the connection requests coming from the test terminals. Application Whitelisting for the DevKit takes place when the draft app submission form is saved in the Developer Central. New app submission form is created in the Apps view by pressing the Create Commerce Apps button.
After application is tested, developer can complete filling the application submission form and submit application to be reviewed. While submitting the app, it is automatically whitelisted for the production Entitlement Services, for the payment devices merchants are using.
Applications developers submit to Verifone are subject to a manual review by two separate Verifone reviewers. Both reviewers conduct the complete review; it is not split between the two of them. After both reviews pass, application is published in the Marketplace.
App distribution model is limited to the USA and UK in the first release. More countries to be added in the coming releases. Developer defines the app distribution by selecting appropriate countries in the app submission form.
After merchants buy the applications in the Marketplace, application deployment is automated via Terminal Mgmt System. Verifone's TMS is called as Estate Owner portal. <--! <--!