#bwurtz-terminal-error
1 messages · Page 1 of 1 (latest)
Hello! 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.
Give me a few minutes and I can take a look!
Thank you
Do you see anything happening on the reader-side/screen when you attempt to process the PaymentIntent?
And if you try doing other actions (like set the reader display https://stripe.com/docs/api/terminal/readers/set_reader_display) do those also fail in the same way?
Yes - nothing shows up
For what it's worth, I just got the same error with a different reader in testing
req_rpz1h1LgX7nCTz
This one corrected itself
And the reader is working again
But like I said, the one I'm having an issue with is still not functioning
It's been non-functional for hours now
Let me loop someone else in as well to help take a look
Yeah I'm surprised restarting didn't help here - is this the only reader you're aware of that's still actively failing like this? I know you mentioned another reader was faililng earlier, but that one resolved itself
The one that corrected itself is my test reader
And no, this is the only one having this issue
Out of 24 or so
We took a look and as far as we can tell, you're doing everything right integration-wise and the internal logs that we have available to us aren't telling us much about what's wrong. For the request you initially flagged (req_5GdMFBHrxBhcuZ) I'm guessing it's in that state because we're not even beginning the payment method collection proccess, but we don't know why your reader is still stukc on the Stripe splash screen and not continuing on as expected.
I'm gonna check with a couple other folks to see if they can think of anythign else, but if we can't find anything I may have to redirect you to support to follow up as they dig in more
👋 @dry fable we're going to flag internally for the product team to have a look but it looks like potentially a broken reader. I'd recommend reaching out directly to our support team for help instead: https://support.stripe.com/contact and providing the information you gave us (reader id, serial number, failed request_ids, when it started, examples of another reader that had this but it fixed itself, etc.)
And then they can follow up with a fix or a potential replacement of the reader