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.
|Start date||19 December 2019|
|End date||31 December 2021|
|Charter extension||See Change History.|
|Chairs||Nick Telford-Reed, Invited Expert; Adrian Hope-Bailie, Coil|
(FTE %: 40%)
|Usual Meeting Schedule||
Face-to-face: 2-3 per year
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:
The Working Group has discussed, but not yet taken up formally, payment method specifications on the following 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.
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.
The following topics are out of scope for this Working Group.
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.
The deliverables of this group should enable parties involved in a payment transaction to meet any and all regulatory obligations.
|Specification||FPWD||Most Recent CR||PR||Rec|
|Payment Request API||
||October 2020||December 2020|
|Payment Method Identifiers||
||October 2020||December 2020|
|Payment Handler API||
||June 2020||January 2021||March 2021|
|Payment Method Manifest||
||June 2020||January 2021||March 2021|
|SRC Payment Method||March 2020||September 2020||January 2021||March 2021|
|Note: The group will document significant changes from this initial schedule on the group home page. See below for information about reference drafts.|
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. The Working Group is encouraged to engage collaboratively with the horizontal review groups throughout development of each specification. The Working Group is advised to seek review at least 3 months before first entering Candidate Recommendation and is encouraged to proactively notify the horizontal review groups when major changes occur in a specification following a review.
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.
This group primarily conducts its work on GitHub and the public mailing list email@example.com (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.
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.
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.
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 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 Charter||9 March 2018||31 December 2019||Deliverables under consideration since the previous charter are listed in section 1.2.|
|2020 Charter||19 December 2019||31 December 2021||Deliverables under consideration since the previous charter are listed in section 1.2.|
The following information related to the W3C Patent Policy is provided as a convenience.
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:26:21 $