#morteza_terminal-bug
1 messages ¡ Page 1 of 1 (latest)
đ 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/1306642488769118289
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- morteza_account-riskrequirements, 2 days ago, 21 messages
yes
And the reader serial ID
wait please
Sure
there's no serial id, we run it on the mobile device with nfc
it was working just fine but today
Is this iOS or Android?
Okay and this is for just one device or across multiple devices?
all devices
Thanks, one minute
Okay I've escalated internally and we are investigating.
Thanks for surfacing this.
ok, thanks
any news
Does look like something broke on our end and our Terminal Eng team is looking into it with urgency.
I'll circle back as soon as I have more news.
ok thanks
The issue has been located and a fix is being worked on. Will hopefully be resolved soon.
thank you very much
@golden coyote I recommend you reach out to our support team on https://support.stripe.com/contact and they can keep you updated about the fix as it gets rolled out!