Web Payments Working Group

In late May, about 25 people participated in the first code-a-thon (中国上instagram加速软件) of the Web Payments Working Group. We organized three, 2-hour videoconferences, separated by 22-hour blocks of time for independent collaboration and coding. We learned a lot and saw some great demos!

中国iphone怎么上ins

On the first day participants introduced seven topics. Four of those ended up gaining traction, and we reviewed their progress on the second and third days. I summarize them here.

Payment App with Web Authentication / FIDO Provisioning

Before the code-a-thon, our colleagues from Entersekt had developed a proof of concept for Web-based payment app that supports Web Authentication. In this demo, the user has a payment app from their bank, and the bank authenticates the user as part of risk assessment. Entersekt showed us a video with the following two flows:

• Enrollment: While interacting with their bank, the user installs a Web-based payment app. The payment app prompts the user to enroll a FIDO authenticator. In the video the user enrolls via the phone’s fingerprint reader.
• Transaction: During a subsequent transaction, the user chooses to pay from the same payment app. The user selects the card to pay with, re-authenticates with a fingerprint scan, enters a PIN, and (after some risk assessment process) the bank returns a proof of payment to the merchant who submits it to complete the transaction.

Within the Web Payments Working Group we have been discussing a vision where payment apps are “first-class objects” in the browser, easily registered and managed via browser settings. We face an important question: “Will users want to register payment apps explicitly or will that create too much friction?” It has been argued that users are familiar with the ceremony of downloading and installing apps from an app store. If we adopt a similar approach for payment app registration, this might help increase the user’s understanding of which powers to grant to the payment app.

With that discussion as a back drop, Entersekt worked with the Chrome team to mock up a registration ceremony for their payment app. On the final day of the event they presented a video of a payment app registration mockup. This video only shows the payment app registration and provisioning; the checkout portion of the user experience would be the same as the first video.

This demo is likely to help us advance the conversation about payment app lifecycle and the relationship of explicit registration to trust, privacy, and security.

QR Codes for Multi-Device Checkout

For several years, people have pondered how QR codes might be used as part of Payment Request flows. We saw our first proof of concept during the code-a-thon. Entersekt brought a second demo to the meeting with the following flow:

• The user is shopping in a desktop browser and, at checkout, opts to pay via their phone, leveraging a QR code for communication.
• On the fly, the browser installs a Web-based payment app from the user’s bank
• That payment app computes and displays a QR code that represents some information about the transaction, including the amount and merchant identity.
• The user opens a payment app from the same bank that runs on their phone. That payment app scans the QR code and prompts the user to confirm the transaction.
• The bank server updates the payment app on the desktop to indicate that the transaction has been successful, and the merchant receives a proof of payment.

On the last day, Entersekt shared a QR payment video to illustrate the flow, including new consent mockups that they developed with Chrome.

Authenticate to Pay (Minimal UI)

Last year, the Chrome Team and Coil to explore an “authenticate-to-pay” feature in payment apps that reduces the total number of user gestures to complete a transaction while simultaneously incorporating multi-factor authentication. Worldline colleagues expressed an interest in enhancing one of their existing Payment Request demos with this authentication UX. Working closely with the Chrome team, they made progress on their demo over the two days. The Worldline demo was shared a few days after the code-a-thon. Worldline indicated that they would like next to enhance the demo to satisfy PSD2 requirements, e.g., with an issing bank as the relying party.

The animation below also show the “authenticate-to-pay” user experience. At this time it is only experimental, it only runs on Android, and it does not yet leverage Web Authentication. But I think there is sufficient interest that the Web Payments Working Group will continue to develop the idea.

Here’s what’s going on in the animation: in general payment apps can open windows for user interaction. However, in the authenticate-to-pay user experience, the payment app tells the browser: “if you launch me, I won’t open a window. Instead, please display the amount, beneficiary, and source of funds to the user and prompt them to authenticate using these credentials.” The browser, not the payment app, opens a small window for authentication. The browser then launches the payment app with the results of the authentication. The payment app does not open a window, but does evaluate the authentication results fed to it by the browser as part of completing the transaction. Because the browser opens a small window, this user experience has been nicknamed “minimal UI.”

Mobile Money on the Web

In the past we have had discussions with the GSMA about connecting operator-run mobile money systems to Web payments. The code-a-thon offered us a chance to catch up with GSMA colleagues. Opportunities to bring mobile money to the Web may be growing as smart phones are becoming more common in regions where mobile money is a widely-used payment method.

Although no code emerged from the discussion, Adrian Hope-Bailie did start work on a document for ongoing discussion: Mobile Money and Web Payments. It is possible that we may see more experimentation around mobile money and Web payments through the Mojaloop Project.

Undeveloped Ideas

Although people also expressed interest on day one in the last three topics, they did not lead to further discussion:

• I pitched the idea of demonstrating a comprehensive authentication “cascade” that would provide the “best experience” if supported in the user’s environment, or fall back to a variety of alternatives.
• We also discussed two points raised by Airbnb during TPAC 2019: integration of “card-on-file” payments into the Payment Request ecosystem, and leveraging responses to Payment Request for account creation.

安卓手机中国怎么上instagram

I think that the success of the event hinged largely on preparation by the participants. Entersekt, Worldline, Coil, and Google had all prepared code or documentation. As always, demos focused our attention, raised compelling questions, and drove discussion. I want to thank all the people who brought code to the event.

The Chrome team helped people prepare by creating a 中国上instagram加速软件 for people who want to experiment with the Payment Request and Payment Handler APIs. I encourage you to try it out, share your project, and provide feedback on the starter kit.

Some additional notes:

• Time zones created the usual issues for global participation.
• 焦点分析｜巨头都想做的电商生意，Facebook有备而来:中国消费者对电商工具并不陌生，即使它出现在非传统意义上的电商平台上。比如基因是即时通讯工具的微信小程序电商，又如基因是短视频的抖音小店。Facebook Shops也是类似的逻辑，尤其是在网红内容生态更成熟、离交易更近的Instagram上。
• We relied on IRC channels for chatting over multiple days. We did not do enough to ensure that people would have access to discussion even when they disconnected from IRC. We will definitely need to fix that for a future event (by using a proxy, or Slack, or some other solution).

Thanks to all the participants! I look forward to seeing more proofs of concept soon.

As people shelter in place due to COVID-19, Web usage has increased dramatically. ISPs, platform providers, telcos, content providers, and most other stakeholders are working to ensure that the network can accommodate the surge. It will be very interesting to see which of these behavioral changes remain commonplace once the crisis subsides.

Two weeks ago, against this preoccupying backdrop —as well as some more playful and colorful green-screen effects on WebEx— the Web Payments Working Group held a big meeting to check in on our activities to improve the Web platform for payments and e-commerce (agenda, 在中国怎么上snapchat).

We reworked our Dublin face-to-face agenda into four 2-hour video conference calls on five topics: payment apps, Secure Remote Commerce (SRC) and Payment Request, authentication, open banking, and merchant feedback.

Improving Payment Apps

In recent months, most of the group’s technical focus has been on improving payment apps, the software (Web-based payment handlers or native apps) that people use to respond to payment requests. In particular, the Chrome team conducted a detailed 在中国怎么上snapchat, which led to a set of proposed changes to payment handlers. That second link includes summaries of all the proposals, so I won’t repeat them here. Together the proposals aim to reduce cross-site tracking, fingerprinting, secondary use of collected data, and unnecessary information sharing.

Instagram隐藏点赞数 点赞时代的终结？ - Chinese:2021-7-31 · Instagram从昨天开始在六个国家测试隐藏帖子的点赞数量，网红直接受到重大影响。 今年1月一张再普通不过的鸡蛋照片在发布后的十天成为Instagram上 ...

• Today only Chromium browsers support skip-the-sheet. Because merchants in particular have a strong desire to understand the user’s transaction journey, there was strong support for defining and promoting consistent skip-the-sheet behavior across browsers.
• Today Chrome skips-the-sheet to an already installed payment handler even when an installable payment handler could also be used. That is: Chrome favors installed payment handlers over just-in-time installable payment handlers. The Working Group did not support this approach and a helpful guiding principle emerged from the discussion: by default, a browser should favor user choice of payment handlers over automatic behavior to reduce user gestures (such as skip-the-sheet).
• This principle is likely to play a role in answering another design question: should a browser skip-the-sheet to a payment handler that supports delegation of all merchant requested data, even if another one that does not support full delegation could otherwise be used?
• Similarly, this principle suggests support for a proposal to find and show just-in-time installable payment handlers, even when the user already has one or more applicable payment handlers for a given payment method.

We also discussed a number of user interaction and user configuration topics:

• Good support for 中国iphone怎么上ins (or perhaps in some cases notification) before enabling powerful payment handler features.
• Requiring some form of gesture to grant a payment handler 手机vnp的服务器怎么填.
• Requiring some form of user gesture before just-in-time installation and skip–the-sheet can be used in combination.
• User configuration of a “preferred payment handler” to enable more streamlined checkout flows.
• A proposal that a single user gesture be usable simultaneously to trigger Web Authentication and launch a payment handler.

As a next step, we will consider the feedback on the proposed changes and present a synthesized approach to installation and display that improves user awareness and privacy, maximizes user choice, and facilitates strong authentication, all while continuing to streamline transaction flows.

The Working Group also appreciated learning about a recent security analysis of Web Payments carried out as a Master’s Thesis. We expressed our appreciation to @crowgames, who has summarized three key findings and already begun collaborating with browser vendors on fixes.

免费翻国外墙的app

Our primary objective on the second day of the meeting was to drive toward consensus on an architecture for doing EMV® Secure Remote Commerce (SRC) through Payment Request API. We reviewed in detail a series of flow diagrams for first time users, returning recognized users, and returning unrecognized users.

HiNounou在拜耳Grants4Apps上海2021加速计划中获胜:2021-8-26 · HiNounou 从中国130多家健康领域的创业公司中脱颖而出，成为拜耳Grants4Apps上海2021加速计划中的4名获胜者之一，并将自8月28日在拜耳上海公司参加为期88天的加速训练项目。

• There will be one Payment Method Identifier (PMI) per SRC system. All the PMIs will share a common origin (domain name).
• There will be a “common payment handler” hosted by the same domain. All of the Payment Method Manifests of the SRC systems will refer to the common payment handler as the default payment handler. Having a common payment handler makes it easier to avoid “wallet selection” in the user experience. Instead, when the merchant accepts an SRC Payment method, the browser will be able to skip-the-sheet into the common payment handler.
• Once launched, the common payment handler will only have two roles: (1) to route users to an SRC-I identified by the merchant (2) to store information that will make it easier to recognize a returning user in a future transaction. This approach has the appeal of leveraging existing merchant relationships with SRC-I’s as well as deployed code.

Participants raised some interesting points:

• The data model of a future SRC payment method definition will, for the most part depend on the EMVCo specification. However, it will also need to support custom data passed by the merchant to the target SRC-I.
• We need to make clearer whether the common payment handler will the preferred payment handler of the ecosystem or the only SRC payment handler available.
• 中国版instagram app-中国版instagram app最新版安卓v1.0.0 ...:2021-6-14 · 中国版instagram app是很受欢迎的社交平台，它的交友形似非常的靠谱。平台源自于国外，但经过汉化之后，更适合国内交流。其商业元素在经过汉化之后，去掉了很多，变成了较为纯粹的交友平台，主要目的就是扩展大家的朋友圈。

Once we have converged on the architecture, we will be able to advance to work on a proof of concept as well as the actual specification of the payment method.

Authentication

Representatives from the Web Authentication Working Group shared updates from their February face-to-face meeting.

We discussed the decision to allow Web Authentication get() but not 中国怎么上instagram from within cross-origin iframes in Web Authentication Level 2. On many occasions we have discussed the scenario where, as part of a 3-D Secure (3DS) flow, an issuing bank may wish to insert some code in a merchant site or a payment handler. The recent decision means that at transaction time, the issuing bank will be able to call Web Authentication without the need for a full redirect to the issuing bank’s site. We hope this will enable a superior user experience at the same time it enhances security and risk assessment.

We also discussed a decision to remove the “transaction confirmation” extension in Web Authentication Level 2 due to lack of browser implementation. The feature had been seen as important fulfilling European regulatory requirements under PSD2 around “dynamic linking.” Participants expressed interest in discussing alternatives (e.g., by adding features to the browser to use FIDO authenticator keys to sign information available through the Payment Request API). I anticipate that those discussions will continue in the joint task force between WPWG and WebAuthn.

Open Banking

STET, Open Banking UK, the Berlin Group, and ISO 20022 Registration Authority / SWIFT brought us up-to-speed about various open banking activities, successes, and challenges. Here are some of the points that stood out for me:

• Adoption is growing and the organizations working on APIs continue to revise them.
• Strong Customer Authentication (SCA) remains a challenging topic, especially around the user experience.
• In addition, the Strong Customer Authentication requirement apparently also complicates the accepted fallback solution when the open banking APIs are not available.
• There remains some tension between data collection for risk assessment and privacy regulation (e.g., GDPR).
• The FAPI profile of OAUTH was mentioned multiple times.
• 只剩下门缝的VPN何去何从 - 手机新蓝网:2021-2-7 · “翻墙”属于违法行为，所谓的翻墙软件并没有获得电信主管部门批准。国内“翻墙”用户众多，根据市场研究机构Global WebIndex的调查研究估测，中国的VPN用户可能多达9000万。这也让一些游走在灰色地带的翻墙软件默默赚钱。“翻墙”软件又叫VPN软件。
• There is a growing set of activities around more use cases, including payroll and business-to-business payments.
• The Berlin Group pointed out that when PSD2 is “tranposed” into national legal frameworks, this can introduce subtle differences in requirements and other challenges to interoperability.
• Our colleagues from SWIFT / ISO 20022 Registration authority discussed their collaboration activities with Open Banking UK and the Berlin Group to harmonize the data model across APIs by leveraging the components of the ISO 20022 repository.

We had anticipated experiments combining open banking APIs with Payment Request and Web Authentication at our code-a-thon. A future virtual event may provide the best opportunity for experimentation.

Merchant Feedback

The Working Group values hearing about merchant experiences with the APIs.

Sumantro Das from 1-800-FLOWERS.COM, Inc. shared his experience working with Payment Request API for the past several years. In the past we have discussed findings that show how Payment request can speed up checkout. Sumantro similarly reported an uplift through Payment Request on product pages from Android. Specifically he cited a number of things he liked, including:

• Flexible user interface
• Built-in support for credit card input (in Chrome)
• Leveraging the API in sophisticated real-time availability of product use cases.

Sumantro also gave an assessment of how Payment Request from several perspectives:

• Security: Good, but needs a refresh
• Timeliness: Good
• Transparency: Good
• Convenience: Good, but needs a refresh
• Usability: Good, but needs a refresh
• Universality and accessibility: needs improvement

He also made some concrete implementation suggestions:

• 详细图文方法，国内上维基百科，instagram谷歌地球的流程 ...:2021-5-27 · 详细图文方法，国内上维基百科，instagram谷歌地球的流程【1】.doc 由 waiyou8vpn 上传于 2021-05-27 09:43:26 文件大小 3.59MB。163免费网盘只提供下载，版权属于原作者，如有侵权请联系我 …
• Support address auto-correct in the sheet
• Allow users to enter promotional codes or gift cards (split tender payments)
• Leverage strong authentication further

如何使用苹果手机下载Instagram应用_搜狗指南:2021-10-31 · Instagram是一款可以分享图片、视频的手机社交网络APP，深受全世界各类人群的喜爱，今天就用最简单的方法教会大家使用苹果手机下载Instagram应用。

中国上instagram加速软件

Now a bit on the virtual meeting experience. Although I sorely missed the hallway time of face-to-face meetings, we compensated a bit by opening the bridge 15 minutes early each day for casual chit-chat. If we repeat this type of meeting, I will suggest even more open time.

Because at times 60 people participated, we skipped introductions around the table. Nick Telford-Reed suggested that next time we seek enhanced tooling support, for example being able to easily reach each participant’s affiliation and short bio from IRC or WebEx.

We surveyed the participants following the meeting and so far have heard:

• Very strong consensus that two hours was a good call duration.
• 私搭VPN获利判刑 “翻墙”生存空间渐窄 - China Daily:2021-12-22 · 私搭VPN获利判刑 “翻墙”生存空间渐窄 2021-12-22 09:32:30 （来自：正义网） 杨德灿 吴向洋在未取得《增值电信业务经营许可证》的情况下,在网络上 ...

More useful feedback for other meeting planners:

• Defining clear objectives for each session —generally good practice— proved especially valuable for a virtual meeting.
• Mute all microphones by default
• 快帆 - 简介 | Facebook:快帆. 13,313 次赞 · 31 人在谈论. 「快帆」是一款帮助海外华人用户高速访问中国网络的加速软件，可以让境外华人从国外直连到中国国内。
• The IRC channel also plays an important role for comments, quips, and questions.
• Add a bio break

instagram电脑版下载-instagram电脑版官方下载(含模拟器 ...:2021-12-4 · instagram以一种快速、美妙和有趣的方式将你在任何地方随时抓拍下的图片分享彼此，而且它允许用户选择图片的滤镜样式，并且拥有多种美化工具，如果你是一个照片爱好者，那么千万不要错过这款软件 …

We may soon have another opportunity for a virtual meeting: we had great plans for our Dublin code-a-thon and there is support for holding an online version.

The co-Chairs and I agree that overall this was a successful meeting, and we might take back some lessons for our future face-to-face meetings. For example, I could imagine organizing meetings so that there is only a half-day of very focused discussion, with long breaks and open sessions for ad-hoc discussions.

facebook

The Chairs and I came away from the meeting really energized and with an emerging picture of next steps in each of these major topics, for discussion with the Working Group in the coming days:

• Payment handlers: There’s a growing confidence in the direction and maturity of the payment handler architecture, with great feedback on Instagram,twitter,facebook下载注册使用教程 - 萌V小站:安装完辅助软件之后，下载好软件之后，下载软件参考上面的方法，下面是用法。 启动app ：点击手机屏幕上Instagram的app图标。 创建账户 ：点击屏幕下方的“注册”按钮，可以选择手机号注册；手机号一定 …. Next we will turn those proposals into concrete pull requests, get review from other W3C groups, and benefit from updated implementations.
• SRC: The Card Payment Security Task Force will continue to build consensus around a proposed architecture, in particular among card networks/SRC providers. However, we welcome thoughts from all the WG’s participants and urge them to join the fortnightly task force calls. Once we have sufficient consensus on the architecture the next step will be work on a proof of concept.
• Open banking: It was great to hear so much progress and cooperation among STET, Berlin Group, Open Banking in the UK and SWIFT. We want to continue to collaborate with these groups on a proof of concept that leverages multiple APIs (and possibly our previous work on a credit transfer payment method). Our plan had been to do this work at the code-a-thon in Dublin that we had to cancel. We’d like to tackle this at a virtual code-a-thon, so let us know if you are interested.
• 免费翻国外墙的app: We expect our joint task force with WebAuthn to continue to look at dynamic linking use cases as well as the 中国版instagram app-中国版instagram app最新版安卓v1.0.0 ...:2021-6-14 · 中国版instagram app是很受欢迎的社交平台，它的交友形似非常的靠谱。平台源自于国外，但经过汉化之后，更适合国内交流。其商业元素在经过汉化之后，去掉了很多，变成了较为纯粹的交友平台，主要目的就是扩展大家的朋友圈。. This is an area which feels like we need to apply some rocket assist. The solution feels like it’s within our grasp, but we’ve not quite been able to connect the dots.
• Merchant feedback: We heard more support for addressing split tender use cases (including coupons) which have been with us since the start of the group. Generally speaking, we will continue to seek increased merchant engagement in W3C discussions around Web payments.

I want to thank everyone who participated in the meeting and hope to see everyone soon in healthier times. Many thanks to the Chairs for contributions to this post. Let’s keep making Web payments better!

UPDATE 2020-03-05: Due to travel restrictions around COVID-19, the Web Payments Working Group does not plan to meet face-to-face as scheduled, but will conduct a remote-first alternative meeting.

Last month, W3C renewed the 手机怎么翻ins墙 of the Web Payments Working Group through 2021. The new charter is similar to the previous one, but added explicit mention of a Recommendation-track deliverable related to the use of EMV® Secure Remote Commerce (SRC) via Payment Request API.

At the end of March we will hold our next face-to-face meeting in Dublin, hosted by Airbnb. Our 中国iphone怎么上ins is still rough, but I anticipate discussion of an SRC payment method, the status of browser support for Payment Request and Payment Handler, updates from the joint task force between WPWG and the Web Authentication Working Group, some merchant experiences with the APIs, and perhaps some discussion of the current Irish and/or EU payments landscape. Given the strong customer authentication (SCA) requirements of Europe’s Payment Services Directive (PSD2), I also expect a special focus on streamlined integration of Web Authentication into payments flows.

Regarding SRC, between now and the face-to-face meeting, we are working on a succinct description of “how SRC can work with Payment Request.” This would be the culmination of discussions within the Card Payment Security Task Force about data models and user experience requirements and assumptions. It is also an important precursor to a concrete payment method specification. My goal is for the Working Group to come together around “how it will work” during the face-to-face meeting, and then to initiate work on the payment method definition shortly thereafter.

For the first time we are meeting for a total of 4 days. Included is a 2-day “code-a-thon” where participants will demonstrate how Payment Request, Payment Handler, Web Authentication, and related APIs can be used to create compelling checkout experiences for a variety of payment method and authentication flows. I anticipate we will look at SRC flows, ACH flows, and open banking flows. We also heard from Airbnb last September interest in topics such as integrating card-on-file into the Payment Request user experience (for consistency with guest checkout), and using Payment Request as part of account creation. My hope is that the code-a-thon results in proofs of concept, fodder for good practices documentation, and ideas for new features.

I look forward to seeing colleagues in person, and also visiting Dublin for the first time!

The Web Payments Working Group met face-to-face 16-17 September as part of TPAC 2019 (agenda, minutes).

The meeting was well-attended, energetic, and brimming with new ideas. I left with the impression that we have a lot to do, but also that we have lots of material to work with, and a growing community to do the work.

The post is long; many thanks to Nick Telford-Reed for helping to make it shorter than it was!

Payment Request API 1.0

To publish our main specification as a Proposed Recommendation we need to address two topics:

1. A Webkit update following a specification change; this is underway.
2. The formal objection previously raised when we advanced to Candidate Recommendation for which there is a proposal for a new feature.

中国版instagram app-中国版instagram app最新版安卓v1.0.0 ...:2021-6-14 · 中国版instagram app是很受欢迎的社交平台，它的交友形似非常的靠谱。平台源自于国外，但经过汉化之后，更适合国内交流。其商业元素在经过汉化之后，去掉了很多，变成了较为纯粹的交友平台，主要目的就是扩展大家的朋友圈。

• whether to gather implementation experience before requesting to advance Payment Request 1.0 (likely to require a number of months); or
• to request to advance with this feature as optional for browsers to implement.

The consensus of the group is that the feature set of v1.0 is otherwise stable.

Payment Handlers

We believe we need more broad and interoperable support of both Web-based and native payment handlers. An important objective of the meeting was to understand how to encourage additional adoption.

The Chrome team cited a number of benefits of payment handlers, including expectations for higher completion rates, better connectivity properties, lower implementation effort, increased reliability, and improved security. Because payment handlers operate as top-level origins (unlike iframe-based checkout solutions) they provide new opportunities to streamline authentication.

Chrome demoed new features since our April meeting, including full delegation of requests for contact and shipping info to payment handlers, great tooling to aid developers, and a new “minimal” user experience where the user simply sees the total and a prompt to authenticate.

Other suggestions to expand our adoption strategy included:

• 《大数据白皮书（2021）》：数据安全合规要求不断提升 ...:2021-12-10 · 12月10日，中国信通院发布了《大数据白皮书（2021）》，这是中国信通院第四次发布大数据白皮书。白皮书在前三版的基础上，聚焦一年多来大数据各领域的发展，探讨了大数据技术、产业、应用、安全及数据资产管理的进展和趋势。
• Conduct more outreach to more merchants, for example via a specialized forum within W3C for merchants to share use cases and requirements.
• 潘达工具箱 - 史上最全面的外网工具注册&使用教程:2021-4-29 · 超好用的Win10电脑外网连接软件推荐 5款最适合安卓手机上外网的软件 国内苹果手机用户首选加速器 加速推荐 2021年科学上网方法整理-Express科学加速测评 游戏&娱乐 怎么在中国看网飞（Netflix） Pixiv官网如何注册账号 怎么看R-18 Fakku绅士站官网登录
• Organize a hackathon to bring together, in particular, merchants, payment handler developers, and browser vendors to demonstrate the value of Payment Request and Payment Handler.
• Improve tooling and testing for developers

We also looked at possible improvements in interoperability and user experience:

• Chrome supports two popular behaviors that are not formally specified: “just-in-time installation” and “skip-the-sheet”. As consistency of user experience is important, we might informatively describe Chrome’s implementation and encourage other browser vendors to adopt the same behaviors.
• The Chrome implementation of Payment Handler API includes a secure modal dialog where the payment handler code executes. This may be a useful type of dialog for other use cases beyond payments, which might make it more attractive from a browser maker perspective. Editor’s note: Since the meeting we have begun work on a modal window explainer.
• Re-evaluating the role of the “sheet” because:
  • Shopify findings suggested users were surprised by this new UX element.
  • Browser vendors report there is a high cost to maintaining a good UX for the data contained in the sheet.
  • Payment handler developers have asked to be able to handle requests for stored data rather than the browser.
  • Mixing “applications” and “instruments” (e.g., card data) in the sheet may confuse users.
  • Implementers may be able to devise superior “selector” experiences, including optimizations for selection of default payment handlers.

Airbnb Experience with Payment Request

Airbnb saw Payment request API as a means to remove complex billing forms, streamline first-time bookings, connect data collection to account creation, and access more payment methods (e.g., Apple Pay and Google Pay). They shared some of their experiences (slides):

• Ideally Payment Request would be “the one API.” However, Airbnb has to provide two flows to support both new and stored cards. They asked: could we integrate cards previously stored by the merchant into Payment Request?
• Could Payment Request give access to label and style information in the sheet to avoid terminology differences between the sheet and a custom checkout?
• 免费加速器官网_免费加速器_免费加速器加速 - 云+社区 - 腾讯云:2021-10-31 · 科技企业加速器（EnterpriseAccelerator），是一种以快速成长企业为主要服务对象，通过服务模式创新充分满足企业对于空间、管理、服务、合作等方面个性化需求的新型空间载体和服务网络，具有较强的集群吸引力和创新网络形态。是介于企业孵化器和科技园区之间的一种中间业态。
• Could we unify guest checkout and new account creation with the merchant, ideally as part of the Payment Request experience, so that the user creates credentials and agrees to terms of service? This suggestion raised concerns that adding too much to the API might make it too heavy-weight.

Airbnb would like to see more interoperable support for payment handlers across browsers, and access to more payment handlers, reinforcing the group’s observations about the need for more payment handler support.

Card Payments

The Card Payment Security Task Force has been working on a Secure Remote Commerce (SRC) payment method definition. Mastercard showed a new demo of three user journeys:

1. New user who is enrolling a card in an SRC system
2. 中国版instagram app-中国版instagram app最新版安卓v1.0.0 ...:2021-6-14 · 中国版instagram app是很受欢迎的社交平台，它的交友形似非常的靠谱。平台源自于国外，但经过汉化之后，更适合国内交流。其商业元素在经过汉化之后，去掉了很多，变成了较为纯粹的交友平台，主要目的就是扩展大家的朋友圈。
3. Returning user but using Web Authentication

The demos included using Web Authentication when accessing a list of candidate cards from SRC systems, and when, on selecting a card, the issuing bank requests authentication.

The demos showed that the user might be authenticated multiple times in some flows, leading us to discuss ways to minimize friction:

• A payment handler might authenticate a user directly, or embed an SRC authentication experience.
• Parties might share authentication results. For example, a payment handler might authenticate the user. Some SRC systems might trust those authentication results, reducing friction when accessing the candidate card list.
• A payment handler might re-use of authentication results as input to a 3DS risk assessment process, making a subsequent 3DS step-up less likely.

We briefly looked at ways to leverage identity known to the browser to simplify SRC transactions.

The Working Group strongly supported continued work by the Card Payment Security Task Force on an SRC payment method definition. Additionally, there was support for 3-D Secure through Payment Request, independent of SRC.

手机vnp的服务器怎么填

The “Basic Card” payment method is currently supported in Chrome, Edge, and Samsung Internet Browser through “built-in” payment handlers. There are currently no expectations for support in either Safari or Mozilla, which led some people to argue that we should move away from Basic Card and focus on SRC. Others said that Basic Card remains a useful payment method at least in the short term because full SRC adoption will require time, and some merchants many not move to SRC.

为何国内没有做成类似instagram这类主打图片社交形态的产品 ...:2021-12-14 · 盈利数据：Instagram 逐渐成为仅次Facebook（全球最大社交软件20亿+用户）、YouTube（15亿+用户）等社交娱乐平台外最受广告主欢迎的产品。相关数据显示，Instagram 在 2021 年 2 季度广告收入增长 177%，广告展示量增加了 209%。

Merchant and Consumer Pain Points

We organized a session on 快帆 - 简介 | Facebook:快帆. 13,313 次赞 · 31 人在谈论. 「快帆」是一款帮助海外华人用户高速访问中国网络的加速软件，可以让境外华人从国外直连到中国国内。 both to validate that our current work is addressing industry needs, and to identify and prioritize requirements as we recharter the group.

The session organizers pre-selected 15 pain points for discussion. During the presentation, people added a few more:

• Some merchants may not ship to some locations (e.g., smaller countries). One idea to help merchants was to geo-locate the IP address of the user and display a warning at the start of checkout.
• Friendly fraud, such as when a child uses a parent’s account to make a purchase (without parental consent) leading to discussion about device profiles and configurations (e.g., “this biometric is authorized to make payments; this one is not.”). In practice, segmenting biometric templates raises usability issues and therefore is uncommon.

We then split into four breakout groups for “importance / difficulty” evaluation of the pre-selected pain points. Some preliminary findings:

• Some pain points could be addressed through more widespread adoption of payment handlers.
• Two groups suggested reframing “speed up checkout” as “find the optimal checkout speed.” For example, checkout could involve more help for new users, and could involve less friction for repeat customers.
• We need to be clearer in our next conversations about audience: when we say “account-free,” what kind of account do we mean? When we say “difficult,” which stakeholder does that refer to?

The Working Group will look for patterns across the breakout group findings and otherwise continue to refine the analysis as part of rechartering.

Payments in Asia

We invited colleagues from JCB and SWIFT Asia to share updates on the payments landscape in Japan and Asia more broadly. We heard specifically about:

• A new QR code standard for in-person payments in Japan. Several people expressed support for more work on QR codes for online payments in our next charter.
• SWIFT initiatives around real-time payments in Australia and GPI, which focuses on improving cross-border payments.

We were treated to a demo of GPI through Payment Request API. The demo involved a push payment initiated by the payment handler, which then returned information that enables the merchant track the status of payment within the GPI system.

免费翻国外墙的app

The Working Group has discussed Web Monetization at its face-to-face meetings for over a year. We heard about progress on the Web Monetization specification since April.

On the first day of the Working Group’s meeting, Coil announced a Grant for the Web, in partnership with Mozilla and Creative Commons. According to the Web site, “Grant for the Web is a $100M fund to boost open, fair, and inclusive standards and innovation in web monetization.”

Naturally, we asked how this relates to Web Payments Working Group deliverables. Coil indicated that there is a likely need for both a payment method definition and enhancements to payment handler functionality to support the Web Monetization model. For example, today content providers include a 中国怎么上youtub element in their pages to indicate where they can receive payment. That could be replaced by calls to Payment Request API.

Web Monetization is called out in our current charter and I anticipate it will also feature in our new one.

Web Authentication and Payments

Several members of the Web Authentication Working Group joined us to talk about their upcoming new features including so-called “TLD+1” use cases, where Web Authentciation may be called from within an embedded iframe. For example, if a Web-based payment handler were to embed code from an issuing bank origin in an iframe, the issuing bank would not be able to use Web Authentication Level 1, but would be able to use the intended Web Authentication Level 2.

We also discussed:

• “Carrying authentication downstream” to avoid multiple authentications (and reduce friction).
• 灰色地带不再 只剩下门缝的VPN何去何从_科技_腾讯网:2021-2-7 · 比如，加速精灵是一家稳定运营三年的老牌VPN商，目前主营美国、中国香港、日本、中国台湾、德国、韩国的高速线路，支持电脑各种系统、手机安 ...
• Dynamic linking requirements under PSD2 and how to secure the display for authenticators that do not have their own display.
• Token binding and its potential role in risk assessment.

教你轻松登录使用Ins-百度经验:2021-10-30 · 教你轻松登录使用Ins,如今越来越多的明星会在i上发布动态，你是否有为登录不了而烦恼呢？一个简单的方法，使你不管在国内国外，都能轻松登录使用i，不错过idol的每一张自拍，每一张动态，想必心情也会美滋滋

Rechartering

The Working Group’s current charter expires at the end of the year. In Japan the participants expressed a strong expectation that we would recharter, so the co-Chairs and I will begin work on a draft to include:

• Completion of Payment Request API 1.0
• Enhancements in Payment Request API 1.1
• Continued work on Payment Handler API
• Continued work on an SRC payment method as well as discussion of identity and user experience issues
• Web Monetization in some capacity

Personally, I think more discussion is required before we include the following:

• Basic Card. I think we need to reach a better shared understanding of the role of Basic Card, and then document that in the charter.
• 3DS support outside of an SRC context.
• QR codes. The QR code discussions we had in Japan focused on physical world payments; I think we need a better understanding of the relationship to Payment Request.

As always, I would like to thank all of the Working Group participants for contributing to this effort. Each year I appreciate the camaraderie and energy boost of TPAC. I look forward to our next phase of Web payments innovation.