#edgarsantiago93
brisk ledge
rugged cove
Express Checkout should be able to finalise the payments at server side with creating payment method at the client first: https://stripe.com/docs/elements/express-checkout-element/accept-a-payment#create-pm
brave flower
awesome, i missed that document, thank you so much!
rugged cove
No problem! Happy to help 😄
brave flower
follow up question, is there a way to test 3ds with apple/google wallets?
rugged cove
Apple Pay and Google Pay has its own authentication like FaceID or fingerprint
It doesn't go through 3DS provided by card issuer
brave flower
i see, so what happens when i as a user, add a card that has 3ds enabled to google pay?
rugged cove
If the issuer requires 3DS, then Stripe SDK will handle the authentication
In test mode, such flow can't be tested
brave flower
thanks, i am using the stripe.handleNextAction method that receives the client secret if theres a "requires_action" status, to handle 3ds with then payment element , can i assume that this will handle 3ds with wallets if needed?
rugged cove
If you use Payment Element integration with stripe.confirmPayment(), you shouldn't need to integrate stripe.handleNextAction()
brave flower
im using this fro the payment element
https://stripe.com/docs/payments/finalize-payments-on-the-server?platform=web&type=subscription
the flow is basically the same as the one you provided, im handling creating the pm, creating the subscription, and confirming the payment as separate events, it says that i should use handlenextaction if the status is requires_action
rugged cove
Oh yes! You're right! I missed the fact that you're using finalised payments on the server
Sorry, my bad
When the status is in requires_action, stripe.handleNextAction() should be used to handle 3DS
brave flower
awesome, that simplifies everything a lot haha, thanks!