lozzy. | Stripe Developers | Page 1

spark walrusBOT Jul 31, 2023, 1:06 PM

#

burnt drum Jul 31, 2023, 1:08 PM

#

The bank ultimately decides whether 3DS is requested. So for automatic the choice is entirely up to the bank. If you set it to any, Stripe specifically asks the bank to request 3DS which makes the bank much more likely to ask for it (though banks can decide to not even if you ask)

fading barn Jul 31, 2023, 1:13 PM

#

I understand that with card payments setting the value to 'any' will trigger 3DS if the card is enabled for 3DS (At least for testing). However, when I test GooglePay and use the token given from Google. It seems to always trigger 3DS. I was told earlier that 3DS for Google/Apple Pay rarely happens but that's not been the case.

I assume you recommend setting the value to 'automatic'?

burnt drum Jul 31, 2023, 1:21 PM

#

Both settings are valid, so automatic is probably the reccommended one unless you have a specific reason to choose any

fading barn Jul 31, 2023, 1:27 PM

#

Despite using Google test cards, 3DS will always be triggered since request_three_d_secure is set to 'any'? In a live environment this will only work if the card used for Google pay supports 3DS. Is this correct?

burnt drum Jul 31, 2023, 1:30 PM

#

Yes, 3DS is a bank thing. So if the bank doesn't support 3DS, there is nothing to be requested and no page for the user to go through. Stripe and Google just direct you to the bank's site, they don't have their own 3DS pages

fading barn Jul 31, 2023, 1:34 PM

#

If request_three_d_secure is set to automatic, how can we test 3DS with Google Pay? Of course you have your own test cards that can trigger 3DS. But in this instance we are using Google test cards.

Will I have to toggle between 'any' and 'automatic' in order to test 3DS with Google/Apple Pay?

burnt drum Jul 31, 2023, 1:38 PM

#

I actually think Google Pay may do its own 3DS handling. Will check in to that and get back to you

#lozzy.