Basic app configuration
North America
Europe
Latin America
Perform a functional review of your app for basic configuration.
Functional review: Basic app configuration
NOTE
When you build your app in production for approval, remember to set the app permissions again. The permissions configured in sandbox do not automatically transfer to production.
Check app launch and operability on the Clover device
One of the most common approval issues is that the app crashes at launch or produces exceptions or crashes. To make sure your app successfully launches on the Clover device:
| Criteria | Description |
|---|---|
| Build the Android app for a subset of Clover devices | 1. When you test your Android app on the emulators, run tests for all the Clover devices that support your app. 2. When you submit your APK in the production Developer Dashboard, select only the Clover devices on which you've tested the app. See how to select a Clover device for an Android app. |
| Set the required app permissions | Make sure you have the right permissions to interact with Clover merchant data. Before you submit your APK, you must set the required permissions in the production Developer Dashboard. |
| Check app usage of Clover APIs | Your app must sync with Clover data and retrieve data from endpoints as expected. For example: The app has Employee Read permission to list employees so the merchant can assign them to tables. However, if the employee list is not populated on the app, it is inoperable. - The app has Customer Write permission to let customers sign up for the merchant's newsletters. However, if the app does not save new customers to the merchant, it is inoperable. |
Use the REST API
| Criteria | Description |
|---|---|
| Make OAuth-authenticated calls to merchant data | Your app needs to have an authentication flow to make REST API calls. While you can generate an API token for testing in the sandbox, you can't use this token in production. For production web apps, you need to build a complete OAuth flow that: - Uses the correct production URL. - Captures the access token for logged-on merchants through the OAuth flow. - Makes REST API calls with the access token. |
| Query the Clover web services for Android apps | Your Android app must query the Clover web services programmatically. For more information, see the WebServiceActivity.java Android example. |
Use the Ecommerce API
| Criteria | Description |
|---|---|
| Request only required permissions for your app | Clover lets you manage information about Clover merchant businesses. Since this information is sensitive, we require that you request permissions for only the endpoints that are necessary for the functioning of your app. After you submit your app for approval, Clover sends you a form to select your app's permissions and justify why each permission is important for your app. Completing the form is part of our app approval process. |
| Ensure PCI DSS compliance with your Ecommerce app | Clover recommends that you integrate your app with Ecommerce using a Clover-hosted iframe tokenizer. The iframe and API integration securely accept credit card information, which reduces the Payment Card Industry Data Security Standard (PCI DSS) compliance burden on app developers and Clover merchants. For more information, see Integration types. |
| Vault cards associated with customer records | If you are vaulting cards in an Ecommerce app, make sure the card information is associated with a customer record. Card data sent with the Clover-hosted iframe or to the v1/tokens endpoint returns a token that can be used for subsequent transactions.Note: Your app must make it clear to the customer that their card is being saved, and it may reused for transactions without requiring a manual card entry. |
Updated 4 months ago