こんにちは TAG-さん!

I'm requesting an early TAG design review of Payment link type in HTML.

Certain push payment flows can cause high friction for users (e.g. display of a QR code that the user needs to scan with an eWallet app). Browsers may have the ability to more easily facilitate these payment flows (e.g. if the user has a wallet installed on their device that supports the underlying payment method for the displayed QR, or has a browser extension for the supported eWallet). Payment link type in HTML is designed to better assist users with payments.

• Explainer: https://github.com/WICG/paymentlink/blob/main/README.md
• User research: QR-based payments are very prominent in south east asian countries. User research in some of these regions have shown that the current online payment experience is very clunky and involves multiple steps. The friction caused by these steps lead to issues like drop offs, wrong payment amount etc. Considering browsers play a significant role in these payment flows, there is significant value in the browser enabling an optimized user experience by reducing the number of steps required to complete payment.
• Security and Privacy self-review: https://github.com/WICG/paymentlink/blob/main/security-privacy-questionnaire.md
• GitHub repo: https://github.com/WICG/paymentlink/
• Primary contacts:
  • Junhui He (@ynyhxfo ), Google, editor
  • Domenic Denicola (@domenic ), Google
  • Rouslan Solomakhin (@rsolomakhin ), Google
  • Aneesh Ali (@aneeshali ), Google
  • Sujie Zhu (@sujiezhu), Google
• Organization/project driving the design: Google
• Multi-stakeholder feedback:
  • Mozilla comments: https://github.com/mozilla/standards-positions/issues/1112
  • WebKit comments: https://github.com/WebKit/standards-positions/issues/428
  • Web Developers
  • we have heard significant excitement for using this feature to reduce the friction of push payment flow. And public feedback is provided on https://github.com/WICG/proposals/issues/150.

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• The group where the incubation/design work on this is being done (or is intended to be done in the future): WICG
• The group where standardization of this work is intended to be done ("unknown" if not known): WHATWG (HTML Standard)
• Existing major pieces of multi-implementer review or discussion of this design: TPAC 2023
• Major unresolved issues with or opposition to this design: None
• This work is being funded by: Google

You should also know that...

The public design doc for the Chromium implementation might also be interesting, as it has more concrete details on what a full implementation will look like, and on one browser's concrete plans for the initial set of supported URL schemes.