Configure Secure Network Pay Display
SNPD has several configuration options that can be set as required for your integration.
Access Clover Device Server Settings
To open the options page, do the following.
- Open the Network Pay Display app.
- Tap the menu icon and then tap Settings.
The Clover Device Server settings appear.
Change the connection protocol
By default, the connection between a POS and Clover device is over WebSocket Secure (WSS). The Clover Device Server also supports an unecrypted WebSocket (WS) connection. To change the connection type, complete the following steps.
A non-secure WS connection should only be used if needed for development and testing. WSS connections must be enabled in production.
- Tap the Server is Secured check box.
- Tap Configure and Restart Server.
The lock icon changes from green to red. On the Network Pay Display screen, the device URLs change from
Change the server port
By default, the connection between a POS and Clover device uses port 12345. The port can be modified by doing the following.
- Tap Server Port.
- On the Enter Server Port Number window, type a new port number.
- Tap Save.
- Tap Configure and Restart Server. The port change is applied.
If the new port is used by another process on the Clover device, an
Address already in usemessage appears. To correct this issue, repeat the previous steps using a different port number.
To change the device's ping settings, modify one or more of the following values.
|Enable Ping||When checked, the device checks that the connection is open at the specified interval|
|Ping Interval||The length of time between pings (in milliseconds)|
|Ping Retry Before Disconnect||The number of times the server will attempt to ping the client before disconnecting|
Change the length of auth token validity
The number of days a pairing code is valid can be set for your environment. Once the interval elapses, a new code must be entered.
- Tap Auth tokens valid for.
- On the Enter # of Days window, change the number and then tap Save.
- Tap Configure and Restart Server. The validity interval is changed.
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's DNS name, and the device's IP address.
- Tap the Enable pairing screen check box.
- Tap Configure and Restart Server.
Use the pairing screen
If the pairing screen is enabled, the Initiate Pairing button appears on the Network Pay Display screen. Tap Initiate Pairing to show the pairing screen.
Device server certificates
To establish trust between the 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.
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.
The device server certificate is issued by the Clover Device Server Root CA. The CA certificate is hosted at:
Certificate URLs for development
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 (US, EU, and Latin America):
Certificate URLs for US production
Certificate URLs for EU production
Certificate URLs for Latin America production
Change the 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:
- In the SNPD app settings, select the Enable Development Certificate option.
- Select Configure and Restart Server. Once the server is restarted, the CA is updated.
- 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.
Updated 2 months ago