[w3c/3ds] Can browser support frictionless flow without fingerprinting? (#10)

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


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/3ds/issues/10