Clover Go API
Clover exposes a full REST API at docs.clover.com plus native Android and iOS Go SDKs for card-present payments, with OAuth 2.0 and webhooks. The catch is sandbox access: partners must email dev@clover.com for keys and buy a $299 Go devkit to test against real hardware.
Frequently asked questions
Clover Go scores D+ on the API Report Card. Clover exposes a full REST API at docs.clover.com plus native Android and iOS Go SDKs for card-present payments, with OAuth 2.0 and webhooks. The catch is sandbox access: partners must email dev@clover.com for keys and buy a $299 Go devkit to test against real hardware.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
Clover Go is Fiserv's mobile-card-reader and Tap-to-Pay product line within the broader Clover POS ecosystem.
General-purpose mobile payment acceptance for micro and very-small merchants who need to take a card outside a fixed counter. A merchant signs up for a Clover account (direct or through their bank/ISO), receives a Clover Go reader (or activates Tap to Pay on iPhone), and pairs the reader to the Clover Go mobile app over Bluetooth.
High as a brand, moderate as a SKU.
Parent: Fiserv, Inc. (NYSE: FI), public, headquartered in Brookfield, WI; CEO Mike Lyons (succeeded Frank Bisignano in 2025).
Clover was founded in 2010, acquired by First Data in 2012, and rolled into Fiserv when Fiserv acquired First Data in 2019.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.