WPIG Vision Task Force

<adamlake> Hello. I am trying to connect via cell and but the number/code I have is not working. If someone could give me a number/access code to call in I would appreciate it.

Vision page https://www.w3.org/Payments/IG/wiki/Vision2017

Automotive (Ted)

https://www.w3.org/2017/Talks/tg-autopay/

<ted> Connected Vehicle Payments Proposal

<scribe> scribe: Ian

(IJ note to self: As we prepare for presentations to the broader IG, think about particular questions to draw to their attention)

[Ted on family usage of car and kids paying their way!]

[Slide 7: Shared vehicle solutions]

[9 incentives for change]

Ted: Vehicle offers more opportunities for multi-factor-auth

[10: Consumer benefits]

[11: Market scope

Ted: One use case is "lower cost of smart parking by avoiding new infrastructure costs"
... that could accelerate revenue growth from smart parking
... Samsung is perhaps biggest Tier 1

IJ: What about Google and Apple?

Ted: Sure, let's add them

dezell: NACS and Conexxus also have a mobile effort going that's useful for automotive

see => http://www.nacsonline.com/Media/Press_Releases/2016/Pages/PR092816.aspx#.WJ3O1hCY6r0

Jeff: Compelling story, Ted.
... would like some more context and focus
... growing set of solutions on slide 11
... and we have web payments at W3C that's working on a tiny slice of payments
... the context question is: what do we think automotive pay at W3C looks like?
... is it it's own standalone thing? Does it relate to existing payments work?
... how does what you envision relate to existing efforts?
... so would like more context about (a) how relates to W3C (b) relation to existing work (c) focus on what we should do and not do

<dezell> +1 to comfort

<todd_a> +1

<manu> +1, we'll have to meet next week.

<mark_tiggas> +1

<adamlake> +1

<jeff> [/me thinks we should go through all of them quickly today AND try to meet next week]

[13: Desired participants]

Ted: Gov participation may be difficult, but might get some good local contacts

<manu> Ian: I think it's important to make the point that there is relevant work going on at W3C right now... NFC CG, Geolocation API, Authentication, PaymentRequest, etc.

IJ: Prongs of why w3c:

- we are doing relevant work already

- web is ubiquitous

- web is for integration across diverse ecosystems

Ted: I think working with IFSF will be very helpful

dezell: NACS and Conexxus have been involved in this for a while. There is also an interesting relationship between distraction on the road and accessibility; that is another connection to w3c existing work.
... also, key issues to be considering include (1) offline payment (2) bluetooth/nfc (2) new payment flows such as rentals
... some additional flows of interest in fueling (1) site-level authentication and (2) above site authentication

Digital Receipts (DavidE)

<dezell> https://www.w3.org/Payments/IG/wiki/Vision2017#Digital_Receipts

[David walks through the wiki]

dezell: The way that it works today is that there is no standardized receipt; it's per merchant. There is no way to reuse it, and there's no way to include in a wallet.

IJ: Please after each story indicate what the limitations are today for fulfilling the best user experience in that story

dezell: Today in retail industry, there is not cross-industry consistency
... there is no customer receipt format in *wide use*
... There are regulatory interests, but also privacy issues
... another use case is *validating* receipts
... Retailers want to be able to audit purchases/sales in a consistent way
... We may want a receipt storage API

<Zakim> manu, you wanted to mention GS1 SmartSearch standard... related to Receipts - http://www.gs1.org/gs1-smartsearch

Manu: I assed GS1 SmartSearch to the wiki
... SmartSearch is a way to express product descriptions, to find them more easily through search engines
... that mechanism could be reused
... I this that GS1 has done much of the work, and it's deployed, and compatible with other w3c tech

<Zakim> Ian, you wanted to ask why browsers need to know about receipts

<manu> Ian: My thoughts wrt. Digital Receipts - what is the browser role in this?

<manu> Ian: On the other hand, wrt. PaymentRequest API... send a payment request get a payment response.

<manu> Ian: Providing mechants with a way to send a digital receipt via the browser might be useful. We can standardize the way digital receipts get back to payment apps.

<manu> Ian: For the other parts of digital receipts, we are not the first party I'd go to for digital receipt formats, but if you let us know why those efforts are not succeeding, that might be an interesting discussion to have. wrt. storage, what are the parts of the Web Platform that need to be improved?

<manu> Ian: We need to understand what W3C should focus on.

dezell: the only thing I"ll say about storage is that it was an example
... but it may also be display

Next meeting

<manu> Ian: I tend to like things that are a sensible next piece based on players in the communityh that are already active... we may have a good chance of success taking advantage of momentum.

9am ET on 17 Feb

We will continue with the proposals.