W3C Web Payments Vision Meeting 2017

Connected Vehicle Payments

Some of the general types of payments in automotive space

• Fuel/charging
• Tolls and Usage
• Parking
• Services
• Entertainment

Connected Vehicle Payment Problems

Enabling payments from Connected Vehicles introduces a number of unique problems.

• Intermittent Connectivity
• Distractibility
• Shared Vehicles

Intermittent Connectivity

• Sporadic cellular coverage
• Potential remote location (off network) payment required
  • provide identifying information and promise to pay
  • venue requesting payment could offer wifi

Distractibility

• All driver interactions need to be minimalistic for safety
• Not a concern when parking, fueling/charging and other transactions when stationary
• Avoid confirmation from driver when car is in motion
  • example toll at 70mph
  • profile parameters to limit type and amount of unattended transactions
  • provide unobtrusive alert
  • voice or no confirmation

Shared Vehicles

Unlike laptops and smartphones, cars are not always used by a single individual

Fleet management

Rentals

Ridesharing

Emerging usage instead of vehicle ownership models

Borrowing friend's car

Personal vehicle expenses on a business trip

Shared Vehicle Solutions

Early thoughts on solving 1:many (vehicle:drivers) relationships

• Driver or individual incurring trip travel costs registers smartphone with vehicle
  • payment profile selected and stored on vehicle for duration of trip
  • payment requests redirected or proxied to phone
  • app from phone runs directly on vehicle, eg SDLink MirrorLink, Android Auto, Apple Carplay

Primary stakeholders

• Auto Manufacturers
• Tier 1s
• Payment processors
• Fuel and service companies
• Telcos
• State/Province and Municipal Governments

Incentives for change

• Reduce Traffic Congestion by removing need to stop and pay (tolls)
• Reduce service station fraud
• Revenue potential from large existing and emerging markets
• Increase percent of vehicles able to pay electronic tolls
• Transaction fee income
• Ability to continue consumer relation after initial vehicle purchase

Benefits for consumer

• Enable automatic (robotic) fueling/charging without leaving the vehicle
• Expense accounting
• Save time and cost*
• Manage loyalty rewards programs
  combine with location based services, vehicle data (eg fuel level) and navigation

*Electronic tolls are often offered at a discount to encourage adoption, expect similar for other types of transactions

Market Scope

• There will be an estimated 220 million connected cars by 2020
• $1.5 Billion Smart Parking revenue in next 10 years
• Fuel > $1 trillion*
• unable to find number for Global Tolls and Usage revenue
• Other Services - oil changes, car washes, valet

Efforts

Some of the existing efforts

Visa	IFSF*	Alibaba*
NACS* and Conexxus	FirstData	Jaguar Land Rover*	Audi*
SAP* and Samsung*	Accenture	Ford
Honda	Apple*	Google*

*Existing W3C Members

Desired participants

• Participants from W3C Web Payments Interest Group and Automotive WebPlatform Business Group
• Other W3C Members not involved yet in either activity
• Organizations already working on specific instead of general efforts
• Payment Processors
• Fuel and service companies
• State/Provice and Municipal Governments
• OEMs and Tier 1s

Why W3C?

W3C is positioned well to succeed in delivering solutions based on its existing Web Payments and Automotive Standards development. A unified, interoperable solution would be preferential to unique efforts.

Relevant Work at W3C

• Vehicle Information Service from W3C Automotive Working Group
• Location Based Services in W3C Automotive Business Group
• Near Field Communication Community Group
• Web Accessibility Initiative for possible Distractability concerns
• Speech API Community Group
• WebAppSec
• Blockchain Digital Assets Community Group
• Web of Things
• See also related groups list on Payments page

Next steps

• Present Web Payments to Automotive WebPlatform BG
• Propose plan on how to proceed to Web Payments IG at their F2F
• Set goal for minimum number of participants to begin work
• Form a joint Task Force
• Identify and invite stakeholders
• Launch Task Force
• Create use cases for vehicle payment situations

Next steps continued

• Identify solutions for problems and determine whether they belong in Payments, Auto or other purview
• Conduct gap analysis between use cases and Web Payments specs
• Submit feature enhancement requests to Web Platform WG
• Recharter Auto WG for any automotive centric specification work needed for payments

See Also

• Automotive Payments Task Force description
• Minutes from Liaison meeting between W3C Web Payments and Automotive activities
• W3C Web Payments Vision TF 2017
• Kevin Gavigan JLR presentation
• 2017-02-10 Minutes for this presentation