#alberto_error
deep ivyBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1247863044575596605
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
severe pilot
hi! probably just a random network blip if it only happened once.
heavy silo
ok. We will try again tomorrow and we will monitor the reader. In case we have the same issue I will write you again
severe pilot
I'd also recommend implementing a try/catch and retry API requests like that which fail(see https://docs.stripe.com/terminal/payments/collect-card-payment?terminal-sdk-platform=server-driven#handle-errors ).
heavy silo
ok. Thanks. I tried again several times but we get the same issue until we restarted the reader
deep ivyBOT
grave stump
One thing to try if this is intermittent is to ensure our Terminal domains are all reachable from your network: https://docs.stripe.com/ips#stripe-terminal-domains
heavy silo
I will take into account what you tell me although there are no changes on our side. All I do is restart the reader. The network is still in the same state. If I could not communicate with the domains I understand that I would always have the problem.
I will try again tomorrow and next days
If I have problems I will write you again with more details if I can
Thank you
grave stump
I'd recommended writing in to our team with as much detail as possible (code, errors, etc) and we can take a deeper look: https://support.stripe.com/contact/email?topic=api_integration