- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Sun, 1 May 2016 21:58:25 -0400
- To: Web Payments Working Group <public-payments-wg@w3.org>
Hi all, Dave Longley and I spent the weekend and implemented a basic payment app, payment mediator, and merchant payment application for the Web Payments HTTP API. You can try the demo here: http://http-mediator-demo.web-payments.io/ There is very basic support for: Payment App * registration * payment request submission * payment response generation * basic card responses Merchant * access control on resource requiring payment * payment request generation * payment response processing Payment Mediator * registration of payment apps * routing payment request to payment app * routing payment response to merchant The implementations don't currently (but we plan to): * do authentication of any kind * support the browser API * store state * do error checking or even have failure paths The purpose of this experiment was to: * test the implementability of the HTTP API and Core Messages (good news! - no surprises found) * provide a space where we could easily iterate on ideas around payment apps, payment mediators, and merchant software * create a demo for folks to see all the pieces in action There is very basic documentation for each component on its respective website: Payment App: http://payment-app-demo.web-payments.io/ Mediator : http://http-mediator-demo.web-payments.io/ Merchant : http://merchant-demo.web-payments.io/ Source code can be found here: https://github.com/digitalbazaar/payment-app-demo.web-payments.io https://github.com/digitalbazaar/http-mediator-demo.web-payments.io https://github.com/digitalbazaar/merchant-demo.web-payments.io -- manu -- Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc. JSON-LD Best Practice: Context Caching https://manu.sporny.org/2016/json-ld-context-caching/
Received on Monday, 2 May 2016 01:58:52 UTC