Full app functionality tests

Clover merchants must have a seamless experience when they are using your app and other Clover apps for their business.

At the minimum, follow these guidelines to create seamless experiences for merchants.

Functionally acceptable by Clover's policies and TOS

Your app must comply with Clover's policies and TOS. For compliance, avoid the following practices.

Do not circumvent Fiserv or its banking channels

All payments and financial services provided by your app must be processed by Clover, Fiserv, or its banking channels.

Do not add surcharges to credit card transactions

Using your app to add surcharges to credit card transactions is against Clover's policies and TOS. See the Clover Credit Card Surcharging Policy for more information.

Do not act as a money transmitter

Using your app to act as a money transmitter or to provide money transfer services is against Clover's policies and TOS.

Do not exclude debit cards from cash discounts

If your Android app is used to apply a cash discount, all three options—cash, check, and debit card—must be available to the merchant.

In addition, if the cash discount app is built to change the price of inventory items, the price change must occur only once. The merchant must be informed of the price changes for them to update their external inventory prices to match the prices on the Clover device.

Do not share or sell employee or customer data with a third party

Using your app to share or sell employee or customer data with a third party is against Clover's policies and TOS.

App workflows

After merchant onboarding, the first few steps taken by Clover merchants are crucial to their experience with the app.

App follows an expected workflow

Ensure that all the buttons and other UI elements function as expected (that is, they function as expected and do not lead merchants to unexpected areas of the app).

Improve merchant experience programmatically

For any configuration set by a merchant, pull all related information and personalize the experience for the merchant. Ensure that all information that can be pulled programmatically is pulled programmatically.

With the merchant read permission, you can retrieve Clover merchant information and automatically populate sign-up forms by simply calling the needed /v3/merchants endpoints.

Do not request merchant credit card or bank account information

Under no circumstances are you allowed to create a payment flow specifically for requesting a merchant to enter credit card or bank account information.

Multi-device functionality

If your Android app provides features involving multiple Clover devices, ensure that the app syncs data across all devices for a single merchant account. If your app does not provide this sync functionality, the app must explicitly inform the merchant.

Payments

If your Android or web app provides any payments-related features, ensure that the app is built for the following expected flows.

Payments on device

To provide customers with payment options, your app must launch the Clover payments flow. We will verify the flow with test card numbers and a live credit card.

Payments on web apps

To provide customers with payment options, your app must use the Ecommerce API for any online (card-not-present) orders.

If you are using Card Connect or Payeezy instead of Ecommerce, please let us know when you are submitting your app for approval.

We will test your usage of the API, confirm if the implementation is correct, and then test with Clover test card numbers and a live credit card.

Syncing with Clover apps

If your app provides any order- or customers-related features, ensure that the app is built for the following expected flows.

Orders

If an order is placed using your app, ensure that the order information syncs with the Clover Orders app. Synced orders must include descriptive line items that align with the item or service ordered by the customer. In addition, any taxes associated with the order must match the taxes calculated by Clover.

After an order is placed, ensure that any payments or refunds are reflected correctly in the Clover Orders app. We will test all the associated payment states: OPEN, PAID, and REFUNDED.

Customers

If a customer is created using your app, ensure that the customer information syncs with the Clover Customers app.

Cash transactions

For any cash drawer features provided by your Android app, ensure that the app is programmatically logging all cash exchange in the cash log. For any exceptions, ensure that you provide instructions to merchants about reconciling their reporting for cash exchange.

Revenue and taxes

For any revenue or tax-related impact from using your app, ensure that the math is accurate and that the final results show up accurately.