Clover Setup


Store Dynamics 2 Clover Integration Setup

Version 1.0 - August 27, 2026

This guide explains how to configure Store Dynamics 2 (SD2) to process credit and debit payments through a Clover PIN Pad using REST Pay Display over a secure local network connection.

The Clover merchant credentials are configured once in System Parameters. Each SD2 terminal is then configured with the network address and serial number of its assigned Clover device.

Information Required Before Installation

Item

Source

Notes

Clover Merchant ID

Clover merchant account

Must belong to the customer being installed.

Clover App ID

AM/PM secure deployment record

Must be from the approved production semi-integrated app.

Clover App Secret

AM/PM secure deployment record

Used only during the one-time code exchange. SD2 does not save it.

OAuth authorization code

Merchant authorization process

One-time and short-lived. Exchange it immediately.

Remote App ID (RAID)

Clover app settings

Use the complete RAID, not only the App ID.

Clover device serial number

Clover device

Required for X-Clover-Device-Id.

Clover device IP address

REST Pay Display/device network settings

Reserve a stable address in DHCP or assign a static address.

REST Pay Display port

Clover device

Default HTTPS port is 12346.

Clover production root certificate

Clover documentation

Install on every Windows POS workstation that connects to a Clover device.

Windows administrator access

Customer/site administrator

Required to install the trusted root certificate.

 

Do not send the App Secret, authorization code, access token, or refresh token by email or include them in support tickets. Do not place these values in the terminal PIN Pad profile.

Step 1: Prepare the Clover Merchant and App Authorization

  1. Confirm the merchant is using the production Clover environment.
  2. Confirm the Store Dynamics semi-integrated app is installed or authorized for that merchant.
  3. Confirm the Merchant ID, App ID, App Secret, and RAID all belong to the same production Clover app and merchant environment.
  4. Have an authorized merchant user complete Clover login and consent through the approved authorization process.
  5. Capture the authorization code returned to the configured OAuth callback.
  6. Exchange the code immediately. An authorization code is short-lived and cannot be reused after a successful exchange. Obtain a fresh code if an exchange fails.

If the merchant cannot sign in or cannot see the app, stop the installation and resolve the Clover account/app assignment first. Do not use a developer login in place of the merchant login.

Step 2: Configure REST Pay Display on the Clover Device

  1. Connect the Clover device and the SD2 workstation to the same local network.
  2. Open REST Pay Display on the Clover device.
  3. Open the REST Pay Display menu and select Settings.
  4. Confirm Server is Secured is enabled. HTTPS is required for production.
  5. Confirm Server Port is 12346 unless the site has approved a different port.
  6. Select Configure and Restart Server after making any change.
  7. Return to REST Pay Display and make sure the server is running and the device displays its HTTPS server address or welcome screen.
  8. Record the device IP address and device serial number.
  9. Configure a DHCP reservation or static IP address so the Clover address does not change after a restart.

SD2 uses the REST Pay Display HTTPS server port. The WebSocket port is not entered in the SD2 terminal configuration.

Step 3: Install the Clover Production Certificate

Local HTTPS connections require Windows to trust the Clover certificate authority that issued the device certificate.

  1. On every SD2 workstation that will connect to Clover, download the production certificate from:

https://www.clover.com/v2/env_device_ca_certificate.crt

  1. Right-click the certificate and select Install Certificate.
  2. Select Local Machine. Administrator permission is required.
  3. Select Place all certificates in the following store.
  4. Select Trusted Root Certification Authorities.
  5. Complete the wizard and accept the security confirmation.
  6. Close and restart SD2 after installing the certificate.

Do not disable certificate validation and do not use an unsecured HTTP profile in production.

Step 4: Configure Clover in SD2 System Parameters

  1. In SD2, go to Back Office -> System Parameters -> Authorization.
  2. Set Credit / Debit to Clover.
  3. Enter the Clover Merchant ID.
  4. Under Clover Configuration, enter the Clover App ID.
  5. Enter the one-time Clover Authorization Code.
  6. Enter the Clover App Secret.
  7. Select Exchange Clover Code.
  8. Confirm the message: Clover token exchange completed successfully. The credentials were saved to the database.
  9. Select Save on the System Parameters page.

SD2 exchanges the authorization code for an access token and refresh token. The token pair and expiration dates are encrypted and stored in eSystemParameter3. The access token, refresh token, and expiration fields are intentionally hidden. The authorization code and App Secret are temporary and are not saved.

If the exchange fails, verify that the Merchant ID, App ID, App Secret, authorization code, and OAuth environment match. Obtain a new authorization code before retrying if the previous code has expired or was already used.

Step 5: Configure Each SD2 Terminal

Repeat this step for every till and its assigned Clover device.

  1. Go to Back Office -> Settings -> Terminal.
  2. Open the terminal record for the workstation.
  3. In PIN Pad, enter the local Clover profile in this format:

https://DEVICE-IP:12346/connect;PosId=CLOVER-RAID

   Example:

https://192.168.11.106:12346/connect;PosId=SPONSORCODE.CLOVERAPPID

  1. In Clover Device Serial Number, enter the serial number of the Clover device assigned to this terminal.
  2. Select Save.

Important:

  • PosId must contain the complete Clover Remote App ID (RAID), including both portions separated by a period.
  • Do not replace the RAID with only the Clover App ID.
  • Do not add the OAuth access token, refresh token, Merchant ID, or App Secret to the PIN Pad profile.
  • Use a separate device serial number and IP address for each Clover device.

Step 6: Verify the Local Connection

  1. On the Clover device, open REST Pay Display and confirm the server is running.
  2. In SD2, open the till and select Function -> Pinpad Status.
  3. SD2 sends a device ping and then returns the Clover device to its welcome screen.
  4. Confirm the status check succeeds without creating a payment or printing a zero-dollar payment receipt.

The status check uses:

POST https://DEVICE-IP:12346/connect/v1/device/ping

A successful connection returns connected: true.

Troubleshooting

Message or symptom

Checks and corrective action

Unable to connect to the Clover PIN Pad

Confirm the device is powered on, both devices are on the same network, the IP address is correct, port 12346 is reachable, and REST Pay Display is running. Check for guest-network or wireless client isolation.

SSL/TLS trust relationship or invalid certificate

Install the correct Clover production root certificate in Local Machine -> Trusted Root Certification Authorities, then restart SD2. Confirm the device is using the production certificate.

REST Pay Display is not running

Open REST Pay Display, start or restart its server, and wait for the welcome screen/server address before testing again.

Invalid URI

Confirm the PIN Pad profile is exactly https://IP:PORT/connect;PosId=RAID. Also confirm REST Pay Display has completed startup.

Protocol Request Orchestration stopped or PIN Pad busy

Complete or cancel the action on the Clover device, return to the welcome screen, and retry. Restart REST Pay Display if no active action is visible.

HTTP 401 Unauthorized

Check the Clover log for an OAuth refresh attempt. Confirm the Merchant ID, App ID, RAID, and token pair belong to the same merchant, app, and environment. Reauthorize if the refresh token is invalid.

Failed to validate authentication code

The code is expired, already used, or belongs to a different App ID/environment. Obtain a new code and verify the App ID before exchanging it.

Error connecting to payment gateway while ping succeeds

The local SD2-to-device connection is working. Check the Clover device's internet connection, merchant activation, payment application status, and Clover processing service. Escalate to Clover when required.

Payment request was canceled

The user canceled on the Clover device or the device canceled the request. Confirm no approved payment exists before attempting another payment.

Device serial number does not match

Correct the Clover Device Serial Number in the SD2 terminal record. Do not use the merchant ID or app ID in this field.

 

Final Installation Checklist

  • Clover merchant authorization completed.
  • Production Merchant ID, App ID, App Secret, and RAID verified.
  • REST Pay Display installed, secured, running, and using port 12346.
  • Clover device has a stable IP address.
  • Clover production root certificate installed on every applicable SD2 workstation.
  • Credit / Debit set to Clover in System Parameters.
  • Authorization code exchanged successfully and System Parameters saved.
  • Each terminal has the correct HTTPS PIN Pad profile, RAID, and device serial number.
  • Pinpad Status succeeds.

Tag: