W3C home > Mailing lists > Public > public-payments-wg@w3.org > May 2016

Re: Updates to Payment Apps wiki page

From: Ian Jacobs <ij@w3.org>
Date: Tue, 10 May 2016 09:51:40 -0500
Cc: Adrian Hope-Bailie <adrian@hopebailie.com>, Payments WG <public-payments-wg@w3.org>
Message-Id: <3C3A2B98-8139-4D70-A975-3D4A32398764@w3.org>
To: David Ezell <David_E3@VERIFONE.com>

> On May 10, 2016, at 8:54 AM, David Ezell <David_E3@VERIFONE.com> wrote:
> 
> Thanks Adrian and Ian:
> 
> FWIW, as a WG member (representing NACS) I’m in full agreement with Adrian’s position below:
>>        My assertion is that we should focus on defining how a browser passes a payment request over the Web
>>        (irrespective of how the app that receives it is implemented). This implies that we need a platform agnostic
>>        mechanism like HTTP.
> 
> My concern is about the logistics of a “v1” vs. “v2”:
> * does "v1" mean FPWD of some subset of documents, or CR, Rec, etc.?
> * is there an expected timeframe?
> 
> If you believe that "v2" (if that's where HTTP API goes) is essential, knowing if it's expected in 2 months or 2 years is helpful in giving feedback.
> 
> I'll look for an open thread…

Hi David,

I think the answer today is “we don’t know, we need to discuss further”

Ian
--
Ian Jacobs <ij@w3.org>      http://www.w3.org/People/Jacobs
Tel:                       +1 718 260 9447




Received on Tuesday, 10 May 2016 14:51:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 10 May 2016 14:51:46 UTC