DECISION: Regarding Call for Consensus to publish Payment Request API as a Proposed Recommendation; please review one change by 1 February.

Dear Web Payments Working Group,

In response to the 18 January Call for Consensus [1] to publish Payment Request API as a Proposed Recommendation the Working Group received support from six Working Group participants and an objection from one non-participant, Anders Rundgren [2]. Adrian Hope-Bailie
provided a substantive response [3] to the objection.

The Chairs hereby record a decision that the 18 January proposal carries. After 1 February the Chairs plan to share the specification and the public objection in a formal transition request to the Director.

Just prior to the Call for Consensus, a new issue (936 [4]) was raised on Payment Request API. Discussion on GitHub resulted in a proposal to
add a paragraph to the "Security and Privacy Considerations" section. The Chairs believe that the paragraph does not add a new substantive
requirement to the API. Instead, it states explicitly one aspect of a broader existing requirement about how information is shared across origins, and what is expected of browsers to mitigate privacy risks related to payment handlers.  The proposal appears to have the support of the person who raised the issue [5]. There is now a pull request [6] to include the addition in the upcoming Proposed Recommendation.

If you have any objections to the addition, please let us know by 1 February (3pm UTC), preferably by commenting on the pull request.

Other than boilerplate text, this is the only change to the specification we anticipate as it advances to Proposed Recommendation.

For more information about next steps and timing, see [7].

For the co-Chairs,
Ian Jacobs


Ian Jacobs <>
Tel: +1 718 260 9447

Received on Wednesday, 27 January 2021 20:34:21 UTC