Clover Platform Docs

Education

Once the information provided in the intake form is reviewed and approved by Clover, a support analyst will set up a Technical Discovery meeting to learn more about the needs of your business and the merchants you support. The engineer is an expert on the SDKs and other tools used to develop an integrated application.

Discovery for semi-integrations

Semi-integrations are meant for those developers who need a way to process card-based transactions while controlling all other aspects of the merchant experience using an external POS. If your needs extend beyond a semi-integration and into more of Clover’s platform, this discussion will reveal the best way Clover can support your needs.

During the discovery meeting, you’ll discuss the following about your architecture and planned application:

  • Clover Remote Pay SDK to be used (Windows, Android, iOS, or cloud)
  • The connection app to be used (see Pay Display Apps)
  • Your application’s architecture and how it will interact with the SDK
  • Clover’s architecture and how it impacts software design decisions
  • Region-specific features and limitations of the SDKs
  • Clover’s REST API (if your application will use it)

You and the engineer will also discuss the scope of your application and the remaining phases in the integration lifecycle.

Discovery for native integrations

Native integrations are meant for those developers who will use Clover hardware and develop their own POS software to run on the device.

During the discovery meeting, you’ll discuss the following about your architecture and planned application:

  • Your application’s architecture and how it will interact with the Payment Connector SDK
  • Clover’s architecture and how it impacts software design decisions
  • Region-specific features and limitations of the SDK
  • Clover’s REST API (if your application will use it)

You and the engineer will also discuss the scope of your application and the remaining phases in the integration lifecycle.

Architectural considerations

There are several technical details of the Clover platform that should be understood before any major development is done using a Clover SDK. A Clover engineer will explain these items to your engineering team and help ensure only compliant code is written.

  • Asynchronous design and impacts
  • One-to-one relationship between a Clover device and the POS system (the POS should not attempt to connect to more than one Clover device)
  • Connecting to and disconnecting from a Clover device
  • Partial authorizations
  • Application reporting (reconciliation)
  • Remote app ID requirements

Updated about a month ago


Education


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.