Developer App Review
Developers have signed up for a Developer account.
Developers have an app submitted for review through the Developer portal.
Developer verifies whether the app follows the general guidelines as described in the Poynt App Development Guidelines.
Should any changes be required, developer updates their app.
The submission form requires the developer to provide a short application summary, detailed description, change log information, app screenshots and the country of distribution. This information will be used by the app review team and it will be displayed in the app marketplace (“Store”) once the app has been approved.
When the app apk is uploaded for the first time, Poynt generates 2048 bit RSA private key that the developer needs to download to securely communicate with their app. Poynt does not store the private key, so if the developer loses the key the will need to generate a new one on poynt.net.
Step 4 & 5:
Upon submission, app status changes to “Submitted” in Poynt developer portal.
Once the app is submitted an automated ticket is generated in the Poynt ticketing system. App review team gets notified via email that the app has been submitted for review.
If the android apk file is being submitted for the first time, developer confirms the submission by sending an email to email@example.com with the following data:
* App Name * Package Name
Poynt app team will request for supporting documents and information:
* App support form * Infrastructure readiness * Distribution agreement * In-App billing details(Plan names, descriptions, amounts etc, see step 11.) * Test credentials(for app review) * Marketing collateral(Images, write-ups etc for post go-live marketing)
Developer returns completed and signed forms to the Poynt app team via email.
At this point, the Poynt App Review Team is engaged and an app review analyst reviews the submitted app.
During the review, if any app issues are discovered the app gets rejected and would need to be updated for further consideration. The app is placed back in the queue(Step 2) if rejected.
If the app passes all checks, the app moves to the next step in the process.
If the app passes all the necessary checks, it is signed.
If the app needs to be run on a select few terminals for sanity checks etc, there could be an optional step to run a pilot test before Go-Live.
The app team creates the billing plans and share the Plan IDs etc for the developer to setup the billing flow when invoking the billing fragment within the SDK. Plan information should follow this format (Example below):
"name": "Basic plan", "description": "Basic services plan with 30-day trial", "country": "US", "currency": "USD", "value": 500 "interval": "MONTH", "scope": "BUSINESS", "trialPeriodDays": 30
Note: "value" should be in cents "interval" can have any one of these values "DAY | WEEK | MONTH | YEAR" "scope" can have any one of these values "BUSINESS | STORE | DEVICE"
The app is set to LIVE by the app review analyst. The app now shows up on the Poynt app store.
Poynt Marketing team will reach out to the developer contact for details on setting up webinars, distribution strategy etc.