#cristiancalara_docs
prime bronzeBOT
đ 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/1300809687943348256
đ 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.
- cristiancalara_best-practices, 2 hours ago, 15 messages
nova imp
Briefly, no, that's not possible. First because if off session transactions may be subject to 3ds later, then the setup intent authorization will typically already require it. Second because you don't actually know if that later payment will require 3ds. The bank gets to decide and it can depend on the details of the payment, or even other payments the customer has done in the interim.
What is your end goal?
You can optionally include a request for 3ds with your setup intent using
payment_method_options[card][request_three_d_secure]=any
https://docs.stripe.com/api/setup_intents/create#create_setup_intent-payment_method_options-card-request_three_d_secure
But its important to understand this is a request to the customer bank, they are not obligated to ask for 3ds
plush wind
Basically I had a case where what you mention did not happen. So 3ds was not requested when we saved the card and then it was required for the next payment in 10m.
It was mainly to see if I can do that until we actually implement the process to handle the 3ds for off session payments - so like a temp solution.
But yeah what you mentioned makes sense - we'll just try to add this handling of 3ds for off session payments as soon as possible on our end
nova imp
Sure thing -- if you want to push as much 3ds during setup as possible while the customer is alreayd present, then using that optional any param will increase that rate
But again its important to internalize that requiring 3ds is always up to the bank, so even doing 3ds during setup is no guarantee of not needing 3ds again later for payment. You always need to be ready to handle getting the customer on session to complete 3ds or provide alternate payment info.
If you have a payment happening soon, consider whether you flow can do the payment on session first with setup_future_usage=off_session to save the card for later payments too
The risk of setup + payment intents in close succession is unpleasant double 3ds for the customer. It should, ideally, be rare, but it can happen.