#deepanshu4186_error
mild tinselBOT
👋 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/1336268991085150269
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
cerulean pendant
👋 happy to help
glass shoal
Hello Stripe team,
While testing failure use cases via Stripe using the test card below, we are observing inconsistent payment statuses—sometimes receiving requires_action and other times failed.
We are setting payment_method_options[card][request_three_d_secure] to automatic because we intend to test only non-3DS flows. Could you help us understand why this inconsistency occurs? Is there a way to enforce non-3DS payments on Stripe?
Account id: acct_1M7fTaD5R7gDAGff
Failed Card:
Stripe Transaction ID: pi_3QoMdED5R7gDAGff01QLrqgG
{
"card_number": "4000000000009995",
"card_exp_month": "12",
"card_exp_year": "34"
}
Additionally, while using the CVV check fail test card below, we occasionally receive a requires_action response even when attempting a non-3DS transaction.
CVV Check Fail Card:
Stripe Transaction ID: pi_3QoMdTD5R7gDAGff0rbklp6x
{
"card_number": "4000000000000101",
"card_exp_month": "12",
"card_exp_year": "34"
}
Could you please clarify why this is happening?