Advanced Fraud Detection Suite (AFDS)

AFDS enables merchants to control and filter transaction activity on their account to control fraudulent activity.
AFDS is available through the Marketplace. For details on the Marketplace, see Marketplace.
The following filters and settings are available in AFDS:
Enables you to set how many transactions to allow each day and filter transactions beyond the daily threshold. All transactions received beyond the daily threshold are handled according to the filter action you select.
Evaluate your weekly or monthly transaction volume and determine the average number of transactions you are likely to process in a day.
Enables you to set how many transactions to allow each hour and filter transactions beyond the hourly threshold. All transactions received beyond the daily threshold are handled according to the filter action you select.
Evaluate your weekly or monthly transaction volume and determine the average number of transactions you are likely to process in an hour.
Allows
Authorize.net
to detect and filter highly suspicious transactions. The filter uses a complex set of criteria set by the Fraud Management team after much research. Because this filter is managed by the Fraud Management team, there are no custom settings.
You cannot decline transactions triggered by this filter since the filter uses a more general set of criteria.
Enables you to set how many transactions to allow from a customer's IP address each hour and to filter transactions beyond this threshold. In order for this filter to work, your integration must include the customer IP address in transaction requests.
Multiple transactions that are part of the same order do not trigger this filter.
Enables you to have greater control over what actions to take based on a transaction's Address Verification Service (AVS) response.
To ensure that transactions are run through the Enhanced AVS Handling Feature, require the billing address and ZIP code on your payment form.
Enables you to have greater control over what actions to take based on the results of card code verification. Card code verification uses the three-digit code on the back of most payment cards, or the four-digit code on the front of American Express cards, to compare with the card code on file with the card issuing bank.
To ensure that transactions are run through the Enhanced CCV Handling Feature, require the card code on your payment form.
Enables you to determine a minimum and maximum transaction amount and filter transactions less than the minimum amount or greater than the maximum amount. All transactions with an amount below the minimum or above the maximum transaction amount are handled according to the filter action you select.
If you allow $0 authorizations, set the minimum to "0". For the maximum transaction amount, determine the amount based on the highest transaction amounts you have processed in the past.
If you add more products or services, adjust the maximum transaction amount as appropriate.
Allows
Authorize.net
to confirm that the shipping address is a valid mailing address.
To ensure that transactions are run through the Shipping Address Verification Filter, require the shipping address on your payment form.
Enables you to filter transactions where the shipping address does not match the mailing address associated with the customer's IP address.
In order for this filter to work, your integration must include the customer IP address and shipping address in transaction requests.
Mismatches are common with gift transactions and do not always reflect a suspicious transaction.
Enables you to filter transactions originating in certain regions or countries. The list of regions include an unresolved region to allow for cases where a transaction's IP address cannot be resolved to a country, which may occur on rare occasion if there are technical issues.
In order for this filter to work, your integration must include the customer IP address in transaction requests.
Enables you to filter transactions where the shipping address does not match the billing address. This filter is useful for manually reviewing orders where customers want to ship to an address other than their billing address.
Keep in mind that a shipping-billing mismatch may occur for several legitimate reasons, such as when using a gift card. In order for this filter to work, your integration must include the shipping and billing addresses.
Accepts transactions submitted only by servers with IP addresses added to this filter. All transactions coming from servers not listed in the filter are rejected.
Rejects transactions submitted from customer IP addresses added to this filter. In order for this filter to work, your integration must include the customer IP address in transaction requests.