Platform Docs

Integration development and approval process

Integrations with the Clover platform

Creating a complete point of sale that complies with PCI and EMV standards is a costly and involved endeavor. Clover’s semi-integrated offerings allow developers to avoid many issues by using a powerful SDK to drive a Clover device with their existing software. Cardholder data encryption and transmission are handled entirely inside the Clover ecosystem, separating risk and ensuring compliance with data processing standards. Clover also offers native integrations where the POS is an Android app installed on a Clover device.

Overview

All integrations on the Clover platform flow through several phases to ensure software quality and compatibility:

  1. Application
  2. Education
  3. Development
  4. Approval
  5. Maintenance
Integration process

Integration process

Application

All integrations begin with the Semi-Integration Profile and Application form. Information collected in this form allows Clover to evaluate your integration. Once your information is reviewed and the application is approved by Clover, an engineer 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. 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)
  • 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.

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.

Education

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 non-compliant code isn’t written.

  • Asynchronous design and impacts
  • Clover devices and semi-integration (1:1)
  • Connecting and disconnecting a Clover device
  • Partial authorizations
  • Application reporting (reconciliation)

If you need help understanding any aspect of the SDK or the device and payments concepts it implements, a support engineer will provide this assistance through a ticket-based system. This system allows both parties to track the progress of individual questions and issues.

Development

Application development can begin once the prerequisite meetings and learning tasks are complete. If you don’t have Clover developer accounts, you must create one for both the sandbox and production environments using the developer dashboards:

Because a positive overall merchant and customer experience is the goal of all integrations, it is recommended that you order a Developer Kit for the Clover device to be used with your integration:

Throughout, Clover engineers are available to answer questions and resolve issues related to the devices and platform.

Approval

Once development is complete, you complete an integration submission packet containing the following:

  • Remote Application ID
  • Integration submission form
  • Sample receipts

A Clover engineer reviews the packet to verify the application meets architectural requirements and that receipts are EMV compliant. If the submitted information is acceptable, a live demonstration of the application is scheduled. During the demonstration, you will show a Clover engineer each feature of the application and its complete compatibility with your chosen Clover device. If there are any issues discovered during the demo, the engineer will document the problems and communicate the findings in writing. The process then shifts back to the Development phase and the required changes are made to the application. A resubmission is required and the Approval phase begins again once you submit an updated integration packet.

Maintenance

An approved application is allowed to operate on Clover’s production environment once all approval steps are complete.

To view logs and information related to your application’s performance, log on to the Developer Dashboard.

Clover engineers will monitor changes to the platform that may impact your application. You will receive updates regarding API changes and deprecations, new versions of the SDK, and platform maintenance periods at the email address associated with your Clover developer account. Make sure emails from semi-integrations@clover.com are not directed to a Junk folder.

If there is a issue with the application once it is in production use, you can post a question on the Clover community site or email semi-integrations@clover.com. A Clover engineer will review the report and, if needed, help you determine the cause. If the cause requires a code change in a Clover SDK or device application, the engineer will inform you when the fix is complete and if you need to update your application code.


Integration development and approval process


Suggested Edits are limited on API Reference Pages

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