- From: Adam Solove <notifications@github.com>
- Date: Mon, 05 Feb 2018 09:58:30 -0800
- To: w3c/3ds <3ds@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 5 February 2018 17:59:46 UTC
@ianbjacobs the above seems like the most promising path to me. I think the endpoint URL selection is necessary. And so for this flow the two big questions are: 1. can we load the method url or do something else to get fingerprinting info to the issuer? 2. can the payment sheet load the issuer challenge URL in a 3ds2-spec-compliant way? and given that this isn't a "payment handler" specifically, what is the kind of thing that knows how to load this URL? (Is it baked into the browser? A third-party script url running in a payment handler-like environment?) -- 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/2#issuecomment-363166659
Received on Monday, 5 February 2018 17:59:46 UTC