(Google)由于Payment Request API背后的魔力， (Payment Request API)Google正在积极为其Chrome浏览器添加电子商务风格。最近，Chrome正在扩展其功能，以提高您的互联网浏览体验。还有什么比简化最终提高用户生产力的在线购买体验更好的方法呢？
谷歌浏览器(Google Chrome)重新定义在线支付体验
chrome://flags后面提供了谷歌浏览器新的一键式结账体验(one-click, one-tap checkout experience)，允许用户尝试实验性的Web Payments API功能。另一个属于同一Web Payments类别的实验性(Web Payments)Chrome标志允许Payment Request API在可能的情况下打开最小的 UI。
现在，Chrome希望显着改善和加快您的电子商务体验(speed up your e-commerce experience)。因此，Chrome对其存储支付相关信息的方式进行了重大改革。通过这种方式，Chrome正在寻求简化在(Chrome)Mac、Windows、Linux、Chrome OS和Android上下达电子商务订单的过程。
Payment Request API已经存在了相当长的一段时间。然而，谷歌(Google)表示，它的重点已经从试图弄清楚支付请求 API(Request API)如何对商家直接有价值，转移到API(APIs)如何在网络上实现更好的支付应用体验。
“We’ve learned that building a compelling payment flow requires much more than just returning a credit card number. That’s why we are switching gears to focus on enabling payment apps through the Web Payments APIs,” said Eiji Kitamura, Developer Advocate at Google.
Chrome不仅希望充当商家、用户和支付方式之间的中介，还希望在应用程序界面内为用户提供无表单支付体验。它可以在最少使用移动设备键盘的情况下实现更快的结账和支付处理。因此(Hence)，开发者可以在很大程度上改善用户的支付体验。
尽管66%(66 percent)的商业流量来自移动设备，但谷歌(Google)表示，移动转化约占桌面转化的三分之一(one-third)。谷歌(Google)认为移动设备上较低的转化率是结帐表格复杂的结果。
过去，谷歌使用(Google)Autofill简化了结帐流程，据称这使移动设备的转化率提高了25% 。(25 percent)尽管Autofill可能会摆脱数据输入的手动性质，但Google认为它仍然基于相同的结帐流程，Google正在积极尝试通过Payment Request API解决这一问题。
弥合原生支付应用程序的差距
与 Web 应用程序不同，本机应用程序提供无摩擦的在线支付体验。Chrome用户通常必须填写冗长的表格，并通过弹出窗口和重定向执行多个步骤才能完成网络支付。现在，Payment Request和Payment Handler API(Payment Handler APIs)共同承诺弥合( bridge the native payments app gap)Chrome 中的原生支付应用程序差距。
“Payment Request API provides a standardized way to invoke a version-mediated, low-friction payment flow on the web similar to what users might already be familiar with in many native apps,” Kitamura continued. “Payment Handler API allows payment apps to plug into the primary guest API to enable form-free payments on the web.”
测试 Chrome 的更快结帐速度
网站调用支付请求 API(Payment Request API)并提供支付参数，包括成本和兼容的支付选项。然后， Chrome(Chrome)会确定网站支持的支付方式与用户在浏览器中配置的支付方式的交集。最终，Chrome允许用户选择他们喜欢的付款方式。
Chrome用户可以输入新的送货地址或选择现有地址。他们可以选择适用的交付方式。付款方式可以是信用卡或安装在其设备上的钱包应用程序之一，例如Google Pay。最后，用户点击“支付”。然后，Chrome 会请求所选付款方式的响应。
支付处理器首先验证请求，然后将响应直接返回给服务器。这样，网站就拥有了处理付款所需的所有信息，进一步消除了离开结帐页面上下文的需要。
同时，支付处理程序 API(Payment Handler API)带来了一个全新的生态系统，允许基于 Web 的支付应用程序充当支付方式并将自身集成到商家网站中，这得益于标准的支付请求 API(Payment Request API)。
(Wallet)Google Pay等电子钱包应用程序可以构建在Web Payments API(Web Payments APIs)之上。现有支付应用程序可以通过多种方式与Payment Request API集成。正如Google解释的那样，其中一种选择是通过在他们现有的支付体验中添加一个服务工作者来实现支付处理程序 API(Payment Handler API)。
Google Chrome电子商务的未来
Payment Handler API中的“委托”功能允许支付应用程序提供商家请求的所有信息，例如运输和联系信息。以前，相同的信息过去总是来自浏览器。
目前，谷歌希望支付处理程序(Payment Handlers)有足够的时间来适应未来通过网络浏览器进行的无障碍电子商务。您可能会问，什么是Payment Handler？好吧(Well)，支付处理(Payment Handler)程序是一个代表用户处理支付请求的 Web 应用程序。
Web应用程序必须指定它们是否处理送货地址和联系信息。他们可以指定是否单独支持每个付款选项，也可以指定是否支持所有付款选项。谷歌表示，向(Google)支付处理(Payment Handlers)商提供送货地址和付款人联系信息的完整授权是最终的图片。
根据TheWindowsClub看到的一份技术文件，谷歌(Google)并没有强制支付处理程序(Payment Handlers)在短期内处理运输/联系要求。
Chrome可以直接跳转到支付处理程序。如果电子商务网站在Payment Request API中表明支持单一支付方式，则必须使用URL标识支付方式。在另一种情况下，用户必须为支持的付款方式安装至少一个付款处理程序。(Payment Handler)
如果用户没有为支付方式安装支付处理程序，则应通过即时注册的方式注册支付处理程序。当满足这些条件时，用户手势和Chrome将触发付款请求(Payment Request)，并且浏览器将跳过工作表。
“Together, delegation and skip-the-sheet enable payment apps to more easily transition their existing flows to the Payment Handler API.”
该功能的工作原型位于Desktop(Desktop)上的“Experimental Web Platform features”标志后面。Google计划在除Android Webview之外的所有平台上实施该功能，因为它表示付款(Payment)处理程序API未针对Android Webview实施。
一键结帐以替换Chrome中的基本卡片(Chrome)
(Chrome)谷歌(Google)证实， Chrome最终将不再支持基本卡(basic-card)支付方式。谷歌(Google)最初以基本卡的形式将支付请求 API(Payment Request API)添加到Chrome，作为基于表单的信用卡支付的替代方案。使用基本卡，客户可以选择存储在浏览器中的信用卡以更快地付款。谷歌(Google)表示，它正在冻结Chrome内置基本卡支持的功能开发，但错误修复除外。
除了Chrome之外，支付请求 API(Payment Request API)还与基于 Chromium 的新 Microsoft Edge(Chromium-based Microsoft Edge)兼容。同时，该功能目前正在Firefox和Safari浏览器中开发。
Google Chrome ships online shopping feature to place orders with one tap
Google is actively adding an e-commerce flavor to its Chrome browser thanks to the magic behind the Payment Request API. Of late, Chrome is expanding its capabilities to make your internet browsing experience more productive. And what better way is there than simplifying online purchasing experiences that ultimately boost users’ productivity?
Google Chrome redefines online payments experience
Google Chrome’s new one-click, one-tap checkout experience is available behind chrome://flags that allows users to try experimental Web Payments API features. Another experimental Chrome flag falling under the same Web Payments category allows the Payment Request API to open a minimal UI when possible.
Now, Chrome wants to dramatically improve and speed up your e-commerce experience. As a result, Chrome is bringing a major overhaul to the way it stores payment-related information. This way, Chrome is looking to simplify the process of placing e-commerce orders on Mac, Windows, Linux, Chrome OS, and Android.
The Payment Request API is around for quite some time now. However, Google says its focus has moved from trying to figure out how Payment Request API can be directly valuable to merchants to how the APIs can enable better payment app experiences on the web.
“We’ve learned that building a compelling payment flow requires much more than just returning a credit card number. That’s why we are switching gears to focus on enabling payment apps through the Web Payments APIs,” said Eiji Kitamura, Developer Advocate at Google.
Chrome not only wants to act as an intermediary between merchants, users, and payment methods but also provides users with form-free payments experience within the application interface. It enables faster check out and payment processing with minimal use of the mobile device keyboard. Hence, developers can improve the user’s payment experience to a significant extent.
Despite 66 percent of commercial traffic originating from mobile devices, Google says mobile conversions are about one-third of the desktop conversions. Google believes the lower conversions on mobile devices are the result of complex checkout forms.
In the past, Google simplified the checkout process with Autofill, which it says resulted in a 25 percent improvement in conversions on mobile devices. Although Autofill might get rid of the manual nature of data entry, Google thinks it is still based on the same checkout flow, something Google is actively trying to address with the Payment Request API.
Bridging the native payments app gap
Native apps offer a friction-less online payment experience, unlike web apps. Chrome users often have to fill a lengthy form and follow multiple steps through pop-ups and redirects to complete a payment on the web. Now, Payment Request and Payment Handler APIs together promise to bridge the native payments app gap within Chrome.
“Payment Request API provides a standardized way to invoke a version-mediated, low-friction payment flow on the web similar to what users might already be familiar with in many native apps,” Kitamura continued. “Payment Handler API allows payment apps to plug into the primary guest API to enable form-free payments on the web.”
Putting Chrome’s faster checkout to test
Websites call the Payment Request API and offer parameters of the payment including cost and compatible payment options. Chrome then determines the intersection of payment methods supported by the site and payment methods that the user has configured within the browser. Ultimately, Chrome allows users to choose their preferred method of payment.
Chrome users can enter a new address for the delivery or choose the existing one. They can select the delivery method where applicable. The payment method can be credit cards or one of the wallet apps that are installed on their device such as Google Pay. Finally, the user taps on ‘Pay.’ Chrome then requests a response from the selected payment method.
The payment processor first verifies the request and then returns the response directly to the server. This way, the website has all of the necessary information to process the payment, further eliminating the need for leaving the context of the checkout page.
Meanwhile, the Payment Handler API results in a whole new ecosystem, allowing a web-based payment application to act as a payment method and integrate itself into merchant websites, courtesy of the standard Payment Request API.
Wallet apps such as Google Pay can be built on top of the Web Payments APIs. There are different ways an existing payment app can integrate with the Payment Request API. As Google explains, one of the options is to implement the Payment Handler API by adding a service worker to their existing payment experience.
The future of e-commerce with Google Chrome
‘Delegation’ feature in the Payment Handler API allows a payment app to provide all the information requested by the merchant such as shipping and contact information. Previously, the same information used to always come from the browser.
For now, Google wants Payment Handlers to have enough time to adapt to the future of hassle-free e-commerce via web browsers. What is a Payment Handler, you may ask? Well, a Payment Handler is a web application that handles a request for payment on behalf of the user.
Web apps must specify whether or not they handle shipping address and contact info. They can either specify if they support each of the payment options separately or specify if they support all of the payment options. Google says a full delegation of providing shipping address and payer’s contact information to Payment Handlers is the end picture.
According to a technical document seen by TheWindowsClub, Google is not making it mandatory for Payment Handlers to handle shipping/contact requirements anytime soon.
Chrome can straightaway jump to a payment handler. If the e-commerce website indicates support for a single payment method in Payment Request API, then the payment method must be identified with a URL. In a different scenario, the user must have at least one Payment Handler installed for the supported payment method.
In case the user has no payment handler installed for the payment method, the payment handler should be registered through just-in-time registration. When these conditions are satisfied, a user gesture and Chrome will trigger Payment Request and the browser will skip the sheet.
“Together, delegation and skip-the-sheet enable payment apps to more easily transition their existing flows to the Payment Handler API.”
A working prototype of the feature is behind the “Experimental Web Platform features” flag on Desktop. Google plans to implement the feature on all platforms except Android Webview since it says Payment handler API is not implemented for Android Webview.
One-click checkout to replace basic cards within Chrome
Chrome is eventually deprecating the support for the basic-card payment method, Google has confirmed. Google initially added the Payment Request API to Chrome in the form of basic-cards as an alternative to form-based credit card payments. With basic-cards, customers can select the credit cards stored in the browser to make faster payments. Google says it is freezing feature development on Chrome’s built-in basic card support, except bug fixes.
In addition to Chrome, the Payment Request API is also compatible with the new Chromium-based Microsoft Edge. Meanwhile, the feature is currently in development in Firefox and Safari browsers.
