Page History
...
Depending on the content of the received threedsdata block (units 3, 4, 5), the authentication proceeds differently.
Main work scenarios:
- For version 3D-Secure 2.0 (unit 3), if the interaction with the card holder is necessary (unit 4) and the issuing bank URL threeDSMethodURL is present (unit 5), the enterprise generates hidden HTML iFrame on the payment page (unit 8) and sends a POST request with one parameter threeDSMethodData to the received address threeDSMethodURL.
- For version 3D-Secure 2.0 (unit 3) without the interaction with the card holder (unit 4), Assist immediately executes a transaction in processing or completes the operation with an error (depending on processing and enterprise settings, and authentication result) (unit 12).
- For version 3D-Secure 2.0 (unit 3), if the interaction with the card holder is necessary (unit 4) and the issuing bank URL threeDSMethodURL is present (unit 5), the enterprise should generate an HTML iFrame object on the payment page and send an HTTP POST request for the card holder verification to the specified challengeurl URL (unit 11). This iFrame displays the issuer's bank ACS page and the customer enters a one-time password received from the bank.
...