Descriptive decline reasons now available for Fraud Detection

Our Fraud Detection solution helps to reduce transaction fraud and risk by blocking payments based on pre-set or custom rules. When Fraud Detection blocks a transaction, you’ll receive a 40101 – Risk blocked transaction response code.

Alongside custom rules that you can configure in Fraud Detection, global Checkout.com policies may block transactions in certain scenarios, such as during high-velocity card testing attempts, or transactions from countries with a very high risk of fraud.

Our merchants have asked for more visibility of why Fraud Detection is blocking payments so they can understand what rules contribute to these declines. To give greater transparency on why Fraud Detection has blocked a transaction, you can now view detailed information in our Dashboard.

Viewing Fraud Detection decline reasons in the Dashboard

To view the Fraud Detection decline reason for a specific transaction:

1. Log in to the Dashboard.

2. Navigate to the Payments tab.

3. Identify and select the transaction that returned the response code.

4. On the Payment timeline section, expand the Risk-Pre Auth-Decline event, to see the different assessments related to the transaction.

5. Go to the View full assessment page for more information on the rule that triggered the response code, such as the one below:

If you need more information about the specific rule, please contact your Account Manager or raise a support request via the Dashboard.

What’s next?

We’re investigating enhancing our API to let you view the rule information for a 40101 declined transaction directly in the response. We’ll be in touch with more details about this feature once we’ve completed our discovery phase.

Until then, we hope you find this enhancement useful in understanding the behavior of our Fraud Detection solution. If there are any other improvements that you’d find beneficial, we’d love to hear your feedback.

‍

‍