Velocity ChecksA Critical Component of Your Fraud Prevention Strategy

Roger Alexander
Roger Alexander | November 22, 2024 | 10 min read

What are Velocity Checks?

In a Nutshell

Velocity checks are a fraud prevention tool designed to monitor the pace at which buyers submit transactions. If you’re out to craft the most comprehensive fraud prevention strategy possible, this article will explain everything you need to know about velocity checks, including why you should integrate them as soon as possible.

Velocity Checks: One of the 10 Key Fraud Prevention Tools

When we talk about fraud, it’s important to remember that it’s not a singular, static problem with just one solution. Effective fraud management demands a multilayer approach, deploying a variety of tactics to attack fraud from multiple angles.

For instance, did you know that a fraudster who submits an unauthorized transaction is probably not the same person who stole a cardholder’s information?

Fraudsters usually buy stolen cardholder information in bulk from hackers. They also run numerous transactions in quick succession, with the aim being to get as much value out of the data as possible before being detected.

So, if that’s the case, you could stop many fraud attacks — or at least minimize losses — by deploying a tool to restrict the number of transactions a user can submit at a time. That’s why velocity checks should become a cornerstone of your anti-fraud strategy.

What are Velocity Checks?

Velocity checks

[noun]/və • lä • sə • dē • CHek/

Velocity checks (sometimes referred to as “velocity limits”) are a fraud prevention mechanism widely used by eCommerce merchants. The tool is designed to flag potential fraud based on the rate at which a buyer submits multiple transactions.

Velocity checks, as the name suggests, monitor the frequency and speed at which a cardholder attempts transactions, logins, or account changes. If submissions are deemed to be excessive, or if purchase behavior deviates substantially from normal purchase patterns, the attempted transactions will be flagged as potential card testing or brute force attacks. They may be blocked as a result.

For example, let’s say a customer logs into Amazon.com, and attempts 5 consecutive purchases within 30 minutes. Their purchasing history shows that they usually complete one purchase in a typical month. With velocity check system in place, it may decline the transactions, or flag them for manual review.

These checks can monitor a range of data elements, including a customer’s:

  • Email address
  • First and last name
  • Device name and language
  • Installed plugins
  • IP address
  • Billing address
  • Shipping address
  • Card number

To improve the effectiveness of velocity checks, merchants should monitor multiple data points submitted at the point of sale.

How Do Velocity Checks Work?

TL;DR

The velocity algorithm compares historical user data against current transaction data. This is done in the context of a pre-programmed ruleset. For example, if a user initiates a bunch of transactions in rapid succession which contradicts historical data for that customer, those transactions will be flagged.

Velocity checks establish a correlation between users and actions (or combinations thereof). These data points are then ranked by a complex system of algorithms to determine a regularity function. This function is then compared against an element of time. In the example below, these transactions made by the same buyer within a few minutes of one another would be considered suspicious:

A secondary component of this system would entail a customer initiating transactions that trigger the predetermined ruleset in any meaningful way. For instance, a handful of purchases made outside of regional operating hours, several purchases made in unusually small increments, etc. These data points can be found using sources like device fingerprinting and canvas fingerprinting.

Velocity limits can be implemented according to two specific indicators:

Credit Card Velocity Checking

Credit Card Velocity Checking

These velocity checking rules are linked to the use of specific cardholder information over a period of time. The system is designed to flag any suspicious transaction volume with regard to the credit card being used.

IP-Based Velocity Checking

IP-Based Velocity Checking

Velocity IP checking tracks the number of attempts that have been recorded from a particular IP address over a short period of time. These systems can flag repeated submissions from the same IP address.

4 Steps to Deploy Velocity Limits

To date, there are countless combinations of velocity rules that you can apply to filter out questionable users or transactions. That said, fraud detection platforms offering velocity checks typically follow specific steps:

Identification of Relevant Data

Providers can access historical transactions in several ways, but the most logical for velocity-checking purposes is through machine learning. This technology can identify and display information at near-immediate speed. This information is critical for crafting your velocity ruleset.

Establishing Velocity Rules

Virtually any combination of data points, timeframes, and user data may be applied via conclusions reached in the first step.

Applying Velocity Rules

Once the initial rules are established by the merchant or provider, the system will run constant velocity checks to assess user behaviors.

Trigger Response

When the rules and conditions outlined in steps one and two warrant a velocity response, a predetermined result will be triggered. For instance:

  • Rejecting a transaction
  • Blocking the user from future transactions
  • Flagging the user as high-risk
  • Asking users to verify their identity

Once the machine has done its work, it’s up to you to decide how to proceed. This is a fairly swift process that occurs in just seconds, with limited friction introduced at checkout.

The Importance of Velocity Checks

TL;DR

When deployed at checkout, velocity checks make it more difficult for fraudsters to conduct manual or automated purchases using stolen card numbers.

Velocity checks work because they target common fraud tactics. In a typical attack, a scammer will illicitly get access to card details via hacking, phishing, or by buying card numbers from black-hat data brokers on the dark web. Once the attacker discovers a working card combination, they have a limited window of opportunity to act before the card is reported as stolen and subsequently frozen or canceled. So, the scammer will often try to make a lot of high-value transactions in a short period of time to maximize their value.

If the transactions are approved, the attacker profits. If this happens, it’s already too late: by the time the cardholder uncovers the fraudulent purchases, the transactions will have already settled. As a result, the cardholder contacts their issuer to file a chargeback. That means the merchant ultimately bears the cost of fraud.

Need help? A better way to stop fraud and chargebacks is just a click away.REQUEST A DEMO

Velocity checks play a crucial fraud prevention role at the point of checkout. This security mechanism blocks repeated transaction attempts, thereby thwarting:

Velocity checks are useful in that they can be customized and tailored to respond to specific fraud indicators. For instance, systems can be configured to flag high purchase amounts from new accounts, transactions attempted from certain geographical locations, similar or identical purchases in short succession, or transactions originating from particular IP addresses.

Velocity Checks & False Positives

TL;DR

Velocity checks can sometimes misidentify legitimate transactions as fraudulent. Merchants should tailor fraud parameters carefully or engage in a multi-layered approach.

Velocity checks are not a panacea for all fraudulent attacks. Like many preventative measures, they are prone to false positives, which occur when valid transactions are flagged as fraudulent. For instance, legitimate buyers making multiple purchases during a promotional period, multiple accounts sharing one payment method, or buyers placing orders while traveling abroad can set off false alarms.

Merchants can reduce false positives by setting reasonable and flexible velocity thresholds that balance individual, time-based, and transaction volume-based fraud indicators. Using past account activity and purchase behavior as a guide, along with contextual data gleaned from device fingerprinting techniques, can also help stop false positives.

After all, every business faces different purchase and fraud patterns. Merchants who continually fine-tune fraud parameters in response to new information, and who use velocity checks in concert with other fraud prevention tools, are more likely to maximize their true positive rate and minimize false flags.

A Multi-Tiered Strategy is Best

TL;DR

Merchants should use velocity checks in combination with other pre- and post-transaction fraud prevention tools as part of a multi-layered strategy to stop fraud.

Velocity checks are useful, but they’re just one of many fraud prevention tools that merchants should deploy. Fraud tactics are constantly evolving, so merchants should combat illicit activity using a holistic and proactive approach.

For starters, this means deploying multiple fraud prevention tools that address both checkout and post-transaction fraud risks. Doing so improves the likelihood that fraudulent activity left undeterred can be detected and neutralized by systems deployed elsewhere. 

For example, merchants can implement:

Learn more about fraud detection tools

Data from each of these fraud detection tools can be composed into a single, simple fraud score. This can help you quantify transaction fraud risks, compare relative risks, and flag or reject risky purchases either manually or automatically.

Velocity Controls: An Important Component of a Larger solution

Velocity checks play an important role in deterring pre-transaction fraud. Use them exclusively, however, and you’re left vulnerable against other threats. 

Take post-transaction fraud risks like friendly fraud, for example. This is a pervasive problem that, according to the 2024 Chargeback Field Report, accounts for at least 50% of all chargebacks. That’s where other fraud fighting tactics, like tactical chargeback representment, come into play.

Have questions? Reach out to Chargebacks911 for a fully-customized, no-obligation ROI analysis today.

FAQs

What is a velocity check?

Velocity checks (sometimes referred to as “velocity limits”) are a fraud prevention mechanism widely used by eCommerce merchants. The tool is designed to flag potential fraud based on the rate at which a buyer submits multiple transactions.

What is a credit card velocity check?

These velocity checking rules are linked to the use of specific cardholder information over a period of time. The system is designed to flag any suspicious transaction volume with regard to the credit card being used.

What is a velocity IP check?

Velocity IP checking tracks the number of actions, transactions, or attempts that have been recorded from a particular IP address over a short period of time.

How do velocity checks work?

The algorithm behind velocity limit technology compares historical user data against current transactional data under the observable context of a pre-programmed ruleset. For example, if a user initiates a bunch of transactions in rapid succession which contradicts historical data for that customer, the transaction will be flagged for review.

Why are velocity checks important?

Besides being highly customizable and integratable with existing systems, velocity rules can help identify several threats, such as account takeover (ATO) fraud, chargeback fraud, and synthetic fraud.

Do velocity checks generate false positives?

Unfortunately, no anti-fraud solution is perfect on its own. There’s a genuine risk that velocity checks could generate false positives and stop legitimate buyers from completing purchases. The odds of this happening are low, but it’s possible if you’re over-relying on velocity checks as an indicator.

Roger Alexander

Author

Roger Alexander

Roger Alexander is a Board Advisor at Chargebacks911. He has more than three decades of experience in the payments and finance space, having served in advisory, directory, and executive roles at a number of firms including Valitor, AvantCard, AltaPay, and Elavon, to name just a few. He attended Harvard Business School to study strategic marketing management.

Like What You're Reading? Join our newsletter and stay up to date on the latest in payments and eCommerce trends.
Newsletter Signup
We’ll run the numbers; You’ll see the savings.
triangle shape background particle triangle shape background particle triangle shape background particle
Please share a few details and we'll connect with you!
Revenue Recovery icon
Over 18,000 companies recovered revenue with products from Chargebacks911
Close Form
Embed code has been copied to clipboard