#tidymince_unexpected
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/1306656206479429706
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello
Payment ID: pi_3QKp76IPsU8bKnjX0t3ev4j3
Yep, most likely a malicious actor trying to get around inputting a CVC so they can card test.
Nothing wrong with your integration
Ok great, thanks
This cannot happen using stripe checkout normally, right? They are somehow hacking their way to sending the request outside of the checkout, right?
They most likely are just disabling the CVC input requirement when inputting the card details but then the backend submission expects CVC so that results in the error.
Ok great, thanks