W3C home > Mailing lists > Public > public-webpayments@w3.org > March 2014

HA: VOTE: Adopt Web Commerce API as work item?

From: . <jonny@yamoney.ru>
Date: Sat, 8 Mar 2014 14:29:18 +0000
To: Manu Sporny <msporny@digitalbazaar.com>, Web Payments <public-webpayments@w3.org>
CC: Charles McCathie Nevile <chaals@yandex-team.ru>
Message-ID: <CCED300B28C79C429F8DFB4B63D9300501056CFDF6@Ivan-1mx10.yamoney.ru>
We have read a draft for Web Commerce API 1.0. Generally we agree thatsuch document must be a part of a standard. However, there are somequestions about Draft contents:

1. It is mentioned in 1.2 that vendor is a seller of digital goods orservices. However, most of the Draft is suitable formaterial goods as well. Why it is stated that only digital goods can besold with this API?

2. It is not clear for me from Web Commerce API docs who is responsiblefor the Vendor's account data storage (or a set of accounts data storage) -I mean the account to which the payment will be transferred. Is the accountout of scope of this Draft? (Maybe this problem can be solved withWeb Identity, however, it does not contain an information about accounts at the moment).

Evgeny Vinogradov
From: Manu Sporny [msporny@digitalbazaar.com]
Sent: 23 February 2014 6:21
To: Web Payments
Subject VOTE: Adopt Web Commerce API as work item?

This vote is being held to determine whether or not the Web Commerce API
should be included as a work item for the Web Payments Community Group.
Any Web Payments Community Group member can vote and will have until
March 8th to submit their vote. The decision will be made by a simple
majority (>50%) vote. Here's the link to the poll:



The Web Commerce API is a proposal to standardize the payment request
and a digital receipt format. The technology is designed such that
closed payment solutions (like PayPal, Google Wallet, etc.) and more
open payment solutions (Bitcoin, Ripple, PaySwarm) can use the same
mechanism to initiate and complete a payment.

You can view the discussion that led to this vote here:


This API enables a web application to initiate payment for a product or
service by calling a navigator.transact.pay() method. The implementation
of this feature is expected to be provided by a JavaScript polyfill at
first, and if deployment is successful, native browser implementations
will eventually surface to enhance usability and transaction security.

Specifically, the proposal would standardize the payment request format
(payment initiation) and the digital receipt format (proof of purchase).


-- manu

Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
blog: The Worlds First Web Payments Workshop
Received on Monday, 10 March 2014 10:23:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:07:28 UTC