Previous Work Done by the IVP SIG
Welcome to the COVESA In Vehicle Payments Birds of a Feather!
Monthly Meeting: Third Thursday of every Month, 9-10am PT, 12-1pm ET, 6-7pm CET (Zoom Link) (Subscribe to Community Calendar to stay up to date)
Slack: Join COVESA Community Slack Workspace (https://covesacommunity.slack.com) - Channel: in-vehicle-payments
Antitrust
Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws. We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.
Open and Royalty-Free
Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.
Recap and discussion on problem statements to be tackled within this group
Proposal 1: Standard for OEM and Third-Party Integration
(as combination of the first 2 we discussed last time):
Problem Statement:
Automotive Original Equipment Manufacturers (OEMs) encounter significant challenges in incorporating third-party service providers into their in-car entertainment ecosystems, compounded by the lack of a standardized approach for the integration of payment, billing, invoicing, and master data exchange processes. This complexity is further exacerbated when attempting to create a uniform API interface that allows third-party applications to conduct transactions for various use cases such as parking, charging, and purchasing food directly from the vehicle's interface. The absence of an industry-wide standard leads to each OEM and third-party provider independently tackling these issues, resulting in inefficiencies and a disjointed user experience.
Solution Proposal:
The proposed initiative aims to tackle the dual challenges faced by OEMs and third-party service providers by establishing a common industry standard that not only streamlines the integration of services into in-car entertainment systems but also defines a standard API interface for third-party apps. This standard will facilitate seamless payment, billing, invoicing, and master data exchange, alongside ensuring technical integration is both efficient and scalable. By doing so, it will enable a consistent and user-friendly interface for in-car transactions across various services and applications, enhancing the overall digital experience within vehicles.
Potential Action Items:
Convene a working group consisting of representatives from automotive OEMs, third-party service providers, app developers, and tier 1 suppliers to collaboratively define the scope and specifications of the proposed industry standard.
Develop a comprehensive framework for the standardization of payment, billing, invoicing, and master data exchange processes, including technical integration guidelines.
Define a uniform API interface that can be implemented by OEMs and/or app stores, ensuring compatibility and ease of integration for third-party applications.
Proposal 2: In-Car Wallet Interface for Apps:
Problem statement:
OEMs face a challenge in standardizing an API interface that 3rd party apps can access to conduct payments usecases such as parking, charging, buying food etc.
Solution Proposal:
Define a standard interface (APIs) that will be implemented by the OEM and/or app stores and tier 1s
Proposal 3: Relevant payment methods
Problem statement:
Validate if other payment methods than credit cars play a relevant role to be implemented as method for in-car payment
Proposal 4: OTA
Problem statement:
OEM face the issue that updates / replacements of rolled-out applications in vehicles is a problem. Typically not all relevant vehicles are updated and OTA.
Solution proposal: Define a consensus on huch much payment credential is stored in the vehicle vs. the cloud with all the implication to security, authentication, etc. .
In-Car Wallet Interface for Apps:
Problem:
OEMs face a challenge in standardizing an API interface that 3rd party apps can access to conduct payments usecases such as parking, charging, buying food etc.