Steve1662 | Stripe Developers | Page 1

fluid girderBOT Dec 15, 2022, 4:48 PM

#

unborn iris Dec 15, 2022, 4:48 PM

#

Hey there, we can't re-open threads. But if you summarize then I'd be happy to help

serene timber Dec 15, 2022, 4:49 PM

#

NP. I switched the environment to use a 'clean' Stripe account and I am still seeing the Apple Pay option when the account does not have an Apple Pay domain registered.

unborn iris Dec 15, 2022, 4:51 PM

#

Are you in incognito/private browsing?

serene timber Dec 15, 2022, 4:51 PM

#

Yes.

unborn iris Dec 15, 2022, 4:51 PM

#

Yeah it will always show up in private browsing

serene timber Dec 15, 2022, 4:51 PM

#

The trytn.dev is still pointing to the 'old'. https://trytn-webapp-booking-scus-staging.azurewebsites.net/smm2022-8-1 points to the new account.

Scheduled Events

English blah blah

unborn iris Dec 15, 2022, 4:52 PM

#

But you won't be able to use it if it isn't registered correctly

#

It will just error

serene timber Dec 15, 2022, 4:52 PM

#

Understand that it will error. Pasting this from the last thread....* Understood that is what I need to do to make it work for that account. But the problem that I have is that I would not expect the Apple Pay button to display for any tenant within our system that has not setup their Apple Pay domain via our system. The account we've been using is now in that category.... aka no Apple Pay domain setup. The question I have is should that Apple Pay option be showing if they do not have a registered domain.*

unborn iris Dec 15, 2022, 4:56 PM

#

Yep it is expected to always show if you are in private browsing

serene timber Dec 15, 2022, 4:56 PM

#

The 'new' account #; acct_1BVRRYFoh8sygNvJ

unborn iris Dec 15, 2022, 4:56 PM

#

This is a nuance of how Apple presents Apple Pay with canMakePayment

serene timber Dec 15, 2022, 4:58 PM

#

So if a Connect account has not setup an Apple Pay Domain and the end user happens to be using a private browser the Stripe code shows a button that will never work?

unborn iris Dec 15, 2022, 5:03 PM

#

If you have PaymentRequestButton mounting on that page then yes

serene timber Dec 15, 2022, 5:03 PM

#

Alternatively I guess we would have to do the lookup to see if they have a registered domain and then set the wallets: {applePay: 'never'} when we create the payment element.

#

We're using elements.create('payment', I believe that is different then the payment request buttons but could be wrong.

#

Confirmed we are not using the paymentRequetButton approach. That would require elements.create('paymentRequestButton',

unborn iris Dec 15, 2022, 5:08 PM

#

Ah yeah that's true it is different but same behavior here for Apple Pay

#

So yes, if you are concerned about the private browsing experience then I do think setting applePay: 'never' is the correct workaround

serene timber Dec 15, 2022, 5:11 PM

#

Got it. The 'nuance' seems more like a bug but understand there is complexity.

unborn iris Dec 15, 2022, 5:11 PM

#

Yeah I call it "nuance" since it is on Apple's side of things here 🙂

#

But fair feedback

serene timber Dec 15, 2022, 5:12 PM

#

We'll head back to the drawing board and see what we're going to do to handle it. Thanks for your help! Cheers!

#Steve1662