#jarens
cerulean mulch
candid plume
Yes that should work. Those payment methods won't require a redirect.
vernal terrace
Gotcha, thanks for the response! My companies' main goal is to enable Apple/Google Pay in our checkout process, which is why we started investigating Payment Element. We're already collecting cards via Stripe's Card Element. My thinking was that adding Stripe's Payment Request Button would be a more direct route considering that adding Apply/Google Pay is our main objective. Do you think that would be a better route to go?
candid plume
I was actually going to mention that button. Could also be a good way to do this. I don't think either is particularly better than the other here, it would be more about what UI makes more sense for your page
vernal terrace
Yep, that's the tricky part. Currently we navigate the customer to a summary page immediately after completing checkout. Our backend then processes the order and charges the Payment Method that was captured asynchronously at a later time. We know that our backend process needs to change - i.e. we need to start using Payment Intents and confirming payments in the client, but other than that, we'd like to make as few changes as possible. Ideally we'd like to validate Apple/Google Pay before investing more engineering time into updating our checkout process.