Avery246813579 - Payment Element Wallets | Stripe Developers | Page 1

tawny sluice Dec 2, 2021, 12:56 AM

#

Hello! Apple Pay will only work in Safari and requires you to validate your domain. Google Pay only works with Google Pay cards in Chrome (not cards saved locally to Chrome).

#

Which one do you want to focus on first, Apple Pay or Google Pay?

pliant ledge Dec 2, 2021, 12:58 AM

#

Google Pay

#

Do you have to verify the localhost domain

#

Seems like kinda a pain for testing

tawny sluice Dec 2, 2021, 12:58 AM

#

No, Google Pay does not require domain validation, but Google Pay requires a secure (HTTPS) connection to work.

pliant ledge Dec 2, 2021, 12:59 AM

#

So nothing will show basically until I am on production or use ngrok

tawny sluice Dec 2, 2021, 1:01 AM

#

Yep, that's correct.

pliant ledge Dec 2, 2021, 1:01 AM

#

Alright so I can just assume it works if the element itself works and I have Apple and Google pay working without this new PaymentElement

#

Also when do the PaymentElement need a redirect?

tawny sluice Dec 2, 2021, 1:04 AM

#

Yep, if Apple Pay and Google Pay work with the Payment Request Button they should work with the Payment Element as well.

#

The Payment Element will always redirect by default.

#

We recommend you do not override the redirect behavior, but you can set redirect to if_required to only redirect sometimes: https://stripe.com/docs/js/payment_intents/confirm_payment#confirm_payment_intent-options-redirect

However, doing so results in a more complex integration and an inconsistent experience for your customers.

pliant ledge Dec 2, 2021, 1:08 AM

#

What method would you ever need redirect for?

tawny sluice Dec 2, 2021, 1:09 AM

#

Right now there are a lot of them, like the bank transfer methods and whatnot.

pliant ledge Dec 2, 2021, 1:10 AM

#

But if I only have card and google pay enabled are there any redirects

#

currently we use the paymentIntent on the client side after the confirmPayment

tawny sluice Dec 2, 2021, 1:10 AM

#

Currently no, but a redirect may be required in the future. You should build your Payment Element integration assuming a redirect may be required at any time.

#

And if you want to add support for things like AfterPay, Klarna, etc. it will be a lot easier if you build with redirects from the beginning.

#

The methods of payment the Payment Elements supports are in this table: https://stripe.com/docs/payments/payment-methods/integration-options#payment-method-product-support

pliant ledge Dec 2, 2021, 1:16 AM

#

Yeah I wanna support PaymentElement but using a redirect is very complicated in our current system

tawny sluice Dec 2, 2021, 1:19 AM

#

As more and more payments go async redirects will become more and more common. Even now some less-than-ideal 3D Secure implementations require a redirect even when they shouldn't.

pliant ledge Dec 2, 2021, 1:20 AM

#

Yeah we can plan for the future and just currently use it now?

#

Since it would basically change our whole payment system

#

and we only use the basic options for the time forward

tawny sluice Dec 2, 2021, 1:20 AM

#

You can as long as you're okay with missing out on payments that do require a redirect. If you're sticking to just cards that should be only a few edge cases.

#

But, again, not recommended.

pliant ledge Dec 2, 2021, 1:22 AM

#

Awesome

#

I will be stupid and will take responsibility in the interim

#

Thanks for the help!

tawny sluice Dec 2, 2021, 1:22 AM

#

No problem!

pliant ledge Dec 2, 2021, 1:43 AM

#

Alright another quick question. Is there a way to validate the payment element to see if the card fields are filled out?

#Avery246813579 - Payment Element Wallets