Clover devices
Clover point of sale (POS) software runs on custom hardware for the best merchant experience. As a developer, you can publish apps through the Clover App Market. Most Android applications run unmodified unless the app depends on Google services not available in the Android Open Source Project (AOSP).
NOTE
Clover devices are not Google Play certified and do not come with Google Play Services.
Clover devices overview
Learn in detail about Clover devices from the Clover Shop. Here is a brief overview of the available devices:
Clover device | Description |
---|---|
Clover Flex | Full-featured payment and business management device that’s optimized for mobility. See Clover Flex models and specifications. |
Clover Mini | All-in-one point of sale (POS) with payment acceptance. The device can function as a standalone POS, or it can serve as a customer-facing payment terminal when connected to another device, such as the Clover Station. See Clover Mini models and specifications. |
Clover Mobile | Mobile point of sale (POS) solution for quick payment processing at food trucks, festivals, and other line-based businesses. Pay-at-the-table restaurants also use Clover Mobile. See Clover Mobile specifications. |
Clover Go | Bring-your-own-device (BYOD) solution from Clover for taking EMV payments on mobile devices. Clover Go works with Apple (iOS®) and Android phones and tablets. See Clover Go solution and accessories. |
Clover Station | Countertop point of sale system (POS) to take payments, track inventory, manage timesheets, run reports, and print receipts. The device alternates between merchant- and customer-facing views. Clover Station requires the addition of a Clover Mini to accept PIN-based debit transactions and NFC payments like Apple Pay®. See Clover Station models and specifications. |
Clover device features
Clover devices are payment card industry (PCI) compliant and include the following features:
- Accept all payment types—magnetic stripe swipe, EMV dip, NFC contactless, and manual entry
- Complete auths, pre-auths, and sale transactions
- Handle voids, payment refunds, and manual refunds (detached credits)
- Handle partial auths
- Take store-and-forward or offline payments
- Detect and prevent duplicate transactions
- Allow manual card entry
- Support cashback
- Allow customizable tip options
- Allow configuration settings for each merchant
- Offer 4G LTE connectivity in all regions with 3G/2G in select regions (optional)
- Include integrated printer with thermal paper in Clover Flex and Clover Mini
- Provide four standard USB ports
Android version and region availability
The following table displays Clover-hardened Android versions running on Clover devices and the countries where the devices are currently available.
Clover-hardened Android Version | Clover Device | US | CA | UK/ IE | DE/ AT | NL | AR | BR | MX |
---|---|---|---|---|---|---|---|---|---|
AOSP 10.0 (API Level 29, Q) | Station Solo | ✅ | |||||||
AOSP 10.0 (API Level 29, Q) | Station Solo (international) | ✅ | ✅ | ||||||
AOSP 10.0 (API Level 29, Q) | Station Duo 2 | ✅ | ✅ | ||||||
AOSP 8.1.0 (API Level 27, Oreo) is upgradable to AOSP 10.0 (API Level 29) | Station Duo (previously Station Pro) | ✅ | ✅ | ✅ | |||||
AOSP 7.0.0 (API Level 25, Nougat) | Station 2018 | ✅ | |||||||
AOSP 4.2.2 (API Level 17, Jelly Bean) | Station | ✅ | ✅ | ||||||
AOSP 10.0 (API Level 29) | Mini 3 (LTE & Wi-Fi only models) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ||
AOSP 8.1.0 (API Level 27, Oreo) is upgradable to AOSP 10.0 (API Level 29) | Mini 2 (LTE & Wi-Fi only models) | ✅ | ✅ | ✅ | ✅ | ✅ | |||
AOSP 4.4 (API Level 19, KitKat) | Mini | ✅ | ✅ | ✅ | ✅ | ||||
Android 13, API Level 33 | Flex 4 | ✅ | |||||||
Android 13, API Level 33 | Flex Pocket | ✅ | ✅ | ||||||
AOSP 10.0 (API Level 29) | Flex 3 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ||
AOSP 8.1.0 (API Level 27, Oreo) is upgradable to AOSP 10.0 (API Level 29) | Flex 2 (LTE & Wi-Fi only models) | ✅ | ✅ | ✅ | ✅ | ✅ | |||
AOSP 5.1.1 (API Level 22, Lollipop) | Flex | ✅ | ✅ | ✅ | ✅ | ✅ | |||
AOSP 4.4 (API Level 19, KitKat) | Mobile | ✅ | |||||||
Clover Go | ✅ |
Key
✅ devices supported in a specified region:
- North America—Canada (CA), United States (US)
- Europe—Austria (AT), Germany (DE), Ireland (IR), Netherlands (NL), United Kingdom (UK)
- Latin America—Argentina (AR), Brazil (BR), Mexico (MX)
- AOSP—Android Open Source Project
Clover device configuration
You can configure a Clover device to display different payment, tipping, and receipt options to customers. Depending on the environment where the device is used, you can enable or disable these options.
Default configurations are:
Mode | Default configuration | Options on POS | Options on device |
---|---|---|---|
Cashier mode | In the Cashier configuration for a retail store, the customer interacts directly with the Clover device to process their payment. | Ask for tip: Disabled | Ask for tip: Enabled Tip is entered on the tablet screen. |
Restaurant mode | Restaurant configuration is for a quick-service restaurant environment. The customer interacts directly with the Clover device to process their payment. | Ask for tip: Enabled | Ask for tip: Disabled |
Tablepay mode | Tablepay configuration is for a full-service restaurant, where customers interact directly with the Clover device to process their payment. | Ask for tip: Disabled | Ask for tip: Enabled Tip is entered on the tablet screen. |
Related topics
For more information on Clover devices, see:
Updated 16 days ago