#dasboss_code
dull dawnBOT
👋 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/1442695001950650378
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
dawn marsh
While the QR code is displayed, we programmatically cancel the transaction. To do this, we use stripe.terminal.readers.cancelAction and stripe.paymentIntents.cancel.
Immediately after the cancellation, we attempt to start a new payment p
Could you continue here? Looks like the text is cut off
When the QR code is displayed, did the customer pay via PayNow at the same time you programmatically call those Cancel APIs?
scenic epoch
Let me show you the full message.
Issue Description:
We are encountering a reader_error when we attempt to start a new payment immediately after canceling a previous payment action where a PayNow QR code was displayed on the terminal. The reader appears to enter an unrecoverable error state.
Steps to Reproduce:
We initiate a payment by creating a PaymentIntent and then calling stripe.terminal.readers.processPaymentIntent.
The payment method is PayNow, and the terminal reader correctly displays the PayNow QR code for the customer.
While the QR code is displayed, we programmatically cancel the transaction. To do this, we use stripe.terminal.readers.cancelAction and stripe.paymentIntents.cancel.
Immediately after the cancellation, we attempt to start a new payment process by creating a new PaymentIntent and calling stripe.terminal.readers.processPaymentIntent again.
This second attempt fails, and we receive a terminal.reader.action_failed webhook event.
Error Details:
Event Type: terminal.reader.action_failed
failure_code: reader_error
failure_message: This action could not be completed due to an error on the card reader.
Expected Behavior:
After a successful cancelAction, the terminal reader should return to an idle state, ready to process the next processPaymentIntent command without any errors.
Actual Behavior:
The reader fails to process the subsequent payment request and returns a generic reader_error. It seems that canceling the PayNow QR action does not properly reset the reader's state, leaving it unable to accept new commands.
Relevant API Calls We Use:
To Initiate Payment:
stripe.paymentIntents.create
stripe.terminal.readers.processPaymentIntent
stripe.checkout.sessions.create
To Cancel Payment:
stripe.terminal.readers.cancelAction
stripe.paymentIntents.cancel
stripe.checkout.sessions.expire
We are writing to report an issue we are experiencing with our Stripe Terminal integration using the Node.js SDK.
Environment:
Platform: Node.js
Integration: Stripe Terminal
Payment Method involved: PayNow
Could you please advise if this is a known issue or if there is a specific sequence of API calls required to gracefully cancel a PayNow QR action and ensure the reader is ready for the next transaction?
Any help you can provide would be greatly appreciated.
Thank you,
scenic epoch
acct_1SI0LnGyoHPd4DQ0
dawn marsh
Okie, and
Expected Behavior:
After a successful cancelAction, the terminal reader should return to an idle state, ready to process the next processPaymentIntent command without any errors.
Actual Behavior:
The reader fails to process the subsequent payment request and returns a generic reader_error. It seems that canceling the PayNow QR action does not properly reset the reader's state, leaving it unable to accept new commands.
Could you clarify how exactly was the reader after you cancelled instead of an idle state?
Did it go back to the home screen?
And could you provide the reader's Serial number?
scenic epoch
Yes, I checked. Hold on please
After we successfully called stripe.terminal.readers.cancelAction, the terminal's screen immediately cleared the PayNow QR code and returned to its default idle screen. (Stripe logo page)
Serial Number: STR70Z1C445002730
dawn marsh
Yeah that sounds just right.
This second attempt fails, and we receive a terminal.reader.action_failed webhook event.
Error Details:
Event Type: terminal.reader.action_failed
failure_code: reader_error
failure_message: This action could not be completed due to an error on the card reader.
Could you share the webhook event Id here? evt_xxx
scenic epoch
yes!
we_1SIfHLGyoHPd4DQ0Eyew60Q3
dawn marsh
I meant the Event Id of evt_xxx. But okie
Could you test it again, but only call stripe.terminal.readers.cancelAction and do not call stripe.paymentIntents.cancel?
dull dawnBOT
scenic epoch
We have attempted to make adjustments based on the feedback, but unfortunately, we are still observing the exact same behavior.
edgy brook
Hey! Apologies, i missed your reply! looking at this now
Could you send a video recording or screenshot of what is happening? This would allow us to further investigate the issue
Also, could i request consent to view your dashboard?
dull dawnBOT
Hello @scenic epoch, we have sent you a direct message, please check it at https://discord.com/channels/@me/1442770504229326869
- 🔗 The message has instructions on how to grant read and write access to your Stripe Dashboard for our Developer Support team, in order to help you more effectively.
scenic epoch
Okay, please wait a moment
gaunt peak
Hello, I'm taking over this issue now. And yes, you have our consent to access the dashboard.
edgy brook
I sent a DM to request consent to your dashboard
could you see if you received it and approve the request?
gaunt peak
Okay, access has been granted. Please check now.
edgy brook
Thank You! Could you also send a screenshot or video recording of the error you see on the terminal device?
gaunt peak
To be clear, the terminal device itself does not display any visible error messages on its screen.
The problem occurs specifically on the second payment attempt. When we initiate it, the payment screen appears on the terminal, but simultaneously, our server receives a terminal.reader.action_failed webhook.
The core issue is this unexpected terminal.reader.action_failed webhook on the second attempt. It disrupts our payment flow, even though the terminal screen appears to be functioning.
edgy brook
Hmm, after the first canceled payment, does the reader get stuck in a loading state for some time before the Stripe home display shows again?
Could i get you to write in to my team for this issue, we might need additional time to investigate this
I will be dropping you a DM on how you can do that, and we can take it from there. If you do write in, please provide:
- The steps you have already taken
- The relevant screenshots/video recordings
dull dawnBOT
Hello @scenic epoch, we have sent you a direct message, please check it at https://discord.com/channels/@me/1442770504229326869
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.