Clover Go and Clover Go SDK

(Legacy Content)

The Clover remote-pay-android-go and remote-pay-ios-go SDKs for Android and iOS POS integrations allow your Android- or iOS-based Point-of-Sale (POS) system to communicate with a Clover Go payment device and process payments. The SDK is designed to allow merchants to take payments on Android or iOS smartphones and tablets.

The SDK includes an example POS. To work with the project effectively, you will need one of these development environments:

For Android:

  • Android Studio 2.3.3 and above
  • Android OS 4.4.4 (API 19) and above on your device

For iOS:

  • XCode 11.1
  • iOS 10.0 and above on your device
  • Cocoapods

Card-present transactions

The Clover Go SDK supports transactions in which the merchant uses the approved card reader to accept physical credit or debit cards on a connected smartphone or tablet. The Clover Go platform supports the following payment options:

  • Magnetic stripe card – A payment card that has a magnetic stripe
  • EMV card – A payment card containing a computer chip that enhances data security. Clover Go's EMV-compliant platform enables the customer or merchant to insert an EMV card into the card reader.
  • NFC contactless payment – A payment card with an NFC chip or a mobile wallet used by tapping the mobile device to the card reader

Payment transactions

The Clover Go SDK supports the following payment transactions:

  • Sale - A transaction used to both authorize and capture the payment amount at the same time. A Sale transaction is final and the amount cannot be adjusted.
  • Auth - A transaction that can be tip-adjusted until it is finalized during a batch closeout. This is a standard model for a restaurant that adjusts the amount to include a tip after a card is charged.
  • Void - A transaction that cancels or fully reverses a payment transaction
  • Refund - A transaction that credits funds to the account holder
  • Pre-auth - A pre-authorization for a certain amount
  • Pre-auth capture - A pre-auth that has been finalized in order to complete a payment (for example, a bar tab that has been closed out)
  • Partial auth - A partial authorization. The payment gateway may return a partial auth if the transaction amount exceeds the customer’s credit or debit card limit.
  • Tip adjust - A transaction in which a merchant takes or edits a tip after the customer’s card has been processed (for example, after the initial auth transaction)