See Clover App Market.
A tip-adjusted sale. This type of transaction is typically used by restaurants and similar establishments.
A transaction in which the customer does not physically present a payment card, such as a phone or web order.
A transaction in which the customer physically presents a payment card, such as a card swipe transaction.
A potential issue encountered by the Clover device while attempting to process a payment. A challenge is triggered by a potential duplicate payment (DUPLICATE_CHALLENGE) or an offline payment (OFFLINE_CHALLENGE).
When a challenge is raised, the Clover device calls the ConfirmPaymentRequest() method and passes in a ConfirmPaymentRequest object that contains the Payment and the list of challenges it encountered. This method prompts the merchant to either accept the payment (and any risk associated with it), or reject the payment. See Working with Challenges for more information.
See Pay Display app.
A platform where developers can publish third-party apps that integrate with Clover point-of-sale solutions. Merchants can find and download your apps by searching the Clover App Market.
The SDK for integrating your point-of-sale software with the Clover platform.
A full-featured payment and business management device that’s optimized for mobility. More about Clover Flex.
An all-in-one point-of-sale with payment acceptance. The device can function as a standalone point-of-sale, or serve as a customer-facing payment terminal when connected to another device, such as the Clover Station. The Clover Mini accepts multiple credit and debit payment types, including:
A mobile point-of-sale solution designed for quick payment processing at food trucks, festivals, and other line-based businesses. Pay-at-the-table restaurants also use Clover Mobile.
Clover’s countertop point-of-sale. Clover Station enables you 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 EMV chip cards, PIN-based debit transactions, and NFC payments like Apple Pay. More about Clover Station.
A specially-permissioned Clover device that can simulate transactions in a sandbox environment. This environment is completely separate from the production environment. A DevKit will enable you to test apps prior to deploying them on the production server. More about DevKits.
A Europay, MasterCard, and Visa (EMV) payment made with a card containing a computer chip that enhances data security.
A system that runs entirely on Clover hardware. Your point-of-sale software runs as an app on Clover devices. Merchants can discover it seamlessly within the Clover ecosystem by searching for the app in the Clover App Market. This may be an attractive option for an integrator building a new point-of-sale software solution, or interested in providing an all-in-one solution for merchants.
Independent Software Vendor. This term may also refer to the vendor’s software developer.
A component of the Clover Connector SDK. ICloverConnector provides the callable interface for interacting with a Clover device.
A component of the Clover Connector SDK. The ICloverConnectorListener interface listens for callbacks from a Clover device.
A connection between your point-of-sale and the Clover platform. Connections may be fully-integrated, semi-integrated, or Clover Go (mobile).
The software developer responsible for connecting a company’s point-of-sale software with the Clover platform. This term may also refer to the company itself.
A payment made with a traditional card that has a magnetic stripe on the back.
A “refund” or credit that is not associated with a previous payment. Because it is an independent transaction, it can be for any amount; a manual refund is not limited to the total of a previous sale. Also referred to as a naked refund.
A business that uses the Clover platform to process payments. Clover merchants are typically small or medium-sized businesses with 10 to 500 employees.
A feature used to associate all of the merchants belonging to a single enterprise, so you can manage and report on them in bulk. A merchant can belong to multiple merchant groups. You can create merchant groups in the Developer Dashboard.
An auto-generated ID for an individual merchant (example: TA72R18N3RAV4).
The service plan to which a merchant subscribes. More about merchant plans.
A category of functionality on the Clover platform. A merchant will have access to certain modules, depending on its service plan. Developers add metadata about app functionality through Clover’s modules framework. Clover uses this information to determine which apps will be available with each service plan. For example, all plans include the Payments, Employees, Settings, Printers, and Customers modules. Higher-level service plans may also include modules for handling items (inventory), discounts, etc. More about modules.
A transaction in which a customer leverages an Apple Pay, Samsung Pay, or Android Pay mobile wallet by tapping their mobile device to the card reader.
See Manual Refund.
See Pay Display app.
A partial authorization. The payment gateway may return a partial authorization if the transaction amount exceeds the customer’s credit or debit card limit. See How can I test a Partial Auth? and How can I tell whether a Partial Auth has occurred? for more information.
The Clover app that handles interactions with customers on customer-facing Clover devices. Clover offers multiple Pay Display apps to accommodate various connection methods:
- USB Pay Display
- Cloud Pay Display
- Secure Network Pay Display (currently available for Clover Mini and Clover Mobile)
A pre-authorization for a certain amount. This transaction lets the merchant know whether the account associated with a card has sufficient funds, without actually charging the card. When the merchant is ready to charge a final amount, it will capture the Pre-Auth to complete the payment. This payment flow is used for bar tabs, for example.
A Clover app that provides core functionality for taking orders and payments. More about the Register app.
The architecture behind the Pay Display app and Clover Connector SDK, such as the protocols and messages that run in the background on Clover devices. This term may also be used to refer to the Clover Connector SDK itself.
A transaction in which the amount is final and cannot be adjusted.
See Pay Display app.
A system that runs on a combination of Clover and non-Clover hardware. Your point-of-sale software and hardware handle orders, while the Clover device handles payment processing.
Smart Receipts allow developers to add information to the bottom of Clover’s paper and web receipts for the customer. This feature offers an easy way to encourage customer interaction, and adds extra value to the receipt. More about Smart Receipts.
A fake merchant a developer can use to test apps.
A transaction in which a merchant takes or edits a tip after the customer’s card has been processed (i.e., after the initial Auth transaction).
See Pay Display app.