#bwurtz999
1 messages · Page 1 of 1 (latest)
Hello bwurtz999, we'll be with you shortly! Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
• bwurtz999, 4 days ago, 14 messages
Is someone able to look into this for me?
Hi 👋
Sorry for the delay
Let me take a look
The request is successful in that the API is able to respond and you provided the correct parameters. The message it is returning is that the reader is having an error (which is unrelated to the API in this case)
Right... any advice on fixing it? The reader was restarted and the problem persists
Does this mean it's a hardware problem? Does the reader need to be replaced?
Taking a look at the reader logs
I am seeing transaction timeout errors as well as network disconnections
You think it's a network issue? It shows as online in the Dashboard
And the reader itself shows as connected to Wifi and the network tests are positive
I am reporting what I am seeing in the logs. I see a number of cancelation requests and transaction timeouts
What do you mean cancelation requests?
Let me widen the log search.
As for cancelation requests, there are API errors when the integration sent an API request to cancel a payment but there was no active payment in process to cancel.
Specifically something like this: https://stripe.com/docs/terminal/payments/collect-payment?terminal-sdk-platform=server-driven#payment-cancellation