Rethinking Payment Request for iOS Chrome
The Payment Request API is a web standard to make it easier for web developers to build low-friction and secure payment flows. The browser facilitates the flow between a merchant website and “payment handlers”. A payment handler can be built-in to the browser, a native app installed on the user’s mobile device, or a Progressive Web App. Today, developers can use the Payment Request API to access several payment methods, including “basic-card” in Chrome on all platforms, Google Pay in Chrome on Android, and Apple Pay in Safari. The Chrome team continues to work with other browser vendors and digital wallet developers to make more payment handlers available with this new standard.
Shipping the Payment Request API over the last two years helped us better understand the challenges in building payment flows on the web. We learned that UX is critical for building user trust with a payment app, and new technology such as tokenization has made great strides in protecting users from online fraud by never exposing a user’s credit card number to a website. Unfortunately, Chrome’s built-in payment handler for “basic-card” falls short on both regards. As we considered solutions, we realized that the best way to enable more seamless and secure payments on the web is to enable an interoperable ecosystem, where digital wallets can bring their best experience to the web. This means shifting focus to the Payment Handler API, which is an emerging W3C standard that allows 3rd party payment handlers, which can be either native mobile apps or progressive web apps, to integrate with the browser to handle Payment Requests. This enables users to complete one-click payments anywhere on the web using their wallet of choice.
This shift in focus means that we will eventually sunset Chrome’s built-in “basic-card” payment handler. We will start by removing “basic-card” support from iOS Chrome, where this feature has the least usage. This change is coming in M81. In its place, we are investigating how to enable native apps on iOS to integrate with Payment Request API in Chrome. The “basic-card” payment method remains a W3C standard and developers can build compatible payment handlers using the Payment Handler API by setting method to “basic-card” when registering a payment handler with the browser.
This M81 change will deactivate Payment Request API on iOS Chrome because “basic-card” is the only supported payment method and because payment handlers are unavailable due to the lack of Payment Handler API support in WKWebView. If you’re a developer that uses Payment Request API, please make sure you use feature detection and provide a suitable fallback to ensure iOS users continue to have a working alternative. This is also needed to ensure your website works as expected in browsers that don’t yet support Payment Request API.
If you are a payment app developer, please check out our tutorials on how to integrate as a native payment handler on Android and how to integrate as a web-based payment handler via the Payment Handler API.
If you have feedback on Chrome’s web payments implementations, you can reach us at firstname.lastname@example.org. If you have feedback on the web payment API specifications, find us at the W3C Web Payments Working Group.
Posted by Danyao Wang, Web Payments EngineerRead More
Related Google News:
- Simplify your Chrome OS migration with Parallels Desktop April 27, 2021
- Colgate-Palmolive moves to the cloud with Chrome Enterprise and Google Workspace April 26, 2021
- Chrome 91: Handwriting Recognition, WebXR Plane Detection and More April 22, 2021
- Contributing to a sustainable future with Chrome OS and partners April 22, 2021
- Getty Images supports its workforce with Chrome Browser Cloud Management April 22, 2021
- Help users log in across affiliated sites on Chrome April 22, 2021
- A more helpful Chrome, throughout your workday April 15, 2021
- Admin Essentials: Understanding Policy Precedence for Chrome browser April 14, 2021