- From: Anders Rundgren via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Mar 2017 16:03:57 +0000
- To: public-web-nfc@w3.org
@kenchris I'm still not clear what your proposal is with respect to the URL mentioned in the initial posting by @zolkis Since the Hardware Based Security Services CG (initiated by Intel) didn't pan out, secure payments seem to continue relying on "Apps" which is why I'm suggesting a charter revision for a possible next phase. The Web Payment WG (technically lead by Google) have had no "philosophical" problems with supporting native Apps including Android Pay. The suggestion in a nutshell is allow Web NFC+ creating a paired BLE connection between a tapping device and the NFC-hosting Web page, including offering some kind of invocation attributes so that only specific Apps are started. In this scenario it is rather the App and/or Mobile OS that is the gatekeeper which means that the Web page security context must be available as well. http://www.europeanpaymentscouncil.eu/index.cfm/knowledge-bank/epc-documents/epc-white-paper-on-mobile-payments-version-50/epc492-09-v50-white-paper-mobile-payments-edition-2017/ "For other mobile proximity payments (i.e. non-NFC based), the lack of standardization in the usage of the various proximity technologies (e.g., QR codes, BLE, etc.) is resulting in a very fragmented approach throughout Europe, and even at domestic level" Actually even NFC payments are quite limited because they are currently based on card operations which fits squarely in mobile phones which are much more advanced than cards (like having a UI). -- GitHub Notification of comment by cyberphone Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/105#issuecomment-288448643 using your GitHub account
Received on Wednesday, 22 March 2017 16:04:05 UTC