lafafm-3DS-wallets | Stripe Developers | Page 1

hardy stratus Nov 19, 2021, 1:27 PM

#

Hey there 👋 great question, please bear with me while I look into that.

#

I know when you're testing Apple or Google pay that we reroute those to a valid test card behind the scenes, I need to double check whether you might encounter a 3DS challenge though.

woeful yoke Nov 19, 2021, 1:37 PM

#

I'm also interesting what's the right place of triggering confirmCardSetup (we are using SetupIntent mechanic here)

E.g. GPay card setup looks in a such way

Mount payment request button
There's a listener paymentRequest.on('paymentmethod' , which handles submit of PaymentRequestButton
Inside that listener we should trigger a event.complete

So I'm not sure when should we call a .confirmCardSetup

After GPay card is retrieved and we already call event.complete('success')
Or before event.complete('success') and in case of unsuccessful 3ds check call event.complete('fail')

hardy stratus Nov 19, 2021, 1:55 PM

#

Thank you for your patience, so you should be prepared to handle 3DS in case a wallet payment method requires it. If you look at our sample code snippet, linked below (step 5), you'll see that we call confirmCardPayment twice. This is to handle 3DS should it be necessary. Since you're using a setup intent you'd replace those functions with confirmCardSetup.
https://site-admin.stripe.com/docs/stripe-js/elements/payment-request-button?html-or-react=html#html-js-complete-payment

woeful yoke Nov 19, 2021, 2:08 PM

#

Ok, thank you

Made it as that page says, working fine

#

But one question is still actual
Any way to reproduce 3ds at least for Google Pay?

#

Or just by updating Radar rules to require 3ds for all supported cards ?

#

In theory, as I remember GPay / Apple pay converts all the card to 4242, which have 3ds supported

hardy stratus Nov 19, 2021, 2:18 PM

#

So I've found that for Apple Pay, the 3DS flow is all handled outside of our control. Still double checking regarding GPay though.

sharp quartz Nov 19, 2021, 3:59 PM

#

Hey sorry for the delay here, the latest info I could find is that this is managed by google for the cards saved in google pay. This extra confirmation flow covers the "browser saved" card in eg Chrome, which is not already authenticated.

#lafafm-3DS-wallets