I was just poking around on a Shopify store on my Firefox browser and saw Apple Pay button showed up, first thought it's a front-end bug on the website but tapped on it and the widget slid up and you can legibly make the purchase!<p>Tried on Chrome too and it worked there too!<p>Tried a few other website and can confirm it works everywhere Apple Pay is offered. is it a feature? bug?<p>Wanna try it yourself? you can check this Stripe test page
<a href="https://stripe.com/docs/stripe-js/elements/payment-request-button?html-or-react=html" rel="nofollow">https://stripe.com/docs/stripe-js/elements/payment-request-b...</a><p>Haven't installed Beta 4 yet to see if it is still working.
Probably preparations due to the upcoming EU framework.<p>As a short summary, here are some of the new EU requirements on gatekeepers such as Apple.<p>Gatekeepers must:<p>- Allow users to install apps from third-party app stores and sideload directly from the internet.<p>- Allow developers to offer third-party payment systems in apps and promote offers outside the gatekeeper's platforms.<p>- Allow developers to integrate their apps and digital services directly with those belonging to a gatekeeper. This includes making messaging, voice-calling, and video-calling services interoperable with third-party services upon request.<p>- Give developers access to any hardware feature, such as "near-field communication technology, secure elements and processors, authentication mechanisms, and the software used to control those technologies."<p>- Ensure that all apps are uninstallable and give users the ability to unsubscribe from core platform services under similar conditions to subscription.<p>- Give users the option to change the default voice assistant to a third-party option.<p>- Share data and metrics with developers and competitors, including marketing and advertising performance data.<p>Gatekeepers may no longer:<p>- Pre-install certain software applications and require users to use any important default software services such as web browsers.<p>- Require app developers to use certain services or frameworks, including browser engines, payment systems, and identity providers, to be listed in app stores.<p>- Give their own products, apps, or services preferential treatment or rank them higher than those of others.<p>- Reuse private data collected during a service for the purposes of another service.<p>- Establish unfair conditions for business users.
Non-Safari browsers on iOS are still Safari's rendering engine, aren't they?<p>I just wish it'd work on Firefox on my Mac. If not that, I'd love a popup that told me the page supports Apple Pay, so I can checkout with Safari instead.
This is not a new API AFAIK. The Payment API[0] has been around for a while. MDN's got the full skinny [1].<p>[0]: <a href="https://webkit.org/blog/8182/introducing-the-payment-request-api-for-apple-pay/" rel="nofollow">https://webkit.org/blog/8182/introducing-the-payment-request...</a><p>[1]: <a href="https://developer.mozilla.org/en-US/docs/Web/API/Payment_Request_API#browser_compatibility" rel="nofollow">https://developer.mozilla.org/en-US/docs/Web/API/Payment_Req...</a>
Apple Pay has been supported in WebKit’s web view (which every browser uses) for a while now, but with some conditions. The biggest obstacle was that an app couldn’t inject any JavaScript code of its own into websites. I wonder if they removed this safeguard.
No it doesn't, because there is no such thing as a non-safari browser on iOS.<p>Firefox, Chrome, anything Apple will allow is just Safari in a different costume.
This is good news, I hope they make it available in all
“In App Browsers” (IABs) too, along with all saved payment cards in your key chain.<p>As a data point from an online retailer, we kept seeing a significantly high (I think it was something ridiculous like 30%) drop out at the check out payment screen for all Facebook/Instagram ad customers.<p>What was happening was they were clicking on ads, coming to our site, going to purchase and then when they reached payment didn’t have access to Apple Pay or there saved card details. The in app browsers have an “open in Safari” button, they were clicking that - so they could use their prefers payment method - and loosing their session and shopping cart. It was catastrophic!<p>We ultimate fixed the issue with a warning message to customers who are within an IAB.<p>IABs are bad for advertisers, they only serve to keep users within the social media app.<p>Anyone with the Beta, I would love to know if either Apple Pay or key chain saved cards are available now in social media IABs.
Do you know if extensions work, too? That was the big thing keeping me off Firefox on iOS, and thus, Firefox on Mac.<p>I want something that syncs to all my devices and supports extensions on all my devices.<p>TBH not allowing safari extensions to work in non-safari browsers felt almost anticompetitive, but I do recognize that there are some UI challenges to solve. Apple Pay was the other big feature I was missing out on.
I hope support for this ends up in Mac browsers. It’s really frustrating to get through a car pieces and realize the site probably supports Apple Pay but you can’t use it because you’re looking at the site outside of Safari