The 3DS Method allows for additional browser information to be gathered by an ACS prior to receipt of the AReq message to help facilitate the transaction risk assessment. The use of the 3DS Method by an ACS is optional.As EMVCo 3DS specification mentioned, the 3DS Requestor should render a hidden HTML iframe in the Cardholder browser and send a form with a field named threeDSMethodData containing the JSON Object via HTTP POST to the ACS 3DS Method URL.The 3DS requestor receives the 3DS method device collection completion request sent by the ACS within the specified time (for example, 5-second), and sets threeDSCompInd to "Y". If the request is not received within the time, threeDSCompInd should be set to "N". The status of this field needs to be sent in the AReq message request.
Create a hidden iframe and post 3DS Method to the ACS, monitor the response every 500 ms. If there is no response from the ACS in 5000 ms, pass the 3DS Method process and do the AReq.
Post Creq Example(result.action=ChallengeShopper)#
threeDSSessionData: 3DS Requestor session data that is returned by the ACS in the CRes message POST to the 3DS Requestor. Optionally used to accommodate the different methods 3DS Requestor systems handle session information.
The Browser challenge will occur within the Cardholder’s browser, and the ACS will provide a formatted challenge UI to the Cardholder within the browser challenge window.For a better user experience, the 3DS Requestor can create an HTML iframe for challenge in the Cardholder browser and close the challenge window upon receiving the CRes message by refreshing the parent page, and removing the HTML iframe.