- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Sun, 11 Oct 2015 08:42:40 +0200
- To: Web Payments CG <public-webpayments@w3.org>
After a few hours pf hacking I got second thoughts...My original idea https://cyberphone.github.io/openkeystore/resources/docs/webnfc--web2device-bridge.pdf making the client-side application interface *identical* for a "Wallet" called from a Web-page or invoked from NFC/BLE (via a Web-page or through a more traditional POS-interface), seems like a better use of my very limited development resources (=me). That is, the navigator.nativeConnect() API ( https://github.com/cyberphone/web2native-bridge#api ) will be complemented by a navigator.tapConnect() API where the proxy will be in the client (mobile) end. Anders On 2015-10-10 15:26, Anders Rundgren wrote: > Today, I started a project which has the goal making it possible for an Android-based "Wallet" to securely and conveniently interact > with [a slightly adapted version of] a Web-shop's "Checkout/Payment" page through the use of an NFC/BLE connection. > > That I probably can do this all by myself [sticking out my neck here...] is not because I'm some kind of über-wizard (I'm certainly not), > but due to the power of the Web2Native Bridge concept allowing you to test new ideas almost as quickly as polyfilling but running > on the native client. > > Anders > https://test.webpki.org/webpay-merchant >
Received on Sunday, 11 October 2015 06:43:13 UTC