W3C home > Mailing lists > Public > public-hb-secure-services@w3.org > June 2016

Apple's take on Hardware Security for Web Payments

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Fri, 17 Jun 2016 08:47:46 +0200
To: public-hb-secure-services@w3.org, Web Payments IG <public-webpayments-ig@w3.org>
Message-ID: <a4a4ebf3-8dbd-df6d-22bf-83238b898f12@gmail.com>
As an avid Web user since 20 years back I have always wondered when chip-cards would also become usable for on-line payments.  It was somewhat surprising that it was Apple who finally pioneered this although their chip-card is a virtualized multi-card scheme running in a "Secure Enclave" (Apple terminology) which is a part of the main CPU.

Anyway, the stumbling block never was smart card middleware as some people have suggested.  The core problem is rather that since there's no such thing as "Trusted Web Application", you obviously need a "shield" [1] between the untrusted open Web and the "chip-card".   However, Apple didn't have to create anything special here since they already had the trusted application; the Apple Pay "App".

Although slightly simplified, the only thing left was an interface to the Apple Pay App:

https://github.com/w3c/browser-payment-api/issues/50#issuecomment-226397124

Anders

1] Merchants do not have any a priori relation to customers' chip-cards so GlobalPlatform-like access control schemes doesn't apply here.  In addition, things like PINs shouldn't be dealt with by external parties which is why certified payment terminals are mandatory in physical shops: https://en.wikipedia.org/wiki/Payment_terminal
Received on Friday, 17 June 2016 06:48:19 UTC

This archive was generated by hypermail 2.3.1 : Friday, 17 June 2016 06:48:19 UTC