The Apple Pay button will only show up to customers who have Apple Pay onboarded and enabled. Customers who don't care about Apple Pay won't ever see the button.

(I work on Checkout)

> customers who have Apple Pay onboarded and enabled

How is this handled on web forms? I have neither of those but it shows up on the preview.

I don't care, I think it's fine ala login via Google/FB links on login forms being on top. I'm just curious!

The preview is using a test key, so it's likely they show everything just for testing reasons.

Oh they mean connected on the users Stripe account or the companies? I thought OP meant some iOS API to see if they have Apple wallet set up with an active card.

I'm guessing there will still be a link if the company supports it if it's the former (first party user level).

Can you say a word or two about why the new Checkout experience is a full-page redirect instead of a modal dialog? (I preferred the dialog.)

I wrote some notes below (https://news.ycombinator.com/item?id=19740475) but TL;DR is that this lets us support a lot of features that that the legacy version never could. If you’re looking for an embedded form, Elements work great (https://stripe.com/docs/stripe-js/elements/quickstart) — you can of course pair Elements with a lightbox/modal library to get a similar experience to the legacy version of Checkout.

So we can build a modal version with Elements that supports all features?

But Stripe removed the modal option from Checkout because features?

A modal with Elements could support all the features that old modal Checkout supports. It would not be able to do all the things that new non-modal Checkout will be able to do in the near future.

You mean SCA-3DS or?

The Stripe 3DS and SCA page says a modal in combination with Elements is fully supported:

Pre-built modal: The Payment Intents API integrates tightly with Stripe.js and Elements to simplify the authentication process. If your Stripe integration uses handleCardPayment or handleCardAction, Stripe.js automatically handles the authentication process—displaying a modal dialog where the customer can provide the requisite information.

This makes it look like we can build a modal version via Elements which fully supports SCA and 3DS through another modal. All on one page.

Also, the Paymentintent docs say we have to set the viewport to mobile on our page so that the UI of Elements can handle 3DS, this makes it also look like it works on our page through a model without redirects. Otherwise Stripe would set the viewport.

Does Elements fully support 3DS and SCA all on our page through modals or not?

In the future will the "Apple Pay" in this instance also be replaced by PayPal, Google Pay, etc, depending on what the person uses?

In Elements the payment request button utilises the PaymentRequest API, so Apple Pay in Safari, a (default) purple browser button in Chrome, etc. So I imagine so.

Google Pay coming soon!

Others have already mentioned that it only shows up for compatible devices, but why would you want it to show below the payment form? That means a user would start filling in the form before realizing there's an alternate payment method. That seems like bad UX to me.

The only thing that's jarring to me is how the button takes the full width of the screen. This is just me nitpicking though, the design otherwise looks great!

Depends on whether your customers are buying on desktop or mobile. It is a big advantage for mobile conversions to support payment solutions like Apple and Google pay.

https://www.commerce7.com/blog/how-digital-wallets-increase-...

My anecdata is from this past weekend when I had a choice of ordering from two different pizza apps. I went with the one that offers Apple Pay because the checkout process is so frictionless.

When it comes to buying things online, for me I prefer Apple Pay > Stored credit card number (Amazon) > Punching in a credit card number > PayPal. For me, this is 90% about trust.

Again, just one data point, but it's the only one I have.

on term of UX i would go Paypal > Punching in a credit card number.

Punching a cc is the worst horror UX ever in the history of life

I'll personally support this claim, on my iPhone Apple Pay is so seamless (finger over home button and done) that I'll consciously want to purchase it more.

Similar story for one-click solutions such as paypal and amazon. If I don't have to get my card out then I'm far more likely to make a purchase.

> Finger over home button One of the best use cases for touch id. Apple pay with FaceID is so much more of a pain in the rear. I have to double click the power button, position the phone so it can see my face, then put it back over the reader. Not at all seamless.

I also highly doubt that the Apple Pay button shows up on places where it isn't supported.

The Apple Pay button is a browser feature and unless you mimic it using CSS, it will only show up if you're in a supported region with a supported device that has apple pay enabled and cards added.

Not sure I agree with that. I assume Apple Pay button will only show for customers who have Apple Pay setup/available to use, and for those customers using Apple Pay (1 click secure payment vs manually entering in card info would seem a no brainer).

If you're on a mac or a phone and not using apple pay, you're just a glutton for punishment.

(Presumably the apple pay button doesn't show up if you're not on one of those.)

That's a commonly used design though. Putting integrations above the standard form itself. Many forms do this with Paypal integration instead of Apple Pay.

Any time Apple Pay is available, I use it.

As a user, I wouldn't want it to be hidden far below the other fields since I might not notice the button and start to fill out the fields unnecessarily.

OH! Stripe is the company that keeps bothering me about Apple Pay?

I've been getting this WordPress "error" about not having Apple Pay working.

I would never use an Apple product so I was wondering how I got that on my WordPress install.

Now I'm curious if Stripe had better competitors?

That doesn’t sound right... what does Stripe have to do with Wordpress? And if Apple Pay is not configured, it’s not going to throw an error, it just won’t show the button.

Yes, this is the condition I'm experiencing.