Re: Overview of Payment App dev call Nov 14th, 2016 from Rouslan Solomakhin on 2016-11-18 (public-payments-wg@w3.org from November 2016)

From: Rouslan Solomakhin <rouslan@google.com>
Date: Fri, 18 Nov 2016 05:56:57 -0500
To: Anders Rundgren <anders.rundgren.net@gmail.com>
Cc: Web Payments Working Group <public-payments-wg@w3.org>, "Hackett, Conor" <Conor.Hackett@worldpay.com>, 임동우 <dw.im@samsung.com>
Message-ID: <CAMMzaWFea4Lzi1s3_5Rg0K6_HV1s4wAxwuSZFukfT0HAS2=TDQ@mail.gmail.com>

Some Android payment apps would like an extra level of protection by
manually checking website certificates against their own list of CAs
instead of trusting the OS or the browser.

On Nov 18, 2016 5:53 AM, "Anders Rundgren" <anders.rundgren.net@gmail.com>
wrote:

On 2016-11-16 14:18, Hackett, Conor wrote:
<snip>

·         Samsung has proposed several improvements to this spec that not
> yet in doc:
>
> o   Pass merchants certificate to the payment app
>

Could somebody elaborate a bit on this?  It sounds like a major (and
promising)
departure from Android intents.

Anders

Received on Friday, 18 November 2016 10:57:30 UTC