- From: Dave Longley <dlongley@digitalbazaar.com>
- Date: Tue, 10 May 2016 12:17:22 -0400
- To: Adam Roach <abr@mozilla.com>, Tommy Thorsen <tommyt@opera.com>
- Cc: Ian Jacobs <ij@w3.org>, Adrian Bateman <adrianba@microsoft.com>, Web Payments Working Group <public-payments-wg@w3.org>
On 05/10/2016 10:29 AM, Adam Roach wrote:
> On 5/10/16 09:23, Dave Longley wrote:
>> If we want to make it easy for people to leverage their browser to
>> provide information like their shipping address, another option is
>> to expose an API for that type of information that Web
>> applications, such as a Payment App, could use to request it.
>
> Are you thinking of something like
> <https://html.spec.whatwg.org/multipage/forms.html#autofill>? Or is
> there some other approach you have in mind?
There are a lot of different ways it could work. Some made various
proposals here more tightly integrated with payments here:
https://github.com/w3c/browser-payment-api/pull/65
Though I was talking more generally about being able to request
structured data from the browser, for example:
navigator.customerData.get({
query: {type: 'PostalAddress'}
}).then(...);
In any case, I'm not proposing that we do this, and I honestly think
we're treading close to being out of scope. I was just indicating that
if we start seeing a laundry list of items to request from the payer in
the PaymentOptions, then I think we're probably doing it wrong.
Especially if those things we're requesting are part of the payment
method, which falls into the ___domain of Payment Apps, not Payment Mediators.
That being said -- this thread is about user consent, so I don't want to
wander off topic.
--
Dave Longley
CTO
Digital Bazaar, Inc.
http://digitalbazaar.com
Received on Tuesday, 10 May 2016 16:20:01 UTC