#virtualrealist_api
hushed gustBOT
👋 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/1228205104470032426
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
quasi berryBOT
limpid minnow
hello! taking a look 👀
it looks like the issuer rejected the 3DS request without requesting for a challenge i.e. showing the pop up modal for the customer to authenticate. If the customer wants to know why the issuer rejected the 3DS request, they'll need to reach out to their issuing bank
frozen quest
I don't really know but it just seems like stripe's way of handling payment is overcomplicated,this card is actually my card and i'm testing my payment system in production after everything was working while i was testing in development.
I used test cards to simulate when a card requires 3DS and when it doesn't. Now the issue is in production stripe still tries to force all cards to carry out 3DS cause my card isn't 3ds secure,i was expecting my paymentIntent to go straight to succeed but instead it always says required-action,this is very very confusing.
so i'm guessing this is why my card issuer is rejecting it,but stripe not detecting it's a card that doesn't require 3ds in the first place complicates things cause i run stripe.confirmCardPayment() every time a user puts in the card details and check if the paymentIntent needs any required_action