#helloferrukh-terminal
1 messages · Page 1 of 1 (latest)
cc @jaunty lion sorry I'm drowning
@dawn blade Can you clarify what you mean by "stops working"? What's the behavior you're seeing?
@jaunty lion terminal processes the payments for some orders and then stops responding
Do you have an example reader serial number I can take a closer look at in addition to a specific time range during which you were seeing issues?
helloferrukh-terminal
Time range is January 2024, what do you mean by example reader serial number?
are you asking for the serial number of the real device that is being used?
I'd want a more specific time range than that (like a couple of hours) - and yes, the serial number of a realy device that's being used that's not working as you expect
serial number WSC513212023993
I am not exactly sure about the hours but the issue occurred on 8th January and the last successful payment was at 7:01 PM UTC
Have you used that rader for a payment yet? I've tried looking around a few different places but I'm not seeing any reader on our end that matches that. Alternatively if you have a Payment Intent ID I can take a look at instead that would also work
This reader is being used by client for some time and it worked fine when they were collecting payments manually before.
Here is the last Payment Intent ID pi_3OWOCZDJwwYPBsng00IPTJgJ
Ah I see - this reader hasn't been successfully used since the 8th. My queries weren't going back far enough
Looking at our logs I don see a large number of timeouts/failure to connect - has anything changed about their setup (especially on the network side) since the 8th?
we had the same doubt and requested the client to check their network connections but there were no changes at the network end as all other network based operations were working fine
Hello! I'm taking over and catching up...