#tea-hanks_best-practices
kind lightBOT
đ 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/1438487958448767166
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
willow hare
To add more context since I accidentally press submit
We collect the payment details using setup intent and setting the usage to off_session. This works perfectly for all cards except the one mentioned above. In this case the user is asked for 3D secure authentication while setting up but also requires them to authenticate it when being charged later
I realise that there seems to be no out of the box solution here except for listening for webhooks and emailing user a link to the payment page where they can authorize this payment. I wanted to ask if there are any other ways to deal with this situation?
fossil cloud
hey there! can you share the ID (pi_xxxx) for a payment this happened with?
kind lightBOT
proper grove
hi! I'm taking over this thread. can you share the PaymentIntent ID as mentioned above?
willow hare
Sure. Here you go pi_3SSeq4Fd6EDIZfQW10ek1m4l
I edited the payment intent id because I was testing and manually captured charge on the last id that I shared
proper grove
having a look
here's what our doc says for the card you used:
This card requires authentication on all transactions, regardless of how the card is set up.
https://docs.stripe.com/testing#authentication-and-setup
so as expected, it always require 3DS.