Fraud Filter - Guide

This guide focuses on how to use Fraud Filter for direct API integration. First, you'll learn how to submit additional fraud data in the request, and then set the Fraud Filter Mode for both the overall transaction level and for an individual fraud rule. You'll then learn how to hold a transaction after it's been authorized and how to release it.

The customer's billing address can be used for Address Verification Service checks and to compare it with the shipping address they provide.

You can also add a product ID, variable reference, and a unique identifier for the customer, along with their IP address. This submitted data can then be used when you set rules in the Fraud Management section of Ecommerce Portal.

In this example, we set the Fraud Filter Mode to Passive at the transaction level and set one rule to Off. We'll also show how to obtain the overall Fraud Filter Result and the result for each individual rule that was executed.

Sample request

If you suspect a transaction is fraudulent and requires further investigation, you can send a Hold request. If the transaction was already placed in the queue to be included in the next settlement file or batch, this will remove it from the queue until the transaction is released.

You can choose to record a reason code for future reference. You must also supply the Order ID and the Payments Reference of the original transaction.

Sample request

If you decide that a transaction is not fraudulent or you have held one in error, you can send a Release request. This will return the transaction to its original status (awaiting settlement or in the queue for the next batch).

Sample request

Explore more functionality to enrich your application.