Release NotesAnnouncementsBlogFAQSupport
Guides

Configure Secure Network Pay Display

United States
Canada
Europe
Latin America

Secure Network Pay Display (SNPD) has several configuration options that can be set as required for your integration.

Access Clover device server settings

  1. Open the Network Pay Display app.
  2. Tap the menu icon and then tap Settings. The Clover Device Server settings appear.
1280

Clover Device Server settings page

From here you can:

Select the connection protocol

By default, the connection between a point of sale (POS) and Clover device is over WebSocket Secure (WSS). The Clover Device Server also supports an unencrypted WebSocket (WS) connection. A non-secure WS connection should only be used if needed for development and testing. WSS connections must be enabled in production.

To change the connection type:

  1. Access Clover device server settings.
  2. Select the Server is Secured checkbox. Click Configure and Restart Server.
    The Server is Secured checkbox enables and disables the secure connection between the POS application and Clover device. The lock icon changes from green to red. On the Network Pay Display screen, the device URLs change from Web Secure Socket (wss://) to Web Socket (ws://). Clover recommends that you select the Server is Secured checkbox.
1535

WebSocket (WS) settings

Edit the server port

By default, the connection between a point of sale (POS) and Clover device uses port 12345.
To edit the server port:

  1. Access Clover device server settings.
  2. Click Server Port. The Enter Server Port Number window appears.
  3. Enter a new port number.
  4. Click Save.
  5. Click Configure and Restart Server. The port change is applied.

📘

NOTE

If the new port is used by another process on the Clover device, an Address already in use message appears. To correct this issue, repeat the steps with a different port number.

Edit device ping settings

  1. Access Clover device server settings.
  2. To change the device ping settings, edit one or more of the following values:
SettingDescription
Enable Ping checkboxWhen selected, the device checks that the connection is open at the specified interval.
Ping IntervalLength of time between pings (in milliseconds).
Ping Retry Before DisconnectNumber of times the server will attempt to ping the client before disconnecting.
  1. Click Configure and Restart Server. The device ping settings are changed.

Edit length of auth token validity

You can set the number of days a pairing code is valid for your environment. Once the interval elapses, a new code must be entered.

  1. Access Clover device server settings.
  2. Click Auth tokens valid for. The Enter # of Days window appears.
  3. Edit the number and then click Save.
  4. Tap Configure and Restart Server. The validity interval is changed.

Work with the device pairing screen

Enable the pairing screen

You can choose to display a screen which provides three ways to pair the device: a QR code, the device DNS name, and the device IP address.

  1. Access Clover device server settings.
  2. Select the Enable pairing screen checkbox.
  3. Select Configure and Restart Server.

Use the pairing screen

If the pairing screen is enabled, the Initiate Pairing button displays on the Network Pay Display screen.

Tap Initiate Pairing to show the pairing screen.

1280

Initiate Pairing button

Work with device server certificates

To establish trust between the point of sale (POS) and the device server certificate issued by the Clover CA, you must install a Clover Device Server Root CA certificate on the POS. Clover provides separate certificates for development and production use.

🚧

IMPORTANT

The certificate must be installed in the Trusted Root Certification Authorities store. If the certificate is not installed in the correct store, a certificate chain error message appears when you attempt to connect.

Sandbox (development)

The device server certificate is issued by the Clover Device Server Root CA. The CA certificate is hosted at:

Certificate URLs (links) for development:

  1. https://sandbox.dev.clover.com/v2/device_ca_certificate
  2. https://sandbox.dev.clover.com/v2/device_ca_certificate.der
  3. https://sandbox.dev.clover.com/v2/device_ca_certificate.crt

Production

The device server certificate is issued by the Clover Prod Terminal Server Root CA. The CA certificate is hosted at different locations for each region—United States (US), Europe, and Latin America (LATAM):

EnvironmentCertificate URL
United States production1. https://www.clover.com/v2/env_device_ca_certificate
2. https://www.clover.com/v2/env_device_ca_certificate.der
3. https://www.clover.com/v2/env_device_ca_certificate.crt
Europe production1. https://www.eu.clover.com/v2/env_device_ca_certificate
2. https://www.eu.clover.com/v2/env_device_ca_certificate.der
3. https://www.eu.clover.com/v2/env_device_ca_certificate.crt
Latin America production1. https://www.la.clover.com/v2/env_device_ca_certificate
2. https://www.la.clover.com/v2/env_device_ca_certificate.der
3. https://www.la.clover.com/v2/env_device_ca_certificate.crt

Edit device certificate for development

By default, the device server certificate is issued by the Clover Prod Terminal Server Root CA. When you are working in the sandbox environment, change your CA using the following steps:

  1. Access Clover device server settings.
  2. Select the Enable Development Certificate checkbox.
  3. Select Configure and Restart Server. Once the server is restarted, the CA is updated.
  4. Select View Certificate Details and verify that the device certificate is issued by the Clover Device Server Root CA.

View the current certificate

To see the complete device certificate, tap View Certificate Details.

See the device certificates FAQ for more information.

Updated over 1 year ago