This question was
closed
by
clover-community-bot for the following reason: automated
Lifespan of terminal pairing for Network Pay
When connecting to a terminal, the initial connection goes through the authorization process where a PIN is provided to enter on the terminal. What is the lifespan of the token returned? I need to know whether this is a process I can do from a management utility and store the value, or if it is more likely to change frequently (e.g., on terminal restart, or if terminal/POS is shut down every night etc.)..
The token returned in onPairingSuccess is specific to the Clover Device Server on that particular Clover device, and is one-time use. When it is consumed, a fresh authToken is returned in onPairingSuccess. The "shelf life" of a Clover Device Server authToken defaults to 30 days, but that is configurable in Secure Network Pay Display's settings. If the authToken is expired or otherwise rejected, onPairingCode will be called with a new pairingCode to enter on the device.
Thank you again
@racheladmin! I saw it was working on a rolling auth code every transaction and wanted to confirm. Definitely not something that can be pre-configured.
Once you have that first authToken to set, the swapping can happen in the background, so the merchant doesn't have to manually enter a pairing code again.
Welcome to the
Clover Developer Community
1 Person is following this question.
