alex-googlepay-testing | Stripe Developers | Page 1

tawdry tokenBOT Jan 31, 2023, 4:55 PM

#

uneven silo Jan 31, 2023, 4:56 PM

#

@tulip radish mostly you can't. Google Pay in Test mode will always use the 4242 card and nothing else. So you'd skip Google Pay to test other flows

#

alex-googlepay-testing

tulip radish Jan 31, 2023, 4:59 PM

#

I see. What about Apple Pay, is there a recommended way to test edge cases?

uneven silo Jan 31, 2023, 4:59 PM

#

Same way for Apple Pay

#

Like if you want to simulate a failure on a future payment, the fact that it's Apple Pay or Google Pay doesn't matter, it's the same as a normal card: it fails, you get them them back on session to pay

tulip radish Jan 31, 2023, 5:01 PM

#

got it. Is there any workaround to test 3DS during the GP/AP setup?

uneven silo Jan 31, 2023, 5:08 PM

#

Apple Pay would never trigger 3DS so no. Google Pay could but we don't have a test card for it

tulip radish Jan 31, 2023, 5:24 PM

#

Thanks. Last question, we're passing the SetupIntent id to stripe.confirmCardSetup(...) along with the payment method. It also accepts handleActions: true/false. Which one would you recommend, how do we know the difference?

If the payment method is not from a Google/Apple Pay but from an Element card form, for example, would that be a proper way to test the handling of next actions? (since we can't force GP/AP to trigger next actions in test mode)

uneven silo Jan 31, 2023, 5:26 PM

#

if it were me I would just never pass handleActions and let the Element do the right thing

tulip radish Jan 31, 2023, 5:32 PM

#

I see, asking since this example https://stripe.com/docs/stripe-js/elements/payment-request-button?client=html#html-js-complete-payment passes false and if it requires action calls confirmCardPayment a second time. But this example is for an on-session payment, we just want to setup the GP/AP to be charged later (so maybe quite a different use case).

#

thanks for your help 🙇‍♂️

#alex-googlepay-testing