#bwurtz999
1 messages · Page 1 of 1 (latest)
The report I am getting from my manager is that this happens after trying to update the reader screen
It's a server-driven integration
Looks like req_1BAA9t3YMaeu3H is one example
what reader are you using?
ok will take a look, will be back shortly
just a quick Q, are you testing in live mode? or are these real customer transactions?
They are real
ok so would you mind describing the scenario of what happened exactly
I'm trying to reconstruct this in my head
I am not on site, but I spoke to the manager a few minutes ago. She reports that trying to add an item to the cart can take several minutes for it to show up on the reader screen
Other times, after trying to accept a card payment, the page will sit for some time and then throw an error and reset
ok so from what I see this request https://dashboard.stripe.com/logs/req_A9DeiPE66NWkWB was running when the other one you shared was sent which explains the message
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
basically you can't cancel a reader action while they're processing a payment
Can you give me the request IDs that were running concurrently?
I'm not sure why it's taking that much time to process the card payment, but this is a separate issue
I can't figure out how to recreate this locally to try and fix it
the one you shared req_1BAA9t3YMaeu3H
it's a matter of disabling the button to "cancel action" while the reader is processing the payment
Yeah but why would the reader screen be taking so long to update?
I use the same app in other locations and it is working fine
maybe it's a connection issue or plenty of other factors could be at play here(e.g. taking the issuing bank some time to authorize the payment, etc.)
OK
But so for the request I shared, you're saying that the reader was attempting to process a payment intent and another request was sent to try and set the screen
Is that right?
yes