- 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>
We have read a draft for Web Commerce API 1.0. Generally we agree thatšsuch document must be a part of a standard. However, there are somešquestions about Draft contents: 1. It is mentioned in 1.2 that vendor is a seller of digital goods oršservices. However, most of the Draft is suitable foršmaterial goods as well. Why it is stated that only digital goods can bešsold with this API? 2. It is not clear for me from Web Commerce API docs who is responsiblešfor 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 accountšout of scope of this Draft? (Maybe this problem can be solved withšWeb Identity, however, it does not contain an information about accounts at the moment). Evgeny Vinogradov Yandex ________________________________________ 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: http://www.addpoll.com/msporny/survey/adopt-web-commerce-api ------------------------------------------------------------------- Background ------------------------------------------------------------------- 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: https://web-payments.org/minutes/2014-02-19/#topic-4 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). https://web-payments.org/specs/source/web-commerce-api/ -- manu -- Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc. blog: The Worlds First Web Payments Workshop http://www.w3.org/2013/10/payments/
Received on Monday, 10 March 2014 10:23:44 UTC