You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
3DS supports no-friction flows and merchants may even accept a liability shift in order to have zero friction flows. Risk engines today fingerprint the browser and determine whether a frictionless flow suffices. Changes in browsers are (by design) going to make the fingerprinting more difficult.
WebAuthn supports low-friction, but not no-friction flows.
What browser capabilities could support no-friction flows without adding to the fingerprinting surface?
3DS supports no-friction flows and merchants may even accept a liability shift in order to have zero friction flows. Risk engines today fingerprint the browser and determine whether a frictionless flow suffices. Changes in browsers are (by design) going to make the fingerprinting more difficult.
WebAuthn supports low-friction, but not no-friction flows.
What browser capabilities could support no-friction flows without adding to the fingerprinting surface?
See some previous discussion about browser-generated IDs:
https://www.w3.org/2019/Talks/ij_risk_20190808/index.html?full#10
The text was updated successfully, but these errors were encountered: