#wafflcoptr
1 messages · Page 1 of 1 (latest)
Hi there, this is the expected behaviour since there's no wway to check the Apple Pay readiness in private mode.
So what would happen on a non-verified domain if a customer selects the Apple Pay option? We noticed when we try this it seems to hang but it might be us not handling an error case.
Wait a second, you said non-verified domain? Sorry I misunderstood you.
It shouldn't happen, do you have a website that I can take a look on?
Can I DM you a link?
Sure
I sent you a DM
OK. Sorry for the back-and-forth, but this is the expected behaviour.
In private browsing mode, the browser always shows the Apple Pay button even if the device isn’t set up for it.
And the Stripe processing will error without showing anytype of error to the user?
You are getting this error because you've registered your domain with Apple Pay.
Do you mean its because the .well-known/apple-developer-merchantid-domain-association file is available on that domain?
We have not verified this domain in Stripe
Not only that, you also need to register the domain. https://stripe.com/docs/stripe-js/elements/payment-request-button?client=html#verifying-your-domain-with-apple-pay
Yes but we are trying to see if we don't need to verify the domains we don't need Apple Pay for the moment. Our use case involves a single web server serving different marketplaces. eg. stripe.oztix.com.au, tesla.oztix.com.au. If we only want stripe.oztix.com.au to show apple pay we can we use the verified domains list achieve this behaviour? It seems to work like this unless you are in incognito mode.
Yes you are right. Even the Apple Pay button is displayed in incognito mode, the payment won't succeed if you don't register the domain for Apple Pay.