[Draft] Web Payments Working Group Charter

Note: This charter has been superseded by the December 2019 charter after review by the W3C Membership.

The mission of the Web Payments Working Group is to make payments easier and more secure on the Web. The group seeks to:

Under this charter, the Working Group defines Recommendations that allow for a payment to be initiated within a Web site or application.

Join the Web Payments Working Group.

Start date 3 February 2020
End date 31 December 2021
Charter extension See Change History.
Chairs Nick Telford-Reed, Invited Expert; Adrian Hope-Bailie, Coil
Team Contact
(FTE %: 40%)
Ian Jacobs
Usual Meeting Schedule Teleconferences: Weekly
Face-to-face: 2-3 per year


Continued Work

The Working Group will continue to advance these existing specifications to Recommendation:

The Working Group will continue to develop the following payment method specification, intended to become a Working Group Note:

Formal Adoption of Work Under Consideration

The Working Group has discussed, but not yet taken up formally, payment method specifications on the following topics:

New Topics

Working Group participants have expressed interest in a number of enhancements to Payment Request 1.0. These include:

The Working Group has discussed the following payment methods but has not developed any draft specifications:

The Working Group will determine which specification type best suits each topic, for example through modifications to Payment Request API, through a payment method specification, or some other specification.

Curation of Working Group Resources

The Working Group will continue to curate the following resources it has published:

The Working Group may publish informational resources (e.g., FAQs or best practices documentation) to support the deployment of its other deliverables.

Out of Scope

The following topics are out of scope for this Working Group.

Security and Privacy Considerations

A key security consideration is the ability to prove message integrity and authentication of all message originators. The Working Group will work with the organizations listed in the liaisons section of the charter to help ensure API security.

Protection of the privacy of all participants in a payment is important to maintaining the trust that payment systems are dependent upon to function. A payment process defined by this group should not disclose private details of the participants' identity or other sensitive information unless required for operational purposes, by legal or jurisdictional rules, or when deliberately consented to (e.g. as part of a loyalty program) by the owner of the information. The design of any API should guard against the unwanted or inadvertent leakage of such data through exploitation of the API.

Relation to Regulatory Requirements

The deliverables of this group should enable parties involved in a payment transaction to meet any and all regulatory obligations.


Recommendation Track Milestones

Note: The group will document significant changes from this initial schedule on the group home page. See below for information about reference drafts.
Specification FPWD Most Recent CR PR Rec
Payment Request API April 2016 April 2019 October 2020 December 2020
Payment Method Identifiers April 2016 April 2019 October 2020 December 2020
Payment Handler API May 2017 June 2020 January 2021 March 2021
Payment Method Manifest December 2017 June 2020 January 2021 March 2021
SRC Payment Method March 2020 September 2020 January 2021 March 2021

Non-Recommendation Track Milestones

On Rechartering

Under this charter, the Working Group intends to deliver specifications for the topics listed in the sections on Recommendation track milestones, Non-Recommendation track milestones, and topics under consideration.

The Working Group would otherwise expect to recharter for other new Recommendation-track deliverables.


For all specifications, this Working Group will seek horizontal review for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the TAG. Invitation for review must be issued during each major standards-track document transition, including FPWD and at least 3 months before CR, and should be issued when major changes occur in a specification.

W3C Groups

Web Application Security
For review of security APIs and features.
Web Authentication Working Group
For discussion of strong authentication.
Web Payment Security Interest Group
For discussions about Web payment security and use cases.

Groups Outside W3C

EMVCo administers many specifications known collectively as EMV®, including specifications about network tokenization, 3-D Secure, and Secure Remote Commerce.
Coordination with ISO TC 68 will help achieve broad interoperability of payment systems (e.g., through alignment between Web protocols and ISO 20022).
Open Banking UK, STET, and Berlin Group
For discussion about open banking APIs and Web payments.


To be successful, the Web Payments Working Group is expected to have a minimum of 10 active participants for its duration. Effective participation in Web Payments Working Group may consume .1 FTE for each participant; for editors this commitment may be higher.

Participants in the group are required (by the W3C Process) to follow the W3C Code of Ethics and Professional Conduct.


This group primarily conducts its work on GitHub and the public mailing list public-payments-wg@w3.org (archive). Administrative tasks may be conducted in Member-only communications.

Information about the group (deliverables, participants, face-to-face meetings, teleconferences, etc.) is available from the Web Payments Working Group home page.

Decision Policy

As explained in the Process Document (section 3.3), this group will seek to make decisions when there is consensus. When a Chair puts a question and observes dissent, after due consideration of different opinions, the Chair should put a question out for voting within the group (allowing for remote asynchronous participation —using, for example, email and/or web-based survey techniques) and record a decision, along with any objections. The matter should then be considered resolved unless and until new information becomes available.

Any resolution first taken in a face-to-face meeting or teleconference (i.e., that does not follow a 7 day call for consensus on the mailing list) is to be considered provisional until 5 working days after the publication of the draft resolution. If no objections are raised on the mailing list within that time, the resolution will be considered to have consensus as a resolution of the Working Group.

Patent Policy

This Working Group operates under the W3C Patent Policy (Version of 5 February 2004 updated 1 August 2017). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis.

For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation.


This Working Group will use the W3C Software and Document license for all its deliverables.

About this Charter

This charter for the Web Payments Working Group has been created according to section 5.2 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.

Charter History

Charter Period Start Date End Date Changes
Initial Charter 21 October 2015 31 December 2017 N/A
Charter Extension 1 January 2018 1 March 2018 None (Rechartering)
2018 Rechartering 9 March 2018 31 December 2019 Deliverables under consideration since the previous charter are listed in section 1.2.
2020 Rechartering 3 February 2020 31 December 2021 Deliverables under consideration since the previous charter are listed in section 1.2.

Reference Drafts as of this Charter

The following information related to the W3C Patent Policy is provided as a convenience.

Payment Request API
Latest publication: 16 April 2019
Reference Draft: https://www.w3.org/TR/2019/CR-payment-request-20190416/
associated Call for Exclusion on 16 April 2019 ended on 15 June 2019
Produced under Working Group Charter: https://www.w3.org/Payments/WG/charter-201803.html
Payment Method Identifiers
Latest publication: 05 September 2019
Reference Draft: https://www.w3.org/TR/2017/CR-payment-method-id-20170914/
associated Call for Exclusion on 14 September 2017 ended on 13 November 2017
Produced under Working Group Charter: http://www.w3.org/Payments/WG/charter-201510.html
Payment Handler API
Latest publication: 24 September 2019
Reference Draft: https://www.w3.org/TR/2017/WD-payment-handler-20170518/
associated Call for Exclusion on 18 May 2017 ended on 15 October 2017
Produced under Working Group Charter: http://www.w3.org/Payments/WG/charter-201510.html
Payment Method Manifest
Latest publication: 12 December 2017
Reference Draft: https://www.w3.org/TR/2017/WD-payment-method-manifest-20171212/
associated Call for Exclusion on 12 December 2017 ended on 11 May 2018
Produced under Working Group Charter: http://www.w3.org/Payments/WG/charter-201510.html

Adrian Hope-Bailie, Ian Jacobs, Nick Telford-Reed

EMV® is a registered trademark in the U.S. and other countries and an unregistered trademark elsewhere. The EMV trademark is owned by EMVCo, LLC.

$Date: 2019/12/16 14:28:14 $