Step 4: Approval

You must have an approved production developer account before Clover can approve your apps. Create a separate production developer account for each country or region in which you want to create apps. The Clover App Market team reviews and approves each developer account you create on a production environment. You can launch an integrated app for a merchant after both the app and the associated developer account are approved.

Complete the steps in the following sections to complete the approval phase:

1. Submit a production developer account for approval

Your application is linked to a production developer account, and this account needs to be verified and approved before testing can begin. You can continue to test your app on sandbox until it is ready for production. You can also set up your Dev Kits to use in the sandbox for testing.

To complete this step, the semi-integration team must be able to verify your identity as an Individual developer or Corporate developer.

Individual developer

If you are an individual submitting a semi-integrated app:

  1. Log in to your US Clover developer account or EU Clover developer account.
  2. From the left navigation menu, click Developer Settings.
  3. On the Developer Info page, enter information in the following sections:
  • Identity Verification fields
  • 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 displays the date and time of your submission and verifying account status. You also receive an email confirmation that your account is submitted.
830830

Status bar with submission time

Corporate developer

If you are submitting a semi-integrated app as a company:

  1. Log in to your US Clover developer account or EU Clover developer account.
  2. From the left navigation menu, click Developer Settings.
  3. On the Developer Info page, click the Account Details row.
    The Edit Account Details page appears.
  4. From the I'm doing business as an drop-down list, select Business.
  5. Complete the required business information fields, and then click Save.
  6. On the Developer Info page, enter information in the following sections:
  • Identity Verification fields
  • 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 displays the date and time of your submission and verifying account status. You also receive an email confirmation that your account is submitted.
830830

Status bar with submission time

2. Recreate your app in the production Developer Dashboard

  1. Log in to your US Clover developer account or EU Clover developer account.
  2. On your app's Settings > Semi-Integrated App page, select Generate RAID. A valid Remote App ID is generated.
  3. Complete the required details.
  4. In your app description, add your points of integration with Clover, for example: Sale, Auth, Void, and so on.
  5. Enter a valid phone number for customer support, along with the hours during which support is available.

3. Record your payment flow videos

  1. See Test payment flows and verify your application can successfully pass the required tests.
  2. Record a video of each payment flow.

4. Submit your application using your production developer account

During the development phase, you test your application in the Clover sandbox environment, without impacting live merchants. Once ready for approval, your application is submitted for approval in the production environment.

  1. Log in to your US Clover developer account or EU Clover developer account.
  2. On the Your Apps tab, find your app, and click Details.
  3. On the Details page, verify the information for your app, such as:
  • App name
  • Tagline
  • Description
  • Icon
  • EULA
  • Support email address
  • Support website
  • Support phone number
  • Two or more app benefits
  • One or more screenshots
  • Required. Link to your privacy policy and your terms of service or end user license agreement. These documents are verified for compliance with Clover's Developer Legal Guidelines.
  1. Click Submit.
  2. Clover reviews your application and checks for compliance with the following:

5. Demonstration of your application

Compatibility verification check points

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 are verified.

PlatformVerification
Remote application ID (RAID) configurationYour 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 the sandbox environment).
Record keeping using an external IDTo ensure Clover can help troubleshoot issues once the app is live in production, 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.

Videos

Video typeDescription
Functional demonstration videoTo assist Clover with the review of your app, we highly recommend recording a video of how your app works and its major features. This video helps the approval team understand how merchants will use the app and assess its features against your privacy policy.

Note: The functional demonstration video is separate from the payment flow videos used to validate your integration.
Payment flow videoYour application must successfully process the payment flows supported by your integration. A video demonstrating how your POS interacts with the Clover device is required for each transaction type. For complete testing instructions, see Test payment flows.

Support for partial authorizations (US region)

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.

🚧

Important:

Semi-integrations for the US region must support partial authorizations for the integrated application to be approved. ou need to include the Clover paper receipt from your partial auth testing.

The following tables detail the transaction features available in Clover’s markets.
North America region

USACanada
Sale:white-check-mark::white-check-mark:*
Auth:white-check-mark:
Partial auth:white-check-mark::white-check-mark:
Pre-auth:white-check-mark:
Capture pre-auth:white-check-mark:
Void:white-check-mark::white-check-mark:*
Payment refund:white-check-mark::white-check-mark:*
Manual refund:white-check-mark::white-check-mark:
Vault card:white-check-mark::white-check-mark:*
Manual closeout:white-check-mark::white-check-mark:
Read card data:white-check-mark::white-check-mark:

European region

IrelandUKGermanyAustria
Sale:white-check-mark::white-check-mark::white-check-mark::white-check-mark:
Partial auth:white-check-mark::white-check-mark:
Pre-auth
Capture pre-auth
Void:white-check-mark::white-check-mark::white-check-mark::white-check-mark:
Payment refund:white-check-mark::white-check-mark::white-check-mark::white-check-mark:
Manual refund:white-check-mark::white-check-mark::white-check-mark::white-check-mark:
Vault card:white-check-mark::white-check-mark:
Manual closeout:white-check-mark::white-check-mark:
Read card data:white-check-mark::white-check-mark::white-check-mark::white-check-mark:

LATAM region

Argentina
Sale:white-check-mark:
Auth:white-check-mark:
Partial auth:white-check-mark:
Pre-auth
Capture pre-auth
Void:white-check-mark:
Payment refund:white-check-mark:
Manual refund
Vault card
Manual closeout
Read card data

6. Submit your application information and videos by email

Once your application is ready, send an email to [email protected] with the following information:

  • Developer name
  • Company/organization
  • Production developer account ID
  • Production Remote Application ID
  • Region—US, Canada, Argentina, or UK/Ireland
  • SDK—Windows, Android, Cloud, iOS, or Go
  • If using Windows, the service used by your app—REST, WebSocket, or Clover Mini DLLs
  • Pay Display app—USB, Cloud, Secure Network, or other
  • List your integration's features:
    -- Automatic partial payment (insufficient funds, required in US)
    -- Sale
    -- Auth & tip adjust (supported in US only)
    -- PreAuth & capture (supported in US only)
    -- Vault card (supported in US only)
    -- Manual refund
    -- Payment refund
    -- Void
    -- Customized display order, for example, discounts or line items/no line items
    -- Manual card entry
    -- First Data gift cards
    -- EBT cash
    -- Pre-sale tipping
    -- Tips on paper
    -- Printing Clover receipts
    -- Reprinting receipts
    -- Customized Clover receipts, example: add a logo or taglines, or remove line items
    -- DisableReceiptSelection transaction setting to skip printing Clover receipt
    -- AutoAcceptSignature transaction setting to skip signature verification
  • Attach or link to videos for your apps payment flows