FIDO Munich Seminar Blueprint for In-Vehicle Payment Standard.pptx
Download as PPTX, PDF0 likes900 views
The document outlines the collaboration between Visa and Starfish for an in-car payment standard that utilizes a dual-component backend system including the Hellgate® car wallet and token master. It describes the integration of various security and authentication frameworks such as the Visa token service and cloud token framework, emphasizing device binding and FIDO protocols. Future advancements planned for 2025 are briefly mentioned, highlighting the evolution of the system.
![The Solutions for In-Car-
Payment with
Visa and Starfish
A construction kit for
implementation
Visa Token Service (VTS)
[Security]
Hellgate® Car Wallet
[Authentication in-car]
Visa Cloud Token
Framework (CTF] [Device –
binding]
Hellgate® Wallet Service
[FIDO-Server / Profiles]
&
Hellgate® Token Master
[Provisioning / Binding]
Issuer recieves
authentication
evidence and can
make
authorization
decision
[Transaction
decision]
Current Setup
Future (2025) Setup
Visa Token Service (VTS)
[Security]
Hellgate® Car Wallet
[Authentication in-car]
Visa Cloud Token
Framework (CTF] [Device –
binding]
Hellgate® Wallet Service
[FIDO-Server / Profiles]
&
Hellgate® Token Master
[Provisioning / Binding]
Issuer recieves
authentication
evidence and can
make authorization
decision
[Transaction decision]
Visa Payment Passkey
Service to be the relying
party
[FIDO-Server]
[Scale and Liability Shift]](https://image.slidesharecdn.com/fidomunichseminarblueprintforin-vehiclepaymentstandard-240721104647-bec5af3c/85/FIDO-Munich-Seminar-Blueprint-for-In-Vehicle-Payment-Standard-pptx-4-320.jpg)
FIDO Munich Seminar Blueprint for In-Vehicle Payment Standard.pptx
- 1. ©2023 Visa. All rights reserved. Visa Confidential Visa – Starfish Blueprint for In-Vehicle Payment Standard
- 2. Live-Demo
- 3. © 2024 Starfish GmbH & Co. KG All Rights Reserved. Hellgate® Car Wallet and Token Master On the In-Car Payment Platform backend side two components power the onboard experiences and connect to the world of the card schemes. In-Car Experience Car Wallet Authenticator Hellgate® Wallet Service Hellgate® Token Master OEM onboard OEM offboard Starfish SaaS Identities & Profiles Visa Token Service VTS Visa Cloud Token Framework CTF Uses FIDO UAF/FIDO2 Credentials bound to specific OEM Credentials bound to specific device (car authenticator) FIDO Server
- 4. The Solutions for In-Car- Payment with Visa and Starfish A construction kit for implementation Visa Token Service (VTS) [Security] Hellgate® Car Wallet [Authentication in-car] Visa Cloud Token Framework (CTF] [Device – binding] Hellgate® Wallet Service [FIDO-Server / Profiles] & Hellgate® Token Master [Provisioning / Binding] Issuer recieves authentication evidence and can make authorization decision [Transaction decision] Current Setup Future (2025) Setup Visa Token Service (VTS) [Security] Hellgate® Car Wallet [Authentication in-car] Visa Cloud Token Framework (CTF] [Device – binding] Hellgate® Wallet Service [FIDO-Server / Profiles] & Hellgate® Token Master [Provisioning / Binding] Issuer recieves authentication evidence and can make authorization decision [Transaction decision] Visa Payment Passkey Service to be the relying party [FIDO-Server] [Scale and Liability Shift]
Editor's Notes
- #5: Visa has several products supporting tokenisation, currently we are offering solutions based on VTS and CTF. These solutions come under Visa’s standard product offering, Token Management Services 1. VTS, FIDO, and Visa Secure are the prerequisites for the solution VTS is initiated by a token requestor which are entities who initiate the process of tokenisation – For example, in the Mercedes Pay case, Starfish is the token requestor that sits in-between Visa and Mercedes Pay FIDO (Fast Identity Online) enables consumers to use their on-device biometrics to provide authentication – In the Mercedes Pay case, Cariad (VW subsidiary) provides this technology Visa Secure authenticates the cardholder – In the Mercedes Pay case, Logpay (VW subsidiary) is PSP 2. CTF links the payment credential to the customer and their device/s – Binds the device to a token 3. VDAP allows digital customer authentication within a merchant or digital wallet environment – Authentication on behalf of the issuer, liability lies with the merchant 4. DAF is a Global Commercial Fraud Liability Framework based on risk. Participant assists with the authentication, providing additional data and flags to the issuer via DAF indicator, Visa qualifies the data, and assigns Acquirer Liability Protection – Liability lies with the issuer *It is important to note the VDAP component is being repositioned as part of DAF so it will not be shown explicitly in the future 5. Pass-Through Wallet stores Visa PAN data provided by the cardholder, and during payment the wallet transfers the data to the PG/merchant *This picture will evolve as new market solutions are developed (e.g. FIDO and biometrics)