Automotive Web Payments Task Force

<Ian> https://github.com/w3c/automotive-pay/wiki/Agenda-20171026

Ian: today we should go over TPAC plans and use cases

<Ian> scribe: Ted

<Ian> previous minutes => https://www.w3.org/2017/10/19-autopay-minutes.html

Rodrigo: I read the wiki explainer page, anyone raise any red flags?

Ian: no, we did delve a bit into toll road scenario
... either you are debiting an account you already funded (stored with regional provider, eg Maine DOT for EZpass) or you are billed
... pay at the pump and parking seem like better fits

<Ian> IJ: Sounded to me like tolls less interested given how funds are collected today (either billed or pre-funded account)

Rodrigo: today the UI component can capture the proper credentials and send to the merchant

<Ian> Rodrigo: But one way to think about this is get previously stored credentials

<Ian> ted: We had someone from Jaguar/Landrover explain today's toll collection scenarios

<Ian> ...either you have an account or you are billed (based on your license plate)

<Ian> .....but another option is for the car to recognize the toll beacon and to do a push payment (before you are invoiced)

<Ian> ...another topic is reconciliation across different DOTs

<Ian> ...so you might address this by paying directly to a payment provider

[agree we should focus on other use cases first. tolls are complicated by existing infrastructure and practices but web payments is not necessarily ruled out]

Rodrigo: let's focus on the primary use cases first. the UI component would be different, Ian can say if we can evolve that piece to be more flexible for the car

Ian: given how our F2F meeting is approaching, at least for now we should focus on the pay at the pump scenario

+1 for fueling being primary use case

<Ian> https://github.com/w3c/automotive-pay/wiki/PayAtPumpExplainer

Ian: I discussed this a bit at Money 2020 this week
... it is a simplistic representation of the world where hardware is needed to initiate the payments
... David and I have been talking with FirstData about their implementation
... we should seek input from auto on the viability of this scenario

Rodrigo: agree, should we have some required reading or other primers in preparation for the meeting

<Ian> ted: Adam (from Jaguar) will not be able to attend

<Ian> ...I do expect some other people who are in the group to attend, however.

<Ian> ...makes sense to share what we have in advance

<Ian> Ted: Web can help with some security challenges

<Ian> ...eg., using user location as a way to get the user to a relevant web page

<Ian> rodrigo: Let's prep people so that they come prepared to the FTF meeting

<Ian> IJ: I'd like to articulate some questions for discussion at the face-to-face meeting

<Ian> ...and get questions BEFORE the face-to-face meeting that we can address in Burlingame

Ian: we should encourage more review of these materials and respondes in advance for a more fruitful f2f discussions

David: I don't think John is coming since IFSF has a meeting in France the following week
... I will ask him about upcoming infrastructure considerations

<Ian> dezell: People are using RFID

David: many are starting to use NFC and RFID

<Ian> Ted: Also DSRC

<Ian> "DSRC (Dedicated Short Range Communications) is a two-way short- to- medium-range wireless communications capability that permits very high data transmission critical in communications-based active safety applications."

<Ian> dezell: there is a relationship between card schemes and oil companies that also needs to be taken into consideration

[DSRC is being considered for V2x space, in flux but standards work at SAE and aligns with NHTSA]

<Ian> Email template:

<Ian> * We are meeting 9 Nov

<Ian> * Would love feedback and questions about this use case description

<Ian> * Also any relevant experience you have on similar systems and constraints or considerations you discovered in doing so

Ian: if people here have specific individuals we want to seek input from we should send them emails in advance
... it was great to hear what FirstData did with regulatory considerations, eg requiring the car at rest

[I may be attending a US DOT/DOE/UK DfT meeting in DC shortly after TPAC on EV infrastructure requirements]

Ian: please cc Ted and myself so we avoid overlap and are generally aware. we can collect and document responses

<Ian> IJ: We should include rationale in the email (e.g., why the web can help reduce friction)

<Ian> Ted: Let people know that they should tell us how we can share their comments (e.g., attributed or non-attributed)

<Ian> Rodrigo: Ted and Ian can write the auto and IG groups

<Ian> ACTION: Ian to send email template to the autopay list today [recorded in http://www.w3.org/2017/10/26-autopay-minutes.html#action01]

Face-to-face meeting

<Ian> https://github.com/w3c/automotive-pay/wiki/Agenda-20171109

[I am meeting with US DOT on Monday on several topics, different focus than payments but will seek appropriate contacts]

Ian: Part of the F2F agenda is about attracting observers and W3C participants from other organizations to get involved
... we want incubators, people to experiment in this space

Rodrigo: do you want me to put this together in a powerpoint

<Ian> ACTION: Rodrigo to put together deck for TPAC to walk through charter, use case [recorded in http://www.w3.org/2017/10/26-autopay-minutes.html#action02]

Ian: that would be helpful
... there may be additional flows for this use case others come up with

Rodrigo: what was your reaction to the previous conversation on flows?

Ian: I see it as incremental improvements especially if we want to rely on hardware that isn't rolled out universally
... some parts were not a great fit from the UX perspective
... we should focus on leveraging our existing payments standards work where possible
... we didn't get some of the other use cases
... there are other topics in our charter besides use cases like distractability. those are more challenges and have not covered

[distractability only a concern for use cases when vehicle is in motion]

Rodrigo: should we iterate over the use cases, summary of focuses so far, challenges and see what their challenges are

Ian: identifying similar use cases and how they differ seems useful for me and add to the agenda
... you mentioned identifying the actors and roles which is somewhat done in the flow diagrams
... I would be happy to explain in detail who the different parties are

<Ian> +1 to understanding roles and business motivations

Rodrigo: the goal is really the flow of the use case, with pay of the pump being a focus for sure
... we want a clear consisent understanding since some are coming from different industry perspecitives

Next meeting

<Ian> TPAC

<Ian> (no TF meeting on 2 Oct)

[no call next week, Ian, Ted and Rodrigo to meet beforehand]

<Zakim> ted, you wanted to comment on incremental and flows and to comment on time allotment

<Ian> ted; We can also provide for remote attendance

<Ian> summary next steps:

<Ian> * Ian to send out minutes from today's call

<Ian> ...and announce next meeting is at TPAC

<Ian> * Ian to draft email template to get feedback on pay at the pump explainer

<Ian> * Rodrigo to draft slides for presentation at TPAC of task force scope + explainer

<Ian> * Ted and Ian to write to the respective groups to get feedback in advance

<Ian> * Other people will ping other people with the email template, cc Ted and Ian