#battbot_unexpected
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1245456203497341039
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello
Hi
Hmmm have you tested this on multiple Readers by chance?
no, this was reported by one of our merchants
Do you have the serial number of the Reader?
Okay and do you happen to have a video of what occurred? And have you tried to reproduce this in test mode?
there was no video
they provided a screenshot
they are saying on that screen, no user interactions was working
we were not able to reproduce this issue
Huh okay and this just happened once?
no they said it happened several times for them
only happens when the pin is entered incorrectly though
And you have other merchants that are live and accepting interac with your same integration?
And no other reports of this, correct?
not that i'm aware of
To which question above?
no other reports from other merchants
we have hundreds of merchants that this integration is working with
oh actually, for the App on device, only dozens
I don't really think Apps on Device should have any affect here tbh
Since this is just during the payment flow
we have no idea why this screen freezes, since our code isn't active on this step, either frontend or backend
that's why i'm bringing the question here
Yep it sounds like potentially that Reader is buggy
Like it sounds to me like a hardware issue
correct pin works though, hardware issues cause problems when pin is incorrect?
we had thought if hardware issue, maybe it has problems with pin entry and etc
I think hardware issues can manifest in a lot of different forms. But I think that is the place to start if this is the only report of this happening and you aren't able to reproduce it on your own device. My recommendation would be to write into our Support team via https://support.stripe.com/contact/login with these details and request a replacement device be sent.