#guillaume_seyna
fickle relic
Right now there's no way to 100% guarantee that you'll never need to do 3DS again on a future payment - while using Checkout in setup mode we see if 3ds is required and create an excemption for future payments, but the bank/card issuer can always choose to reject that exemption and STILL request 3DS
The only way to build a robust integration for this is to bring your customer back on-session if 3DS is required
vagrant viper
Thank you very much for your input !!
you mention the checkout, is it more robust if we use API calls directly instead of the checkout session ?
also how do other big platforms do it ? is the age of the account + volume some kind of parameter that gives big platform an advantage in 3DS triggering ?
fickle relic
Using a setup mode checkotu session vs the API directly shouldn't really have a difference in terms of triggering 3DS
and the account + volume shouldn't have an affect on this either
vagrant viper
thanks again. that's puzzling. we're digging a bit further and there's one of our connected accounts that triggers 3DS for almost 50% of the payments... 🤔
fickle relic
Does your flow involve cloning payment methods to your connected accounts?
while age of account wouldn't affect 3ds (at least not to my knowledge) - location of account certainly would
tribal timberBOT