#lnlinh31_api
thin heronBOT
đ 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/1303510218633908234
đ 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.
- lnlinh31_api, 13 hours ago, 5 messages
spice otter
Hi there. We don't reopen threads but happy to pick up where we left off
vocal oyster
Hi, I see that on your docs you sent me before https://docs.stripe.com/disputes/prevention/card-testing
But I see that your captcha implement on POST /v1/payment_intents/pi_xxxxxxxxxxxxxx/confirm not work, an attacker can re-sent multiple times with a single captcha token
spice otter
I can't speak to specifics on the automated controls used for this particular PaymentIntent