#lnlinh31_api
warped pondBOT
đ 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/1303538540415684672
đ 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, 1 hour ago, 7 messages
- lnlinh31_api, 15 hours ago, 5 messages
ancient shore
The fraud detections for card testing have been in placed on Payment Element and Checkout: https://docs.stripe.com/disputes/prevention/card-testing#optimize-integration
However, your integration uses split Card Element in https://dashboard.stripe.com/logs/req_7l8rPU283Yxqr4, which the automatic fraud detections by Stripe aren't supported. You should implement the card testing preventions such as implementing CAPTCHA, limiting access to your payment form, adding rate limit, detecting and prevent unusual behavior by yourself with the guide here: https://docs.stripe.com/disputes/prevention/card-testing#prevent-card-testing
