Digital Native’s Needs & Wants from Financial Services Providers
summary
Digital natives demand real-time onboarding with eKYC, biometric auth (Face ID/WebAuthn) and liveness detection to defeat deepfakes, while APIs must support progressive profiling and granular consent under rules like Hong Kong AML/MLO, PDPO, GDPR or CDR. Use OIDC/OAuth2 and CIBA for third‑party consent flows and FIDO2/WebAuthn for device authenticators. Legacy systems get modernized by putting software skins or a centralized digital identity platform in front and orchestrating APIs — an approach described as already feasible and in production.
AI-written summary · about
chapters (12)
- 0:00Digital natives' financial needs
- 1:29Digital native financial services
- 2:57APIs and digital identity
- 5:51Instant gratification in banking
- 7:16Convenience versus security
- 9:04Progressive profiling and data control
- 11:59Lifestyle platforms shaping expectations
- 13:26APIs in financial ecosystems
- 15:36Key areas for providers
- 18:05Secure financial APIs
- 21:38Modernizing legacy systems
- 24:08Q&A
related talks
28mAuthentication Digital Financial Services
15mTransforming security and experience with digital identity
14mTransforming Digital Identity with AI
38mDigital Identity - Improving the necessary evil
10mDigital Security and Efficiency Through Single Sign-On
40mSecuring Your Direct to Consumer Identity Strategy
10mDigital Identity & Protection
04mYou Don't Need a New Identity Platform for the AI Era