The Payment Card Industry PIN Transaction Security version 4 (PCI PTS-4) regulation requires payment terminals to restart every 24 hours. This restart is to reset cache and terminal data.
The terminals available with the Worldpay Integrated Payments service comply to PTS-5 and above, and are therefore subject to this regulation.
Without action from you, the terminals automatically restart 24 hours after their last restart time. This automatic restart occurs even if the terminal is processing transactions at the time.
You can control the terminal restart, and set the restart to a time of day when there is no activity. There are two ways to do this 24 hour reset:
IPC Controlled Restart – The payment terminal automatically restarts every day between 2am to 6am local time as part of the IPC scheduled updates process.
POS controlled Restart – This will be available soon. When available, you, the merchant, can send a request from the Electronic Point Of Sale (EPOS) application to restart the payment terminal. This request must be integrated within the EPOS application.
These two methods are described in detail below.
Before the scheduled updates process begins, IPC first checks if it is busy - which means a transaction is in progress.
a) If busy - Retry after a five second interval. If found busy then continue the retries. b) If not busy - IPC calls the scheduled updates process and issues a reset command, sets the terminal’s date & time and displays the IPC welcome message on the terminal.
Following a successful restart of the terminal, IPC runs as normal and processes any updates scheduled for that paypoint.
After 70 minutes, IPC will repeat step 1 and IPC will again issue a reset to the payment terminal. a) If busy - Retry after a five second interval. If found busy then continue the retries. b) If not busy - IPC calls the scheduled updates process and issues a reset command, sets the terminal’s date & time and displays the IPC welcome message on the terminal.
The POS controlled restart process is being developed and should be available soon.
Feedback or bugs to report?
Ask our developer community.
Search our documentation, API references and articles.