#Alexander_
gaunt schooner
analog robin
Hello 👋
Have not seen this come up that frequently 🤔
Let me take a look
lofty canyon
here is a screenshot, it's a SetupIntent from a Google Pay button created by elements.create('paymentRequestButton', ..., I can provide more details if needed.
analog robin
My understanding is that Google Pay payments shouldn't be triggering 3DS auth checks but could be wrong.
looking..
lofty canyon
it happens with live keys for my real card
analog robin
Sometimes it depends on how the card is added to Google Wallet, How exactly did you share the card to your wallet?
lofty canyon
it's a card I added a while ago, don't really remember how exactly. What does it depend on exactly?
real yacht
👋 stepping in
So with Google Pay there are times that 3DS can and will be requested
It most often depends on how the card was actually saved. For instance, if you save a card to your Chrome browser as opposed to your Google Wallet, then there isn't the same level of security present and thus the typical 3DS exemption won't always apply
Beyond that, it is always possible for an issuer to force 3DS if the so desire, regardless of the exemption
They can do this for fraud reasons or other measures
Though that is pretty unusual
Overall, we do talk about how to handle 3DS in our docs for Google Pay: https://stripe.com/docs/stripe-js/elements/payment-request-button?client=html#html-js-complete-payment
Do you have that implemented?
Specifically, do you have handleActions=false set?
lofty canyon
I don't have the if (paymentIntent.status === "requires_action") part indeed. And I don't pass any value for handleActions.
Let me read and try it out and get back to you.
real yacht
Gotcha. Yeah add those pieces in and let us know if that doesn't clear it up!
lofty canyon
by the way I'm using confirmCardSetup instead of confirmCardPayment since it's a SetupIntent. Mentioning in case the above is not relevant.
real yacht
Should work the same
confirmCardSetup also supports handleActions (https://stripe.com/docs/js/setup_intents/confirm_card_setup#stripe_confirm_card_setup-options-handleActions)
lofty canyon
Just passing handleActions: false made it succeed without asking for 3DS at all.
(which is good on one hand but at the same time I don't how to test my 3DS integration)
real yacht
Hmmm yeah I mean you aren't really supposed to be testing in prod any way as it is against our ToS (see: https://stripe.com/docs/testing#use-test-cards)
Overall, as long as your integration is set up like we show above in terms of handleActions: false and then confirming again if it moves to requires_action then you are good to go
lofty canyon
I'm testing with a real card in live mode
real yacht
Right, you aren't supposed to do that 🙂
Since we aren't supposed to send fake authorizations to card networks
But yeah, I'd recommend mocking a response where your PI moves to requires_action and then ensuring your code handles that via calling confirm with Stripe.JS
As long as that happens, you are good to go
lofty canyon
Right, you aren't supposed to do that
I see, doing it as I didn't find a way to test Google Pay 3DS handling in test mode
real yacht
Yeah I understand
I'm just noting it mostly
I know there are some gaps in what you can test in test mode
We mostly recommend mocking in these cases
But I know where you are coming from.
lofty canyon
👍 thanks to both of you, feel free to close the thread. Really appreciate the quick and on-point help in this channel 🙇♂️ keep rocking!
real yacht
Happy to help!