Platform Docs

Clover development basics


Create a developer account at Enter and verify your email address. This will create a developer account for you, as well as a test merchant account.

We’ve created a sample inventory file that will help you get started with your test merchant.

Once you log on to your sandbox account, select your test merchant from the drop-down list in the header. Select the Inventory app and then import the sample inventory file.

The following Android development guidelines are designed to help you produce high-quality apps with a smooth development and launch process. These foundations can help your apps provide the kind of excellent merchant experiences that attract and keep loyal subscribers.

Best Practices

  • We strongly encourage you to integrate some form of crash reporting utility into your Android products. This will help you maintain operational awareness of your product.
  • We also recommend that you collect metrics on app usage. This will help you build better products and increase your awareness of any issues.
  • To avoid confusing consumers, do not use the term PIN in your app.

Code Quality

Your app should conform to the following Java and Android programming practices:

You should also understand the difference between compileSdkVersion, targetSdkVersion, and minSdkVersion (see Setting Android SDK versions for for more information. Leverage the native Android buttons, such as the Back and Home buttons.

Device Rotations

Clover Station and Station 2018 use display rotation when switching from merchant-facing mode to customer-facing mode. If your app will be available for either Station device, it must gracefully handle display rotation.

Display rotation is disabled on Clover Flex, Clover Mini, and Clover Mobile.

Async Tasks and Executors

  • Minimize or eliminate work on the main UI thread.
  • Verify that your activity is not finished or destroyed upon completion of an AsyncTask’s background task.
  • Use a back-off switch when responding to errors and confirm normal functioning before proceeding, instead of starting new loops.


  • Do not check app tokens into your source code online.
  • Use Google’s Android Keychain when storing tokens on the Clover device.
  • Do not prompt users to enter sensitive cardholder data, such as card numbers and expiration dates, except as part of Clover’s payments SDK (this means that third-party Clover Apps are not payment apps as the term is defined in the PCI PA DSS).
  • Following Clover's guidelines for SSL/TLS.
  • Follow the SEI Cert Java Secure Coding Guidelines.

Clover development basics

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.