Clover Platform Docs

An integrated app can be launched for merchant after both the app and the associated developer account are approved. This process includes all of the following elements:

  • Submitting your production developer account
  • Recording your payment flow videos
  • Submitting and demonstrating your app

Once you have finished development of your application, complete the steps in the following sections. Once your approval request is received, a Clover team member will review the request and contact you with the results.

Submitting a developer account for approval

Your application is linked to a production developer account, and this account must be verified and approved before testing can begin. To complete this step, the semi-integration team must be able to verify your identity.

Individual developer

If you are an individual submitting a semi-integrated app, complete the following steps:

  1. Log on to your Clover developer account.
  2. On the side nav, click Developer Settings.
  3. On the Developer Info page, provide the needed information in the following sections:
  • Complete the Identity Verification fields
  • Complete the Contact Info fields
  1. Click the Developer Agreement link and read the agreement.
  2. To accept the developer agreement and submit your account information, click Submit Application.
    The status bar updates with the date and time of your submission and shows that your account is being verified. You will also receive an email confirmation that your account has been submitted.

Status bar with submission time

Corporate developer

If you are submitting a semi-integrated app as a company, complete the following steps:

  1. Log on to your company's Clover developer account.
  2. On the side nav, click Developer Settings.
  3. On the Developer Info page, click the Account Details row.
    The Edit Account Details dialog appears.
  4. For the I'm doing business as an field, select the Business option from the drop-down list.
  5. Complete the required business information fields and then click Save.
  6. On the Developer Info page, provide the needed information in the following sections:
  • Complete the Identity Verification fields
  • Complete the Contact Info fields
  1. Click the Developer Agreement link and read the agreement.
  2. To accept the developer agreement and submit your account information, click Submit Application.
    The status bar updates with the date and time of your submission and shows that your account is being verified. You will also receive an email confirmation that your account has been submitted.

Status bar with submission time

Record your payment flow videos

Read the section on testing payment flows and verify your application can successfully pass the required tests. Record a video of each payment.

Submit your application using your production account

During the development phase, the Clover sandbox environment is used to test your application without affecting live merchants. Once ready for approval, your app is submitted for approval in the production environment. To submit your app, you must link to your privacy policy and your terms of service or end user license agreement. These documents will be verified for compliance with Clover's Developer Legal Guidelines.

Your application will be reviewed and checked for compliance with the following:

Demonstration of application

To complete the demonstration, you must provide evidence of your applicationโ€™s compatibility with the following platform features. Your app's integration points with Clover will be verified.

Remote application ID (RAID) configuration

Your connection logic must correctly pass the RAID generated for the application. A misconfigured or missing RAID will cause your merchants to experience slower transaction processing.

OAuth implementation (REST API only)

All interactions with merchant data sent through the Clover server must be authenticated with an OAuth token (and not a merchant API token as allowed in sandbox).

Recordkeeping using an external ID

To ensure Clover can help troubleshoot issues once the app is in production use, you must maintain a record of each transaction. The identifier of each transaction is passed as the ExternalId and provides the link between your system and Clover. Each transaction response includes the same string in the ExternalPaymentId field.

Functional demonstration video

To assist Clover with the review of your app, we highly recommend recording a video showing how your app works and its major features. This video will help the approval team understand the way merchants will use the app and assess its features against your privacy policy. Note that this video is separate from the payment flow videos used to validate your integration's use of the SDK.

Payment flows

Your application must successfully process the payment flows supported by your integration. A video showing your POS' interaction with the Clover device is required for each transaction type. For complete testing instructions, see Testing Payment Flows.

๐Ÿšง

IMPORTANT

Partial authorizations

As required by the card associations we support, the Clover platform implements partial authorization functions for prepaid and debit cards. This function allows merchants to take a split-tender payment when a customer has insufficient funds to complete a transaction with the presented card. Semi-integrations for the US region must support partial authorizations in order for the integrated application to be approved.

The following tables detail the transaction features available in Cloverโ€™s markets.

USA

Canada

Sale

๐Ÿ—ธ

๐Ÿ—ธ*

Auth

๐Ÿ—ธ

Partial auth

๐Ÿ—ธ

๐Ÿ—ธ

Pre-auth

๐Ÿ—ธ

Capture pre-auth

๐Ÿ—ธ

Void

๐Ÿ—ธ

๐Ÿ—ธ*

Payment refund

๐Ÿ—ธ

๐Ÿ—ธ*

Manual refund

๐Ÿ—ธ

๐Ÿ—ธ

Vault card

๐Ÿ—ธ

๐Ÿ—ธ*

Manual closeout

๐Ÿ—ธ

๐Ÿ—ธ

Read card data

๐Ÿ—ธ

๐Ÿ—ธ

Ireland

UK

Germany

Austria

Sale

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

Auth

Partial auth

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

Pre-auth

Capture pre-auth

Void

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

Payment refund

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

Manual refund

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

Vault card

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

Manual closeout

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

Read card data

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

๐Ÿ—ธ

Argentina

Sale

๐Ÿ—ธ

Auth

๐Ÿ—ธ

Partial auth

๐Ÿ—ธ

Pre-auth

Capture pre-auth

Void

๐Ÿ—ธ

Payment refund

๐Ÿ—ธ

Manual refund

Vault card

Manual closeout

Read card data

Updated about a month ago


Approval


Suggested Edits are limited on API Reference Pages

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