Actions

The available actions depend on the shop options. By default, you have access to the “Receive an alert” and “Refuse the payment” actions.

Action	Description
Validate manually	This action allows to temporarily block the payment capture. In the meantime, you can verify the transaction and decide to validate or cancel it. The transaction has been created with manual validation. It can be validated as long as the capture delay has not passed. After this delay, the payment takes the “Expired” status. This status is final. When the transaction is created in manual validation mode following the application of a control, you are notified via the instant payment notification. The value MANUAL_VALIDATION is sent in vads_risk_assessment_result in redirect mode and fraudManagement.riskAssessments.results in embedded mode. To receive e-mail notification when a control creates a transaction in manual validation mode, you must: add the “Receive an alert” action in the control configuration and create a notification rule specific for risk assessment. This action can be combined with other actions, such as Receive an alert or 3-D Secure preference.
Refuse the payment	This action allows to refuse a payment. Example: refuse a payment if the used card is a commercial card. The Refuse action has priority over Validate manually. The payment is declined and the error detail (vads_payment_error / detailledErrorCode) is set to 147.
Receive an alert	This action notifies you that a risk has been identified. Examples: the amount of the transaction is greater than EUR1000, the transaction has been made with a card from a country considered as high-risk for online fraud. This action can be combined with other actions, such as Validate manually or 3-D Secure preference. The alert allows you to trigger processing or verification for the transaction, such as placing the delivery process on hold until checks can be performed for the transaction. You are informed: via the end of payment notification The INFORM value is sent in vads_risk_assessment_result in redirect mode and fraudManagement.riskAssessments.results in embedded mode. by e-mail You must create a specific e-mail notification rule to receive the alert. The condition for triggering the notification rule is Informative risk assessment = Failed. For more information on the notification configuration process, see: Be notified in case of fraud risk.
3-D Secure preference.	This action is available if 3-D Secure is enabled for at least one of the contracts associated with the shop. It allows to change the default authentication mode (NO_PREFERENCE) applied during the payment. The available choices depend on the shop options. If your shop has the “Frictionless 3DS2” option and is associated with an activated 3DS2 contract, you will have the choice between the following authentication modes: Challenge Frictionless If “Frictionless” is selected, 3-D Secure authentication will be performed with a forced preference for Frictionless if an exemption applies. You can find all useful information about 3DS exemptions in the 3D Secure guide.