#allthepratts-ECEvsPE

1 messages · Page 1 of 1 (latest)

tawny locustBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

drifting path
#

Usually people do this when they want the express options (Apple Pay, Google Pay, etc.) to appear as distinct buttons above the Payment Element instead of options inside the Payment Element.

covert burrow
#

That's exactly what I was looking for, thanks! Can you provide some clarity into this statement from the docs:

It’s preferred to collect payment details before creating an Intent when using the Express Checkout Element. If you previously integrated with the Payment Element, you might need to update your integration.
It doesn't sound like it's required to make that update in order to use Express Checkout? What is the benefit of making that update? If I did decide to use both the Payment and Express Checkout Elements, would I have to include both integration methods (PaymentIntent before payment details and PaymentIntent after payment details)?

drifting path
#

You're correct, that update isn't required. We recommend it because it makes the overall flow and integration simpler, but you can ultimately do whatever works best for you.

#

For the Express Checkout Element + the Payment Element where you create a Payment Intent first I do think you would need to implement both flows, yeah.

covert burrow
#

Thanks! Appreciate the quick and knowledgeable responses.

drifting path
#

Happy to help!

tawny locustBOT