Note: This draft has been superseded by the October 2015 draft charter.
The mission of the Web Payments Working Group is to make payments easier and more secure on the Web, through incremental improvements to Web infrastructure that support and facilitate payments.
Fragmentation of the payment landscape is limiting the full potential of the Web, including lack of standards in areas such as:
The standards from this Working Group will reduce some areas of fragmentation, producing benefits such as:
For more background information about this group, please see the Web Payments Working Group Charter FAQ. For more information about Web Payments activities beyond the scope of this charter, see the Web Payments Interest Group description below.
|End date||31 December 2017|
|Confidentiality||Proceedings are public|
|Initial Chairs||Nick Telford-Reed, Worldpay, Co-Chairs TBD|
|Initial Team Contacts
(FTE %: 50%)
|Doug Schepers, Ian Jacobs|
|Usual Meeting Schedule||Teleconferences: Weekly
Face-to-face: 2-3 per year
Under this charter, the Working Group defines standards that ease integration of the payments ecosystem into the Web for a payment initiated within a Web application.
The Working Group will standardize a set of messages and a message flow for the initiation, confirmation, and completion of a payment. Deliverables from this group will increase interoperability between payer and payee systems (for existing and future digital payment schemes), and encourage greater automation of the steps in a typical payment.
This group is chartered to standardize programming interfaces; not user interfaces. This group will not define a new digital payment scheme.
The scope of work supports the following elements of a basic purchase triggered by payment initiation through a Web application. These standards define a high-level message flow for a payment from payer to payee either in the form of a credit push (payer initiated) or a debit pull (payee initiated) payment, and can be used to facilitate a payment from any digital payment scheme. They involve:
The group will also address exceptions that may occur during these steps, including payment authorization failure, lack of available digital wallet service, and lack of suitable registered digital payment instruments.
This Working Group intends to create a standard programming interface from the Web to a payer's digital wallet so that someone with a conforming digital wallet can seamlessly make payments with a conforming application running in a conforming user agent. Because the "digital wallet" concept means different things to different audiences this charter includes the above definition to clarify the intent of this group.
This group is not developing standards for loyalty schemes and coupons, digital receipts, digital credentials, tickets, and location services. Future W3C activities may seek to increase interoperability of these or other additional digital wallet capabilities.
The group may define APIs that will also be used outside of a user agent context, such as between Web services, or from within a native application (where the browser is not the proxy between digital wallet and payee application).
In the design of these standards, the Working Group will not assume that each user has only one digital wallet. In this charter, the phrase "the payer's digital wallet" is shorthand for "the payer's digital wallet(s)" as the payer may have multiple digital wallets.
The Working Group may consider the use case where an aggregation service acts as a more sophisticated digital wallet service or provides a wider choice of payment solutions to the payer. For example, the aggregator service might combine the functionality of multiple digital wallet services, or apply more complex algorithms to discover and collect the set of digital payment instruments available to the payer.
Security is obviously critical in payments.
For the APIs defined by this group, a key consideration is the ability to prove message integrity and authentication of all message originators. This group will work with the organizations listed in the liaisons section of the charter to help ensure API security.
There are other aspects of security (e.g., authentication of payer identity) that this group will leave to the digital payment schemes. This group will not define authentication standards (e.g., hardware-based solutions in securing transactions, or authenticating users via biometry or other mechanisms) but should be aware of industry developments to help ensure compatibility with the flows defined by this group.
In addition, W3C is developing additional security-related specifications in other groups that may be adopted in digital payment schemes. This group will follow that work to help ensure compatibility with the payment flow standards described in this charter.
Protection of the privacy of all participants in a payment is essential 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 as part of the payment process unless required by operational, 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 public facing API should guard against the unwanted leakage of such data through exploitation of the API.
Digital payment schemes define how various parties meet relevant regulatory obligations. The deliverables of this group should not prevent parties from meeting those obligations.
Web Payments APIs will seek to increase interoperability for the following:
It will include standard request and response messages for:
It will specify the delivery mechanism for these messages in at least the following scenarios:
The group will seek interoperability between two user agents and two services that enable payers to use digital payment instruments.
|Note: The group will document significant changes from this initial schedule on the group home page.|
|Web Payments APIs||March 2016||November 2016||September 2017||November 2017|
A very large proportion of payments on the Web are conducted using payment cards from one of the global card schemes. The group should attempt to define a standardized specialization of the payment flow specifically for payment cards.
A generic card payment Recommendation could:
This charter does not include a deliverable for a standard mechanism to discover —via the payer's digital wallet— available digital payment instruments. However, the Working Group may document good practices and recommend algorithms for the discovery of payer digital payment instruments.
The Web Payments Working Group anticipates developing test suites for Recommendation-track specifications it develops.
The Web Payments Interest Group acts as the overall coordinator at W3C of a vision for Web Payments, by gathering Web Payments Use Cases, engaging in liaisons with other payments standards bodies, and developing a high-level architecture. The group intends to explore more eCommerce scenarios than are represented in the current Working Group charter, such as digital receipts; loyalty programs and coupons; peer-to-peer payments; and harmonization of user experience in-browser, in-app, and in-store.
From time to time, the Interest Group will seek feedback from the Working Group on its evolving vision, and share information about the evolution of the Web payments technology landscape. The Interest Group may also propose new Working Groups to cover topics such as identity, credentials and commerce (including invoicing, receipts, loyalty programs, coupons, discounts, and offers). The Web Payments Interest Group also expects to provide technical input to this and other relevant W3C Working Groups, based on a detailed analysis of the relevant Web Payments Use Cases.
This group will also collaborate with future W3C Working Groups developing authentication protocols.
In addition, for the Card Payments specification, the Working Group will need to collaborate with the administrators of existing global card schemes.
To be successful, the Web Payments Working Group is expected to have 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 the public mailing list firstname.lastname@example.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.
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 (5 February 2004 Version). 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 charter for the Web Payments Working Group has been created according to section 6.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.
$Date: 2015/10/08 18:01:18 $