Managing actions

Several actions are available to the merchant.

  • Disable or Enable 3D Secure

This action allows to not perform the 3D Secure authentication during a payment (for small amounts, for example) or, inversely, to force it.

Note:

The shop has a default behavior: enabled or disabled 3D Secure. This behavior can also be configured in the Advanced risk assessment. The action will allow to modify the default behavior.

  • Decline the payment

This action allows to reject a payment.

Example: reject 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, 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" 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 (this corresponds to using the condition "RISK_CONTROL_WARNING" in a rule of the notification center).

  • Manual validation

This action allows to temporarily block the payment capture.

In the meantime, the merchant can verify the transaction and decide if he/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.