---
updatedAt: 2026-03-24T12:14:41.000Z
agentTools:
  projectIndex: https://docs.clover.com/dev/llms.txt
---

# Use Clover Connector

[block:html]
{
  "html": "<div class=\"container-top\">\n  <!-- North America -->\n  <div class=\"container-reg\">\n    <div class=\"pill-reg\">\n      <div class=\"label-reg\">North America</div>\n    </div>\n  </div>\n\n  <!-- Europe -->\n  <div class=\"container-reg\">\n    <div class=\"pill-reg\">\n      <div class=\"label-reg\">Europe</div>\n    </div>\n  </div>\n\n  <!-- Latin America -->\n  <div class=\"container-reg\">\n    <div class=\"pill-reg\">\n      <div class=\"label-reg\">Latin America</div>\n    </div>\n  </div>\n</div>\n\n<!-- CSS moved to global stylesheet-->\n"
}
[/block]

The Clover Connector SDK provides a consolidated asynchronous interface that enables your point of sale (POS) software to interact with Clover’s customer-facing payment devices.

In this section, we introduce Clover Connector for different platforms.

## Prerequisites

These tutorials assume you have already:

* Read the [Overview of the Clover Platform](https://docs.clover.com/dev/docs/clover-architecture)
* Set up a [developer account](https://www.clover.com/developers) (including your test merchant settings).
* Order and set up a [Clover Developer Kit (Dev Kit)](https://docs.clover.com/docs/clover-dev-kits).
* [Create a Remote App ID](https://docs.clover.com/dev/docs/create-your-remote-app-id) (`remoteApplicationID`) for your semi-integration POS. This is different from your App ID.

## Tutorials

Use the following tutorials to build a semi-integrated solution for your platform:

* [On Windows using .NET](https://docs.clover.com/dev/docs/windows)
* [On Windows using REST](https://docs.clover.com/dev/docs/on-windows-using-rest)
* [On Windows using WebSockets](https://docs.clover.com/dev/docs/on-windows-using-websockets)
* [In the Cloud](https://docs.clover.com/dev/docs/cloud-sdk-v3)
* [On Android](https://docs.clover.com/dev/docs/semi-integrated-android-apps)
* [On iOS](https://docs.clover.com/dev/docs/ios)

## Callable and Callback interfaces

### ICloverConnector

`ICloverConnector` provides the callable interface and includes the following capabilities:

* [Processing cards](https://docs.clover.com/dev/docs/transaction-types) as Sales (fixed-amount payments), Auths (tip-adjustable payments), and PreAuths (pre-authorizations for a specific amount that can be updated before finalizing payment)
* Vaulting card tokens for future payments
* Processing payment refunds and voids
* Displaying order details
* Printing images and text
* Requesting batch closeouts
* Requesting device and payment status
* Starting and communicating with [Custom Activities](https://docs.clover.com/dev/docs/using-customer-facing-platform)

### ICloverConnectorListener

`ICloverConnectorListener` provides the callback interface and includes the following capabilities:

* Responses to sales, authorizations, and pre-authorizations
* Responses to card vaulting requests
* Responses to payment refunds and voids
* Responses to tip amount adjustments and captured payments for pre-authorizations
* [UI event messages](https://docs.clover.com/dev/docs/ui-state-messages#listening-for-ui-messages) sent as the Clover device changes screens, along with appropriate actions correlating to options on the device (for example, Cancel, OK, Done, Yes, and No)
* Closeout processing events
* Requests to confirm payments or signatures
* Events sent when the device disconnects, connects, or is ready
* Responses to device and payment status requests
* Responses or messages from [Custom Activities](https://docs.clover.com/dev/docs/using-customer-facing-platform)