#pocketJared
1 messages · Page 1 of 1 (latest)
HI 👋
I can test this out but I'm not certain what the expected behavior is in that case. Do you have the reader's serial number handy?
"WSC513128034182"
And the reader was restarted while it was showing the screen to collect card details?
Correct, it is restarted (or shut down) prior to collecting the card details.
That's odd. I restarted my WisePOSE on the Collect Payment screen and was able to complete a purchase immediately afterward
I can see, in the error. logs for your reader, a large number of canceled transactions though
Yeah I am still working thought the capturing piece so not surprised there are a large number of cancelled transactions.
I restarted my WisePOSE on the Collect Payment screen and was able to complete a purchase immediately afterward
After the restarted the device it prompted you to Tap, insert, or swipe to pay?
Mine defaults back to the splash screen, and when I query the api for my reader it claims to be processing the payment still.
I can send a new payment to the reader, just trying to find a reliable way to know what my reader is up to.
Sorry, my device restarted to it's neutral state. I had to send a new Payment Intent to it to trigger the payment screen again
So before sending the new intent, if you query the reader, the reader action status is still in_progress that is my issue.
I was hoping to prevent sending an intent to a reader that was in the middle of processing an intent, but after restarting my reader the reader still thinks it is processing an intent, hopefully that use case makes sense.
Interesting. And you are using a server integration, correct?
Correct
I was testing with my JS integration because it was faster. My reader goes to status: "online" immediately upon restart
I am specically taliking about
"action": {
"status": "..."
}
Got it. I am able to replicate now
I don't see a very clear way for you to determine exactly what happened with the reader
Well. except for listening for the terminal.reader.action_failed webhook event
You could then clear the action by using the Cancel current action endpoint: https://stripe.com/docs/api/terminal/readers/cancel_action
However, that request will fail until the reader comes online again
Shouldn't this happen after shutdown or restart automatically?
I noticed it happened automatically if I left my reader shutdown long enough.
My guess is there's a time out feature
However this is a good point. There may be other use cases to consider that would prevent this from being a good default but it's worth raising internally to get more information.
I have a less ideal workaround for now (a pop up to ask the user if they are really really sure as this is an edge case), but seems like something that should be updated automatically when the reader moves offline.
Thanks for the quick response and escalation internally!