You can link your point-of-sale hardware or software with Clover payment devices in a number of different ways. Choose the method that works best for your technology and your business and cut down your time-to-launch by leveraging our integration options.
Depending on the combination of merchant- and customer-facing devices you require, Clover offers different payment interfaces.
PaymentConnector interface exposes all of the Clover features needed for your Clover app to make a sale, issue a refund, and perform other payment functions. If you are building a native Android app and need to take payments, this API will serve your needs.
For example, you may develop a register app for a merchant, and the app will use the
PaymentConnector to process the sale. The interface is used for the following:
- Passing information about the transaction to the Clover payment app
- Returning confirmation of the transaction
CloverConnector interface is usually used to tether a POS (Clover or third-party) to a customer-facing Clover device. The interface offers the same payment functions as
An integration of this type could be a Windows-based POS that connects to a Clover Mini over USB. In this case, the
CloverConnector is used to do the following:
- Establish the USB connection
- Pass information about the transaction to the Clover Mini for customer review
- Initiate the payment flow on the Mini
- Receive the customer choices for a tip and a receipt
- If required, receive the signature for verification
- Return confirmation of the transaction to the POS
In a native integration, your POS runs directly on Clover hardware as an app. Merchants can discover your app seamlessly within the Clover ecosystem, simply by searching for it in our App Market. You take care of the merchant experience, and let us take care of the payments.
This may be an attractive option if you're building a new POS, or want to provide an all-in-one solution for your merchants.
For more information on how to natively integrate with Clover, please visit the
clover-android-sdk GitHub repository.
Semi-integrated solutions run on a combination of Clover and third-party hardware. Your point-of-sale software and hardware handle orders, while the Clover device handles payment processing. Our high-level SDKs make it easy to send messages back and forth between devices.
Keep your merchants satisfied with the system they're used to, and let us take the hassle of EMV compliance away from you. After integrating with us, the Clover device becomes a plug-and-play solution for your merchant base.
If you have an existing POS with a strong merchant base and are looking for the fastest way to make that system EMV compliant, then this is probably the best option for you. Semi-integration is also a good choice:
- If you have a sophisticated system that's difficult to move away from
- If you have a strong brand your merchants identify with
- If your POS system requires specialized hardware
The API uses an asynchronous call model. Your point-of-sale initiates a request, Clover receives and processes the request, and then provides a response.
Our SDKs support sales, auths, pre-auths, tip adjusts, refunds, manual refunds, and other actions. By downloading a single library and installing our device drivers, you can connect and start taking payments in less than a day.
To find out how to semi-integrate, see our Getting Started tutorials.
Clover Go is Clover's BYOD solution. This EMV-capable device attaches to a smartphone or tablet, quickly enabling native iOS and Android mobile apps to accept swipe, NFC, or EMV transactions with no EMV certification required on your end.
The Clover Go integration option is best for merchants on-the-go who want to enable their iOS and Android apps to accept payments. A Clover Go integration leverages a streamlined set of functions with a cost-effective and highly secure EMV-capable device.
For a developer preview of these SDKs, email email@example.com.
The Clover Go SDK is embedded within the mobile POS application. It leverages an asynchronous call model to interact with the calling application. Once the SDK is initialized, the calling application can initiate a payment request. The request will activate the card reader connected to the mobile device. The customer can then use any of the following mechanisms for payment: card-present transactions, card-not-present transactions, and cash transactions. The SDK will interact with the payment gateway to process the transaction and provide a callback with the payment response. The calling application will have the ability to capture the signature.