Call for Consensus to Remove PaymentItem.type from Payment Request API - Review Requested by 18 October

Dear Web Payments Working Group Participants,

In February of this year we identified "PaymentItem.type" as a feature at risk in the Candidate Recommendation of Payment Request API. This was done so that we could drop the feature from the specification in case of issues or insufficient implementation, without having to delay the advancement of the specification. To date, only one browser maker (Mozilla) had announced plans to implement the feature. However, after some experimentation and user testing, Mozilla has decided not to ship this feature either. We have not heard additional interest from other implementers or merchants. 

This is a call for consensus to remove the "PaymentItem.type” feature from Payment Request API. Removal at this time does not preclude inclusion of this feature or a similar one in a future version of the API.

For more background information about the feature, see issue 163 [1].

Working Group participants are invited to respond to this proposal by 18 October 2018 (10am ET).

For the co-Chairs,
Ian Jacobs



That the Web Payments Working Group drop the “PaymentItem.type" feature from the Payment Request API Candidate Recommendation by adopting this pull request (possibly with minor editorial changes):

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 18 October (10am ET) for the proposal,
it will carry.

Formal Objections

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

Ian Jacobs <>
Tel: +1 718 260 9447

Received on Wednesday, 10 October 2018 12:50:56 UTC