- From: Gildas Le Louarn <notifications@github.com>
- Date: Tue, 30 Jan 2018 16:23:14 +0000 (UTC)
- To: w3c/3ds <3ds@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 30 January 2018 16:23:41 UTC
Fully agree with you Adam but in such case, it remains some tricky questions. Specification from EMVCo concerning native client is [there ](https://www.emvco.com/wp-content/plugins/pmpro-customizations/oy-getfile.php?u=/wp-content/uploads/documents/EMVCo_3DS_SdkSpec_210_1017.pdf) and [there](https://www.emvco.com/wp-content/plugins/pmpro-customizations/oy-getfile.php?u=/wp-content/uploads/documents/EMVCo_3DS_SDKDeviceInfo_210_1017.pdf): - According that specification, the native client shall be able to output native components or HTML content, in such case we still have cross domain issue. - That SDK should be certified, as a consequence who will develop it: agent providers, networks, third parties, merchant using third providers? I share the point of view we need a standardized native implementation to integrate 3DS in browser but according my current knowledge of 3DS 2.1 specification, I can't figure out how to do it without 3DS specification updates. The question can be, should we look for a solution compliant with 3DS 2.1 or could we envisage a solution based one an evolution of the current 2.1 specifications? -- 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-361647745
Received on Tuesday, 30 January 2018 16:23:41 UTC