Managing actions

Several actions are available to the Merchant.

  • Disable 3D Secure

This action is only available if the shop’s default 3D Secure behavior is set to 3D Secure enabled by default.

Depending on the 3D Secure protocol available for the MID (contract), this action allows:
  • In 3DS1: to not perform cardholder authentication,
  • In 3DS2: to not express a specific preference concerning the authentication ("No Preference").

    If the issuer decides to perform an authentication without interaction (frictionless), the payment will be guaranteed.

Note:

This option becomes available only after selecting the Selective 3D Secure option.

By default, the behavior of the shop is “3D Secure enabled”.

  • Enable 3D Secure

This action is only available if the shop’s default 3D Secure behavior is set to 3D Secure disabled by default.

Depending on the 3D Secure protocol available for the MID (contract), this action allows:
  • In 3DS1: proceed to cardholder authentication,
  • In 3DS2: request strong authentication of the buyer (“Challenge Requested”).

  • Refuse the payment

This action allows to refuse a payment.

Example: refuse a payment if the used card is a commercial card.

  • Raise an alert

This action allows to warn the Merchant about an identified risk (see chapter Configuring notification e-mails addressed to the merchant).

Examples: the amount of the transaction is greater than 1000 EUR, the transaction has been made with a card from a country considered as high-risk for online fraud, etc.

The alert allows the Merchant to trigger processing or verification for the transaction.

This action allows the Merchant to trigger actions such as put the shipping process on hold while the transaction is being verified. Technically, the module will generate a “Warning” notification for the transaction. To be informed, the Merchant must configure his/her notification center before triggering an IPN URL, an e-mail or an SMS based on the “Warning” status of the transaction. For more information on the notification configuration process, please see chapter Creating notification rules specific to risk assessment.

  • Validate manually

This action allows to temporarily block the payment capture.

In the meantime, the Merchant can verify the transaction and decide if he or she wishes to validate or cancel it.

The transaction is then created via manual validation. It can be validated as long as the capture delay has not passed. Once the delay has passed, the payment takes the Expired status. This status is final.