Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1)

Hey @marcoscaceres I found the EMVCo and UL webinars on 3-D Secure 2.0 to be helpful in understanding the 3DS architecture. The Directory Server is in the "interop domain" - essentially, it's a network entity that acts as a broker between the 3DS Server in the "merchant or acquirer domain" (likely run by a payment service provider) and the Access Control Server in the "issuer domain". As far as I can see, architecturally it doesn't make sense for the browser to communicate directly with the Directory Server.

-- 
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/1#issuecomment-363162608