Before submitting your application for approval, we recommend paying attention to the versioning assigned to the APK file, which is defined in the versionName parameter of the AndroidManifest.

• Semantic versions: each time you submit a new version, it must be strictly greater than the last submitted version. For example, if the last version was 1.5.0, the next one could be 1.5.1, or 2.0.0, etc. Duplicate or lower versions than the last registered will not be accepted during system review.

• Non-semantic versions: if you use a different version format (example: 1.6.1-smartApp, releaseA, etc), make sure the new version is different from any version you have previously submitted, as reusing already used identifiers is not allowed.

Contact your Mercado Pago representative and share the APK file (which must be smaller than 50MB) for your application to be reviewed. The Mercado Pago security team will review whether the guidelines outlined in the Smartapps restrictions document are being followed.

To publish your application in the Mercado Pago ecosystem and ensure the security of the application and its updates, you must digitally sign it with a certificate. In the official Android documentation you will find the step-by-step process to sign the application with the certificate generated by the developer.

In addition, you should always use the same signing key to avoid conflicts in the distribution tool caused by applications signed with different keys.

Share with the Mercado Pago Support team the necessary information for installing the application on the Point Smart terminals that will operate with the application, making sure to provide the following details correctly:

• Required: the serial number of the Point Smart terminal and the user_id of the application of the associated Mercado Pago account.
• Optional: the pos_id of the cash register and the store_id of the store that have been created and will be associated with the terminals.