You need to sign your apk before uploading it in the developer portal. Steps as follows:

a. Generate an Upload key and keystore

In Android Studio select Build->Generate Signed Bundle/APK



b. Choose Signature version and sign the app with your key

Select the appropriate Build variant, signing version as V1(Jar Signature) and generate the signed apk.


Locate the apk named app-release.apk or the app-debug.apk depending on the build variant chosen. Upload this apk to Poynt developer portal.


APK Submission through developer portal

1. Create a New developer account or Sign-In to your existing one

2. Create an App


Enter the app name as you want it displayed in Poynt Store.

3. Download the Public-Private keypair

The private key is used to generate self-sign JWT required to obtain an access token. You need this key if you plan to use Poynt Cloud API.

IMPORTANT! Poynt does not store your private key. If you lose your private key you will neeed to reset and download new key in Developer Portal.


4. Go to App details


5. Edit App details



If you need to reset your API private key, you can go to App Keys tab:

6. Upload an Apk

The package name of your app has to be unique in the Poynt Store. The best practice is to have the package name start with the domain name of your site (e.g. If you own domain name your apps package name should start with com.awesomedeveloper). Apps with package names starting with co.poynt or com.poynt will be rejected.

NOTE: Make sure that you are uploading a signed release version of your apk (If you are uploading a dev variant to test billing integration it can be signed by Android Studio debug key).


WARNING: Make sure you don't lose the key used to sign your apk. If you do, you will not be able to push updates to merchants who use your app and will need to create a new app with a different package name




You are not done yet. Uploading your apk does not submit your app for review!

7. Provide additional information needed for your app to be listed in Poynt Store

Select the terminal types that the app is compatible with under Terminal Compatibility.



Based on the country you select you will be promted to accept the Distribution Agreement.


NOTE: MCCs, or Merchant category codes, classify businesses by what they sell or the service they provide. These four-digit codes are assigned by payment card organizations — Visa, MasterCard, American Express and Discover — when the business first starts accepting these methods of payment. Please provide the (MCC) codes of merchants (in a comma-delimited format) your app is best suited for. More information on (MCCs) codes can be found here


If you are uploading a new version of your app provide the list of changes in the Change Log.

Upload a minimum of two screenshots (for best results use 800x1280px resolution). You can also upload a video (up to 10MB).

Save the submission.


8. Create Billing plans


Cancelation Policy determines if the subscription will be canceled immediatey or will remain to be active until the end of the current billing cycle.

Save and submit the plan. Plan will be in Pending state until a Poynt analyst approves it.

9. Submit the apk for Poynt Review



The app has now been successfully Submitted.


10. Beta Apps:

The apk is reviewed within 24 hrs. If all the checks pass, the apk status changes to IN-PILOT. The app is now available under the Beta Apps section of the app store on the terminal.

IMPORTANT! During the Pilot / Beta testing phase, the app can be installed on up to 10 devices for beta testing. As soon as the device limit is reached the app will not be displayed under the `Beta Apps` section of the app store.


If the apk is rejected, the rejection reasons are displayed for that version.


11. Plan approval & Go-Live

If the app exits the Pilot phase successfully, Poynt review analyst will change Billing plan status from Pending to Approved. The app is also set to Live status and the app made available on the app store.