#vmehtawhq_api

1 messages · Page 1 of 1 (latest)

alpine remnantBOT
#

👋 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/1287620113952149504

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

pearl cove
fiery ermine
#

This isn't an API to Stripe. Stripe request ID should look like req_xxx. Could you share the Stripe request ID, so that I can take a look why this error occurred? Here’s how you can find it: https://support.stripe.com/questions/finding-the-id-for-an-api-request

pearl cove
#

This is stripe js sdk that's making call for reader I think.

#

Are readers handled by 3rd party company?

fiery ermine
#

Oh sorry! JackRabbitService is an internal service

pearl cove
#

yeah

fiery ermine
#

Stripe readers are self-owned. Could you share the terminal ID (tmr_xxx), so that I can look into it further?

pearl cove
#

Yeah, give me a sec

fiery ermine
#

Does this error only occur recently? Or is it intermittent?

pearl cove
#

I am not sure about the terminal id here, this screenshot was taken at customer's end and support agent took this screenshot. Should be one of these terminals: tmr_Ft1KWQqDEMJhjQ, tmr_Ft0qDQboV71sZy.
There's also one in screenshot.

#

This is the first time seeing this

fiery ermine
#

Are all terminals facing the same issue? Or just the one in the screenshot?

pearl cove
#

Just heard from one only for now

fiery ermine
#

The one in screenshot was tmr_Ft0r9w8iXIP70H. Looking into it now

alpine remnantBOT
fiery ermine
#

I'm able to see the same error log at our end. The issue is unlikely due to an integration issue since other readers are working fine. Can I suggest you writing to Support https://support.stripe.com/contact with the terminal serial number or terminal ID with the issue and screenshot, so that we can check with the relevant team?

pearl cove
#

Sure, could you confirm which terminal id it is and any log reference or anything else that you want to give me to add to that ticket.

fiery ermine
#

The terminal ID is tmr_Ft0r9w8iXIP70H (serial number WSC513124016693). The log reference would be the error in the screenshot

pearl cove
#

Thanks, that helps!

fiery ermine
#

No problem! Happy to help 😄