In Vehicle Payments Birds of a Feather

Previous Work Done by the IVP SIG

General

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

Charter

Doc

Wallet Project Charter

Doc

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.

Agenda & Meeting Notes

18th of January 2024

• Permission to record the call?
• Welcome and Introductions
  • List of participants
  • Brief introduction of each member, their role, and organization they represent.
  • Objectives and expectations towards the IVP group
• Recap COVESA Networking Reception & Demonstration Showcase @ CES 2024
  • Pictures
• Proposed problem statements to be tackled within this group:
  • Proposal 1:
    • Problem Statement: OEMs face a challenge in integrating third-party service providers into their in-car entertainment systems, necessitating a complex process that involves payment, billing, invoicing, and master data exchange, along with technical integration between the entities. This issue is compounded by the lack of a standardized approach, resulting in each automotive OEM and third-party provider independently grappling with the same problem.
    • Solution proposal: To address the prevalent challenge faced by OEMs and third-party service providers in integrating services into in-car entertainment systems. This project aims to establish a common industry standard to streamline payment, billing, invoicing, master data exchange, and technical integration processes.
    • Action items:
  • Proposal 2:

    • 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.

        Solution Proposal:
        Define a standard interface (APIs) that will be implemented by the OEM and/or app stores and tier 1s
        Action Items:

  • Proposal 3:
    • Validate if other payment methods than credit cars play a relevant role to be implemented as method for in-car payment
  • Next events
    • COVESA All Member Meeting
      • April 16-18, 2024
        Gothenburg, Sweden
      • Call to action: Participants and potential working group

14th of December 2023

• Who will be at CES? And, what are you doing?
  • mavi.io will be there all week
  • Starfish will be there
• Should we meet at CES?
  • Have presence at booth at CES with QR code to register contact info for updates 
• Problem Statement

16th of Novemeber 2023

• Jens Kohnen and @Vamsi Putrevu will serve as chairs.  It was agreed there is a need for OEM chair(s) in addition.
• It was agreed the next meeting will be on 14th of Dec.  See Community Calendar for details. 
• Charter was reviewed.
• It was agreed there is a need for clear problem statement(s) that this group intends to work on.
• Action Item:  Participants will bring clear problem statements to the next meeting.
• The following areas of categorization were discussed:
  • Feature on demand
  • parking, fuel, charging - scale from vehicle platform
  • vehicle as a platform - direct service provider
• It was suggested that the relationships between VSS and AOSP groups should be explored.