Re: Call for Consensus to take up Facilitated Payment Link Type in HTML (please respond by 23 October)

🥳

1. Support the proposal.

(Not surprising to anyone, I expect! ;)).

On Thu, 9 Oct 2025 at 14:02, Ian Jacobs <ij@w3.org> wrote:

> Dear Web Payments Working Group Participants,
>
> This is a Call for Consensus to take up the following proposal as a formal
> deliverable of the Web Payments Working Group (as described in our charter
> [1]).
>
>    Facilitated Payment Link Type in HTML
>    https://wicg.github.io/paymentlink/
>
> We discussed this proposal briefly at our call today [2] and previously at
> our 28 August meeting [3] and 30 January meeting [4].
>
> PLEASE RESPOND to the proposal by 23 October (16h00 UTC).
>
> For example, if you support the proposal, respond to this list with "1.
> Support the proposal."
>
> For the co-Chairs,
> Ian Jacobs
>
> [1] https://www.w3.org/Payments/WG/charter-2025.html#incubation
> [2] https://www.w3.org/2025/10/09-wpwg-minutes.html#4978
> [3] https://www.w3.org/2025/08/28-wpwg-minutes.html#3960
> [4] https://www.w3.org/2025/01/30-wpwg-minutes.html#a59a
>
> ----------------------
> BACKGROUND
>
> An explainer is available:
>  https://github.com/WICG/paymentlink/blob/main/README.md
>
> Please also see the following document for discussion of this proposal and
> how it compares with other wallet technologies, including Payment Request
> API:
>  https://github.com/w3c/webpayments/blob/gh-pages/wallet-tech.md
>
> --------
> PROPOSAL
>
> That the Web Payments Working Group take up the Facilitated Payment Link
> Type in HTML proposal as a Recommendation Track specification:
>  https://wicg.github.io/paymentlink/
>
> Please indicate one of the following in your response:
>
> 1. Support the proposal.
>
> 2. Request some changes, but support the proposal even if suggested
> changes are not taken into account.
>
> 3. Request some changes, and do not support the proposal unless the
> changes are taken into account.
>
> 4. Do not support the proposal (please provide rationale).
>
> 5. Support the consensus of the Web Payments Working Group.
>
> 6. Abstain.
>
> -----------------
> FORMAL OBJECTIONS
>
> * Formal Objections are described in the W3C Process Document
>    https://www.w3.org/policies/process/#registering-objections
>
> * To register such an objection to this proposal, please include the
> phrase "FORMAL OBJECTION” in your response and be sure to include
> substantive arguments or rationale.
>
> * Silence will be taken to mean there is no Formal Objection.
>
> * If there are Formal Objections, the Chairs plan to contact the
> individual(s) who made them to see whether there are changes that would
> address the concern and increase consensus to publish.
>
> ----------
> NEXT STEPS
>
> * In the case where this Call for Consensus results in a decision that the
> proposal carries, the staff will work with the editors to discuss a
> timeline for publishing this document as a First Public Working Draft. We
> also anticipate discussion of this proposal during TPAC 2025.
>   https://github.com/w3c/webpayments/wiki/Agenda%E2%80%90TPAC2025
>
> * To raise issues on the proposal, please use this issues list:
>    https://github.com/WICG/paymentlink/issues/
>
> --
> Ian Jacobs <ij@w3.org>
> https://www.w3.org/People/Jacobs/
> Tel: +1 917 450 8783 <+1%20917-450-8783>
>
>
>
>
>
>
>

-- 
smcgruer • he / him