- From: Evan Schwartz <evan@ripple.com>
- Date: Thu, 18 Jun 2015 14:31:16 -0400
- To: Web Payments IG <public-webpayments-ig@w3.org>
- Message-ID: <CAONA2jXGiOWYV+E5CaKYeBSqK2aNSTYev90JhyzV8XKkMoZ_=A@mail.gmail.com>
Here is a rough prototype for what a Web Payment Request standard could look like. This is a spec that the browsers or user agents would implement, and websites could call. Importantly it is a standard that could support all types of payment schemes without the schemes having to change or implement anything. https://github.com/emschwartz/web-payment-request-chrome (It is implemented as a Chrome extension now but ideally some of that functionality would be handled by the web browser natively) This is a small subset of what the IG has been discussing but it is a very simple spec that could address some of the problems the group is interested in solving. Its scope is intentionally small and restricted to a retail use case on the Web. Comments, issues, questions, and pull requests are very welcome! Looking forward to hearing your feedback, Evan PS This was the written proposal that underlies the thinking that went into this prototype: https://docs.google.com/document/d/10T3z25zzBoorOaOUuQiJCu7gZXQeSvUSqYpJmsqrE6Y -- Evan Schwartz | Software Architect | Ripple Labs [image: ripple.com] <http://ripple.com>
Received on Thursday, 18 June 2015 18:32:11 UTC