W3C home > Mailing lists > Public > public-payments-wg@w3.org > January 2021

Call for Consensus to publish Payment Request API as a Proposed Recommendation - reply requested before 27 January

From: Ian Jacobs <ij@w3.org>
Date: Mon, 18 Jan 2021 10:00:38 -0600
Message-Id: <056C1CE6-51A3-4D26-9FCD-113CAF79AAC3@w3.org>
To: Web Payments Working Group <public-payments-wg@w3.org>
Dear Web Payments Working Group Participants,

This is a Call for Consensus to publish Payment Request API as a Proposed Recommendation:

 Payment Request API
 (Specific GitHub snapshot [1])

If you are a Working Group participant who supports the proposal, please reply with an email to on this thread list that says "1. Support the proposal.” We prefer explicit support to silence.

We would like to thank the editors for preparing these documents.

PLEASE RESPOND to the proposal by 27 January 2021 (17h00 UTC).

For the co-Chairs,
Ian Jacobs

[1] https://github.com/w3c/payment-request/tree/137af6bbfa807f449e15b454cb4d4fb81e94703c


That the Web Payments Working Group request that the W3C Director approve publication of Payment Request API as a Proposed Recommendation. The specification has not changed since publication as a Candidate Recommendation [1] in December 2020.

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.

We invite you to include rationale in your response.

If there is strong consensus by 27 January 2021 (17h00 UTC) for the proposal, it will carry.

[1] https://www.w3.org/TR/2020/CR-payment-request-20201203/


* If you wish your LACK of support to publish to be conveyed to the Director and reviewed, please include the phrase "FORMAL OBJECTION” in your response and be sure to include substantive arguments or rationale. The W3C Director takes Formal Objections seriously, and therefore they typically require significant time and effort to address.

* 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.

For more information, see:


* In the case where this Call for Consensus results in a decision to publish, the Chairs will request approval from the W3C Director to publish the Proposed Recommendation (including review of any Formal Objections).

* See the optimistic timeline to Recommendation:

Ian Jacobs <ij@w3.org>
Tel: +1 718 260 9447
Received on Monday, 18 January 2021 16:00:43 UTC

This archive was generated by hypermail 2.4.0 : Monday, 18 January 2021 16:00:44 UTC