#bwurtz999 - terminal connection
1 messages ยท Page 1 of 1 (latest)
Hello, can you tell me more about where you are seeing that the location can't connect, and where the reader shows up as online?
This problem has been going on for a week or so. Our app connects to the reader, accepts payment, everything is fine. But then a few hours go by and the card reader becomes unresponsive
In my 'Connect' section I can 'View As' and see that the reader is actively pinging Stripe
We run this app in a dozen other units. None of them have this issue
We thought it might be an issue with the iPad, so last week we bought a new iPad. Same problem keeps happening
Gotcha. Do you have the ID of this terminal?
And when you say it becomes unresponsive, is that the actual device completely freezing, certain API calls to it failing, or something else?
Items get scanned. They show up in the cart. But nothing shows up on the terminal reader screen
tmr_EprbvQwsbsWk9l
Thanks for the ID. And I am less familiar with how that kind of setup might work. Have you checked your logs on whatever machine handles the cart to see if it is getting any errors related to updating what is on the terminal?
I have checked. There are no errors
The payment intents are being updated when items are added
Do you have one of the IDs of one of those payment intents as well?
pi_3LFGs1E46hUZZRHV0ZzmxdFb
Thank you!
Thank you
Any ideas about what could be going on here?
What's so frustrating is that it's the same app and card reader at all of our other locations. And they don't have this issue
Yeah I can imagine. I am checking in to the logs that we see on our side about the terminal and will also likely reach out to a colleague for how to better troubleshoot this. I am not immediately sure on what is going wrong here or where you may want to look next
OK thank you. Any ideas would be greatly appreciated
Has this terminal been able to make any payments? I am looking at what we see on our side for it. I see that somewhere we say we have not seen that terminal in a few days but that doesn't sound right given what you have seen
Have you checked its connectivity settings? I do see failed connection errors in our logs for that terminal as recently as today
Oh interesting
So we had someone go to the unit and restart it. That was about 10 minutes ago
Last week, when the app was working and I could see that the reader was 'online', I had someone run this test
0-4-2-6-8
and this one
0-8-6-2-4
And both tests passed
But the reader screen stayed blank when items were added
Are you using LAN or a Wifi connection here? My colleague brought up that Wifi connections are still in beta for this kind of reader so wifi may be less reliable on them. https://stripe.com/docs/terminal/payments/setup-reader/verifone-p400#:~:text=Connecting over WiFi is a beta feature. For production use%2C have an Ethernet connection ready as a backup%2C in case of degraded networks or connectivity issues.
Interesting. Will pass that on
The reader is now 'working' but if this pattern holds in a few hours it won't work anymore
It was on wifi
Gotcha.
All good info thank you.
But this reader has been able to make payments since the 23rd? I may have misunderstood something in our logs
What's tough is that is is a self-checkout system so there isn't a cashier there to tell me exactly when it stops working
The reader made it's first successful payment on May 26th
In looking at the logs (and all the payment intents that were updated but never completed) it looks like this has been an issue ever since it was first installed
The client only alerted us to this two weeks ago
We had someone go over there this morning and power it off/on and now it's connected and accepting payments (pi_3LFKJpE46hUZZRHV0D1OY2vs for one example)
But at some point this afternoon it will probably stop working
Gotcha. This is starting to sound like the device may be faulty but I am trying to think of how else to verify what is happening here. Do you know if the device is completely frozen and doesn't react to anything or is it more that the cart specifically isn't updated?
@dense hawk sorry for the delay
Nothing appears to be visibly wrong
But I've added additional logging and I can see that the 'addToCart' call is reaching the JS
๐ @dense hawk had to head out, but let met catch up and try and see what's wrong
awesome thank you!
@winged rapids Any update here?
Not yet - trying to sort through some logs here, so it's taking a while
Got it thank you
It's odd - I'm not seeing any of the logs I'd expect around the timestamps for pi_3LFGs1E46hUZZRHV0ZzmxdFb
A couple of questions - just to confirm, your application automatically handles disconnections, right?
And has your client mentioned anything about them using multiple POS devices with this one reader?
I don't know if my app handles disconnections, which I'm going to guess means that it does not
Does the JS library include a function to handle disconnections?
There is only one POS device at this location, and it's ours
Sorry by POS device I mean laptop or desktop that the reader connects to - not the reader itself
In terms of handling disconnections - have you read through this (https://stripe.com/docs/terminal/payments/connect-reader?terminal-sdk-platform=js&reader-type=smart#handling-disconnects) ? The Stripe library doesn't automatically reconnect, but we do offer callbacks when the reader is disconnected so that you can update your app to indicate the reader isn't connected anymore and restart the connection process
No, there is only one
I definitely don't have unexpectedDisconnect configured
I will get that configured
Do you have any idea what is causing the disconnects though?
It's only happening at one location
It could be anything - given that it's just at that location I'm guessing it has to do with their wifi setup