#zach_61657

1 messages · Page 1 of 1 (latest)

devout vergeBOT
lethal pine
#

Well, browser in this case since you mentioned they're on an iPhone. Are you able to reproduce this at all? Do you know if they can see the ApplePay button on other web stores?

#

I assume they also already have a card set up in ApplePay?

inner field
#

Unfortunately I don't have an Apple device to test with so I haven't been able to reproduce.

That is a good question on other stores which I have asked them and am waiting on an answer.

On card, I believe so, since they mention they've set it up. However, I am not 100%.

One other note, on the demo in the Stripe docs, they can see the Apple Pay button, but I think that always shows since it is in test mode?

#

As well, I have confirmed a couple of recent payments have come through via Apple Pay - so it is working for some folks.

So I think mainly the scope of this is if there's anything other than Device / Browser / Card Available that could affect visibility?

lethal pine
#

Ah, I see. In the Express Checkout Elements docs, the ApplePay button will show up even if a card hasn't been added to your wallet. If it's working for some folks, it looks like it's specific to this user

inner field
#

Thanks and good note, the domain is verified.

So I think you're right that it's this user, I was concerned since the docs mention the element tries to optimize for conversions that it could override our request, but it sounds like it must just be a compatibility / setup issue.

Just to clarify, is this the default behavior of Apple Pay in general? That is, will all implementers of Apple Pay have this behavior? I assume so, but just want to clarify for my client.

lethal pine
#

What behavior exactly?

inner field
#

Basically just only showing the button if valid payment is available. Now that I'm thinking about, it's kind of a silly question, but it would help to know if it's an Apple design decision / API thing, or Stripe-specific.

lethal pine
#

Got it. Yep, this is expected behavior based on the browser and device used. Like, if I'm on an Android device, it makes sense that ApplePay would never be displayed

inner field
#

Of course, that makes sense, and on an iOS device in Safari, if Apple Pay is not setup, it's not possible to display an Apple Pay button that would first prompt someone to set it up?

This doesn't make much sense of course from a user experience perspective, but I think Google Pay does allow it anyway.

lethal pine
#

So the Express Checkout Element, when used in Safari, will prompt a customer to set up ApplePay if they haven't already. The older PaymentRequestButton will not show the ApplePay button if the customer has yet to set up a card in their wallet

inner field
#

I see, we're using the newer button. So I have to assume that something is just incorrect about this users device or browser then. Thanks for helping me understand the behavior of this element!