Use of FIDO Authentication Data in 3-D Secure Messages
summary
Describes a concrete EMV 3-D Secure payload: merchants put a JSON up to 3DS requestor otd (20,000 chars) carrying RP ID, a registration attestation blob, device binding info and an authentication assertion blob plus an SPC flag. Flow shows IDV then on-device passkey creation, a registration 3DS message to the issuer, and later an assertion message the issuer can verify against the stored public key. Pilots are running and issuers can ignore the optional field today or consume it for risk or audit evidence.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:25EMV 3DS overview
- 2:41How the 3DS protocol works
- 6:16FIDO and EMV 3DS integration
- 7:53Enrollment and authentication
- 11:09Message formats and structure
- 13:11Strategic call-outs and future
- 14:45Q&A session
related talks
25mEMV® 3DS: Enhancing secure, convenient authentication ...
25mKeynote Reshaping Digital Payment Authentication
24mWhere FIDO Meets SSI
14mSecuring Authentication with and within FIDO
02h 22mFIDO 101
24mStreaming Authentication
28mAuthentication Digital Financial Services
23mEnhancing FIDO2 Security for Safety-Critical Applications: Best Practices and Consid...
