Actions

This action allows to temporarily block the payment capture.

In the meantime, the Merchant can verify the transaction and decide if they wish 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. 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 risk rule, the merchant is notified via the instant payment notification.

The vads_risk_assessment_result field is set to MANUAL_VALIDATION.

The merchant cannot define a specific notification rule to be notified about this action.

This action can be combined with other actions, such as Raise an alert or Define an authentication mode.

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

Refuse action has priority over Validate manually.

This action allows to warn the merchant that a risk has been identified.

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

This action can be combined with other actions, such as Validate manually or Define an authentication mode.

The alert allows the merchant to trigger processing or verification for the transaction, such as placing the delivery process on hold until checks can be performed on the transaction.

It allows to change the default authentication mode (NO_PREFERENCE) applied upon the payment.

The available choices depend on the store’s options.

If “Frictionless” is selected, 3D Secure v2 authentication will be performed with the merchant preference forced to Frictionless if an exemption applies (see “Application of exemptions”).

For additional information, click “?” in the Help column.

Action not available in the “3D Secure result” tab.