#mkoenke
wild acorn
quiet pulsar
Yup! This flow should still work with apple + google pay
pine flint
woohoo thats great news, thank you for the confirmation. The problem with this flow is when you try to integrate a payment method with a redirect right?
quiet pulsar
No as far as I know it should still work with a redirect as well - are you seeing issues with it?
The redirect would be happening with confirmation (the final step) not when the PaymentMethod is created
pine flint
we havent implemented all of it yet, trying to decide the best way to do it. When I say payment method, I meant something like Klarna or one of those options, not the actual stripe PaymentMethod .... trying to figure out how we would work the redirect in if someone is able to update the amount or currency after the PaymentElement is rendered. We currently allow the user to select the product/add promos/ etc. after we render the card element that we are currently using. And then on the backend, we create the payment intent after we collect the card information. We actually send the PaymentMethod at the same time as we create the PaymentIntent, and the charge is processed so we never have to do the confirm step on the frontend.
If we use the deferred payment intent flow, and finalize payments on the server, the way we are doing it now, I am wondering what options that prevents us from using. Or if we do deferred payment intents and then confirm on the frontend, what options that might open up for us.
The priority is definitely apple pay and google pay.... but would be nice to leave other options open too
quiet pulsar
Okay backing up uhere for a second - you can create a stripe PaymentMethod where the type is Klarna (which is what I meant when I was referring to a payment method that needs a redirect)
pine flint
oooo I was missing that part for sure...
quiet pulsar
if you ONLY finalize payments on the server and never come back to the client that does severely limit the types of payment methods types you can use because there are a lot of types that would need the customer to be on-session to handle next actions (see https://stripe.com/docs/payments/finalize-payments-on-the-server?platform=web&type=payment#next-actions). Even cards have the potential for needing next actions to handle 3DS
So yes, you can finalize payments on the server, but it would still be recommend that you at least implement stripe.handleNextAction to make sure you handle any other actions to complete the payment
pine flint
right, so thats our only exception, we do handle 3DS cards
gotcha, so we can use the handleNextAction after finalizing payments on the server, to complete the actions necessary to use klarna or a payment method with a redirect?
quiet pulsar
yup!
pine flint
you all are awesome, you have no idea how much I appreciate this discord lol
quiet pulsar
❤️
pine flint
thanks so much