Fraud Protection Tools

To combat online fraud, we have provided Admins with powerful tools. These tools enable Admins to set 24-hour velocity filters, reducing the risk of fraudulent activities. Admins can monitor transaction frequency and detect suspicious patterns.

We also introduced the option for Admins to blacklist end-users based on transactional metrics. This provides an additional layer of protection, preventing potential fraudsters from engaging in illicit activities. As an admin, you can enforce security measures and safeguard your site.

Furthermore, Admins can whitelist verified end-users to ensure legitimate users are not inconvenienced. This balances security and user experience, creating a safer online environment and a seamless transactional process for genuine customers.

Spark Location: Commerce > Fraud Protection

Velocity Filters

Spark Location: Commerce > Fraud Protection - Filters tab

These Filters are set for either Sales or Transaction thresholds for any given 24hr period.

We are providing you with three different ways to limit these transactions:

• Per Email
  • Number of Transactions
  • Dollar amount spent
• Per IP Address
  • Number of Transactions
  • Dollar amount spent
• Per Credit Card - ONLY card type, last 4 digits, expiration date.
  • Due to compliance, we don't ever see the full credit card number - this number is passed along directly to the Gateway.
  • Number of Transactions
  • Dollar amount spent

Any fields left blank when you save your filters will result in no limits being set.

Whitelist & Blacklist Rules

Spark Location: Commerce > Fraud Protection - Whitelist tab or Blacklist tab

Whitelist

This allows you to define emails and/or IP addresses that can bypass the additional fraud tools in place on the Velocity Filters tab AND Accertify (add-on service), if enabled.

1. Name the Rule
2. Add an internal Note (optional)
3. Set the values (Email address or IP address)
   1. You can add multiple emails or IPs by adding one per line (not separated by a comma)
   2. For IP addresses, only IPv4 addresses are supported (0.0.0.0 to 255.255.255.255).
4. Save

There are a few other ways that you can add to the whitelist including from the Purchases Report, the Failed Transaction Report, and the Order Viewer in the Actions Menu.

Blacklist

This tooling allows you to set parameters that, when all are met, the purchase will not be permitted.

1. Name your rule
2. Add an internal Note for reference (optional)
3. Apply Fields - These are the parameters that you can limit.
   • Email Address
   • IP Address
   • Credit Card Full Name
   • Credit Card Last 4
   • Credit Card Type
   • Billing Info - First Name, Last Name, Address, City, Postal Code, State Province, Country
   • Shipping Info - First Name, Last Name, Address, City, Postal Code, State Province, Country
4. Save

Much like the Whitelist, there are a few other places that you can add rules to the Blacklist, These include from the Purchases Report and the Order Viewer in the Actions Menu.

Failed Transactions Report

Spark Location: Commerce > Reports > Failed Transaction

This brand new report will be your go-to report of you have a customer reach out an they are struggling to complete the sale on your website. This new report will capture the Date/Time and Customer information when they are attempting to complete the transaction online. In addition to the customer data, we will also be displaying the Source and the Failure Reason for the transaction.

The sources listed will include:

• Saffire
• Payment Gateway - depending on which Gateway you utilize, the Gateway's name will be displayed
• Accertify - add-on Fraud Protection service. For more information about the Accertify add-on, please reach out to us via support@saffire.com and we will happily explain how this service works and discuss pricing.

In addition to informing you where the source of the failure is occurring, we are passing along the reason for the denial. In the case of source=Saffire, we will explain if these are due to any Blacklist Rule or Velocity Sales or Transaction Limits that have been set.

If the source of the transaction failure is coming from the Payment Gateway, we will pass along the messaging provided by that Gateway. Sometimes these aren't always clear as to what the resolution is, but we have provided a separate article with many of these failure codes and how they can be fixed here: Online payment processing errors

If the source is coming from Accertify, we will give you a table explaining all of the 'points' that have been issued for the transaction, resulting in it's exceeding the threshold limit for your protection.