#diegus.
sterile fjord
rough pine
Hello! I believe those two test cards are meant to be used to test situations where 3DS would be required for every transaction - while using Setup Intents is the best way to ensure most subsequent transactions will succeed w/o 3DS, it's still possible the bank/card issuer will ask that 3DS be collected again
raven flame
👋🏻 Karbi! I see . Do you know how often bank/card issuer might ask for 3Ds? And also, what should it be the right way to solve it ? I guess that I can read the payment intent status in the webhook but not sure how long 3D auth session will last to allow customer to accept
rough pine
I don't have a sense of how often this happens (it really depends on a lot of different factors like the specific issuer, the type of charge, the amount, etc)
The right way to solve this would be to bring your customer back on-session and call handleNextAction to trigger 3DS for your customer to complete (https://stripe.dev/stripe-ios/stripe/documentation/stripe/stppaymenthandler/handlenextaction(forpayment:with:returnurl:completion:))
raven flame
What I guessed, I’ll figure out the best experience to reduce friction, it’s my main fear.
Last question, do you know if that extra 3D auth requirement can be force by Radar rules? I guess so but I’ve never checked on it
rough pine
You mean is there a way to force 3DS on certain transactions based on Radar rules?
raven flame
And thanks a lot by the way , really appreciate
Yup, I meant that. After reading Qa testing cards description I shared above, I’m wondering if that extra 3d requirement has been forced on Radar software
rough pine
👍
Yup, this is something you can configure in your radar rules (https://dashboard.stripe.com/test/settings/radar/rules) - we offer a set of default rules that you can change, but if you want more complex rules you need radar for fraud teams