Secure Payments Confirmation 101
summary
Secure Payment Confirmation builds on WebAuthn/FIDO and integrates with 3DS (spec 2311) to present a browser-rendered, biometric/passkey flow that completes with a signed assertion. Implementations in Europe—two production pilots with issuers and PSPs (Germany, Finland)—show it works in production, reduces the merchant flow to 4 screens vs 7, and is measurably faster than OTP. Current limitations: only Chrome and Edge support SBC, Safari does not, pilots are limited to friends-and-family and full rollout awaits device-binding for PSD2 compliance.
AI-written summary · about
chapters (17)
- 0:00Introduction and welcome
- 1:09Personal note and background
- 2:17Context and challenges in payments
- 3:25What is Secure Payment Confirmation
- 5:58Third-party authentication use case
- 6:20How SPC works with FIDO and WebAuthn
- 8:12Benefits of SPC over traditional methods
- 10:20Live demo comparison
- 11:26Pilot programs and testing
- 13:17European pilot details
- 15:04Credential creation process
- 16:09Authentication workflow in pilots
- 20:04Usability study insights
- 21:52Pilot feedback and value
- 22:58Next steps and adoption
- 24:00Future enhancements to SPC
- 25:26Q&A and PSD2 compliance
related talks
25mKeynote Reshaping Digital Payment Authentication
25mEMV® 3DS: Enhancing secure, convenient authentication ...
01h 14mWebAuthn: Theory and practice
33mSimple. Open. Mobile: A Look at the Future of Strong Authentication
33mNavigating Passwordless Authentication with FIDO2 & WebAuthn
42mSecurity, Fraud, and Compliance Panel
32mSecuring Online Identities with Simple, Secure, Open Standards
28mAuthentication Digital Financial Services
