#dan_kres
1 messages · Page 1 of 1 (latest)
Well you can't pass parameters to determine whether or not 3DS is required. Ultimately the bank/issuer determines that
What you can do is optimise your payments to reduce the chances of 3DS being requested
Can you describe more about the payments you're initiating? Is the customer off-session (MIT)?
Not exactly, the customer is present on the website, but the aim is not to call the 3ds so that the payment passes in truly one click, without authorization.
Definitely the 3ds to be called whenever issuer asks to, or this payment requires SCA
but the aim is not to call the 3ds so that the payment passes in truly one click, without authorization.
Yeah, you can't guarantee that. As I said, you can optimise payments to reduce the likelihood of 3DS being requested which is ultimately determined by how you saved/setup the card.
If you want to force 3DS then yes you can pass request_three_d_secure: 'any'
Otherwise with automatic we will defer to the bank as to whether they require authentication
And regarding off_session field - what has to be passed to reduce the chances of 3DS being requested
You'd only use that field if your customer's were not present in the payment flow (i.e. off-session)
Any additional specific fields which can trigger 3ds?
as in, you want to force it in test mode so you can see/test it?