We develop POS software that integrates with multiple payment terminals. It is developed with .Net framework and operates on Windows 7 POSready and Windows 10.
Recently one of our merchants has been reporting an issue where the Clover terminal will display the wrong price and then the remote pay display app will crash saying "Pay display isn't responding". One important note is that this does not happen all the time, it will happen randomly at least once a day.
We use a common interface across all of the payment terminals integrations, so the same price data is sent across integrations. We have been able to eliminate the main program as the cause of the problem, which narrows it down to our CloverConnector implementation or some issue with the payment terminal itself.
Our CloverConnector implementation follows the .Net example relatively closely except for some necessary changes like disabling receipts when needed and other minor settings.
We initially suspected the Clover unit was defective however, the store uses two terminals and two POS systems and this issue has affected both of them.
None of our other merchants have reported this issue with our Clover semi-integration, nor have we had any wrong price issues with any other integration.
Has anyone encountered this issue before or knows the potential cause?
Are there any common pitfalls that could lead to this issue?
