--- a/latest/charters/payments-wg-charter.html Fri Jul 10 11:17:49 2015 +0200
+++ b/latest/charters/payments-wg-charter.html Sat Jul 11 21:50:20 2015 +0200
@@ -50,10 +50,8 @@
<h1 id="title">[DRAFT] Web Payments Working Group Charter</h1>
<p class="mission">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.
- <p>
- <b>Note</b>: For more information about roles involved in this payment flow (payer, payee, etc.), please see the
- <a href="http://www.w3.org/TR/2015/WD-web-payments-use-cases-20150416/#terminology">Web
- Payments Interest Group's glossary</a>.</p>
+ <p><b>Note</b>: For more information about roles involved in this payment flow (payer, payee, etc.), please see the
+ <a href="http://www.w3.org/TR/2015/WD-web-payments-use-cases-20150416/#terminology">Web Payments Interest Group's glossary</a>.</p>
<div class="noprint">
<p class="join">@@Join the Web Payments Working Group.</p>
</div>
@@ -89,7 +87,7 @@
</table>
<h2 id="goals">Goals</h2>
<p>Under this initial charter, the Working Group defines standards that ease integration of the payments ecosystem into the
- Web for a payment initiated from a Web site or Web application. Where practical the standards will be usable by native applications/apps.</p>
+ Web for a payment initiated by a Web application. Where practical the standards will be usable by native applications/apps.</p>
<p>We anticipate the following benefits of this work:</p>
<ul>
<li>Streamlined payment flow, which is expected to reduce the the percentage of transactions abandoned prior to completion ("shopping
@@ -108,14 +106,12 @@
<a href="http://www.w3.org/TR/web-payments-use-cases/#an-overview-of-the-payment-phases">Web Payments Use Cases</a>.</p>
<div class="scope">
<h2 id="scope">Scope</h2>
- <p>A payment, on the Web today, ordinarily starts on a payment page where the
- <b>payer</b>must manually select a payment scheme, manually select their own
- <b>payment instrument</b>for that
- <b>payment scheme,</b>manually capture the details of that instrument into the page (along with any other essential data such
- as a shipping address) and then submit this data back to the
- <b>payee.</b>The payment data briefly passes through the Web (from the payer's user agent to the payee's Website) on it's way
- to a payment processor. At that point, much of the communication to complete a payment takes place among banks, card networks,
- and other parties in the payment ecosystem typically outside of the Web.</p>
+ <p>A payment, on the Web today, ordinarily starts on a payment page where the <strong>payer</strong> must manually select a payment
+ scheme, manually select their own <strong>payment instrument</strong> for that payment scheme, manually capture the details
+ of that instrument into the page (along with any other essential data such as a shipping address) and then submit this data
+ back to the <strong>payee.</strong> The payment data briefly passes through the Web (from the payer's user agent to the payee's
+ Website) on it's way to a payment processor. At that point, much of the communication to complete a payment takes place among banks,
+ card networks, and other parties in the payment ecosystem typically outside of the Web.</p>
<p>In an effort to improve upon this process, various parties have innovated ways to make the payment flow easier, for example
by caching payment instrument information in browsers, registering users on eCommerce websites to facilitate re-use of customer
data and/or payment credentials, and even developing new payment schemes. Unfortunately, these efforts all suffer from a
@@ -125,19 +121,24 @@
payment systems (existing and future), and encourage greater automation of steps in a typical payment. The interfaces between
the payment schemes and the Web are via the user agent and the Web application, therefore the scope of the initial charter
is focused on the interactions between these two components and the external actors that will interface directly with them.</p>
+ <p>The group will focus primarily on standardisation of a set of messages and a message flow for the initiation. confirmation and
+ completion of a payment. By focusing on the message format and flow the group leaves open the standardisation of the delivery
+ mechanism for these messages as this will vary depedning on the use case and technology stack. The group will aim to standardise
+ the delivery mechanism for common cenarios such as WebIDL APIs for the use cases where the messages are proxied between payer and
+ payee via the browser or Web APIs where the messages are exchanged directly over the Web between two online entities in the
+ classic REST pattern.</p>
<p>
<b>Note:</b>W3C expects to a wider variety of of eCommerce scenarios over time, including digital receipts; loyalty programs
and coupons; peer-to-peer payments; and harmonization of user experience in-browser, in-app, and in-store. For more information,
- see the
- <a href="http://www.w3.org/TR/web-payments-use-cases/">Payments Use Cases</a>published by the W3C Web Payments Interest Group.</p>
+ see the <a href="http://www.w3.org/TR/web-payments-use-cases/">Payments Use Cases</a>published by the W3C Web Payments Interest
+ Group.</p>
<h3 id="wallets">Wallets</h3>
<p>The standards from this group may be implemented in a variety of ways, including as stand-alone applications, in the cloud,
or within user agents such as browsers. Some of the functionality provided by the standards from this group can be found
in various Web services today, as well as in digital wallets. Because the "digital wallet" concept can be useful as a shorthand,
but means different things to different audiences, this charter includes a definition to clarify the intent of this group.
- In this charter we define a
- <b>wallet</b>as a software service, providing similar functions in the digital world to those provided by a physical wallet,
- namely:</p>
+ In this charter we define a <strong>wallet</strong>as a software service, providing similar functions in the digital world to
+ those provided by a physical wallet, namely:</p>
<ul>
<li>It holds payment instruments registered by the wallet owner;</li>
<li>It supports certain payment schemes and enables the payer to use registered payment instruments to execute a payment in