Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • If there is the issuing bank URL threeDSMethodURL (unit 7), the merchant generates hidden HTML iFrame on the payment page (unit 9) and sends a POST request with one parameter threeDSMethodData to the received address threeDSMethodURL, and then calls the get3dsecver2 service (unit 10).
  • If there is the issuing bank URL threeDSMethodURL (units 7, 9, 10), without the additional interaction with the card holder (unit 8) - Frictionless Flow (F), IPS Assist immediately executes a transaction in processing or completes the operation with an error. In response to a call to the get3dsecver2 service, the merchant will receive the payment status (unit 6).
  • For 3D-Secure version 2 (unit 3), if If there is the issuing bank URL threeDSMethodURL (units 5 7, 89, 910), and the additional interaction with the card holder is necessary (unit 108), the enterprise merchant generates hidden HTML iFrame on the payment page (unit 8) and sends 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. This is the Challenge Flow (C) scenario.
  • For 3D-Secure version 2 (unit 3) with no issuing bank URL threeDSMethodURL and without the additional interaction with the card holder, - Frictionless Flow (F), the transaction will be processed immediately and the payment process will be completed (unit 12).
  • For 3D-Secure version 2 (unit 3), if the additional interaction with the card holder is necessary (unit 4), but with no issuing bank URL threeDSMethodURL, 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.

...