RE: A first draft of the future Web Payments Interest group is available for comments

Stephane,

I only have a couple of comments:
- include B2B use cases the scope
- clarify somewhere that "browser" is used to refer generically to web user-agent functionality that may be used in an actual web browser, a hybrid app, or an installed web app. The goal as noted below is that the web provides support for payments in all these environments, and not limited to a particular type of application or dependent upon its functionality (e.g. the browser "chrome").

I believe that with that change, the key points that were made in our position paper, and that I expressed in the workshop, can be addressed through the charter as-is:

- Almost as much as anything you can do on the web, payment is personal. W3C should ensure that users are able to make their own choices for relationships with providers of various web payment system components, and not be locked into a particular set of relationships just due to using a particular device, browser, or network. User choice, including the ability to choose who one trusts to represent them in payment UX, is essential.

- UX needs to address the entire lifecycle of user engagement with payment services and managing a virtual wallet, which may vary depending upon the use case. The act of payment (or reception) of funds is just one aspect to be considered. Analysis of use cases across each lifecycle stage should be used to uncover requirements for web APIs.

- To have the broadest applicability, web payment services need to be accessible to users of browsers, hybrid apps, and native web apps (e.g. installed apps executing in web-based devices or web runtimes). We should avoid the UX being dependent upon one type of web environment, e.g. while browsers may provide some UX features through their chrome and configuration, web payments should also work outside web browsers.

- Standards should address how components in a web payment system can interact via APIs, but not mandate a particular UI, rather set out as needed the expectations on UI capabilities that can be implemented in different ways.

- While transfer of funds is a natural first focus for web payment APIs, they should also be designed to consider transaction execution more generally, so that different things of value can be exchanged, e.g. bartered goods or service

Thanks,
Bryan Sullivan | Service Standards | AT&T

> On Thu, May 15, 2014 at 7:41 AM, Stephane Boyera <boyera@w3.org> wrote:
>> Dear All,
>>
>> Following-up on my last email, I've just published a first draft of the
>> future W3C Web Payments Interest Group (aka Web Payments Steering Group).
>> The document is available at
>> http://www.w3.org/2014/04/payments/webpayments_charter.html

>>
>> I've also just published short blog post to request feedback, see
>> http://www.w3.org/community/webpaymentsigcharter/2014/05/15/first-draft-of-future-web-payments-interest-group-charter-published/

>>
>> We need your help to move this forwards:
>> *All comments are welcome. You can answer this email, contact W3C team
>> privately or join the Community group dedicated to the charter development
>> (http://www.w3.org/community/webpaymentsigcharter/join ) to provide
>> contribution. We will be able to make progress if the work items and the
>> scope of this group is inline with your interest and expectations.
>>
>> *We need to increase our sphere of influence and involve more payment
>> industry actors. W3C is well connected with Web and technology actors, but
>> we are relatively new in the payment area. Please disseminate the charter in
>> your network, or let us know who you believe we should engage with to
>> discuss this charter first and then to work  on its implementation.
>>
>> Best
>> Stephane
>> --
>> Stephane Boyera        stephane@w3.org
>> W3C                +33 (0) 6 73 84 87 27
>> BP 93
>> F-06902 Sophia Antipolis Cedex,
>> France
>>

Received on Tuesday, 27 May 2014 14:20:07 UTC