#hendie_api
coarse oysterBOT
đ 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/1347595160250351779
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
viral thunder
Hi, you can the API request and it could succeed as long as your network meets our network requirements to minimize timeouts.
I think there is a question behind the question. Can you add more context here? Are you seeing an issue after retrying?
twilit viper
so it will not break the confirm that will come because the terminal did in fact receive the initial request?
You understand we're talking about the timeout we get that's a false negative right? The second case on the page I referenced?
I can understand a retry when the reader did not receive the initial call - but the docs are not very clear about the second case.
and like I said, this was the first time we really encountered it, so we have not had any retry mechanism in place, and even if we did there is no easy way to simulate that case in testing
viral thunder
Ah, on the same page now. Let me look
Yeah, from looking around, that is right it should not break the confirm and you can confirm it here: https://dashboard.stripe.com/logs/req_IuoR5X7ogGjosq. If you retried the request, you'd likely would receive an error message indicating that the PaymentIntent is already confirmed/successful.