Velocity checks

Spec sheet // Glossary // VELOCITY CHECKS
Glossary / V / Velocity checks
Glossary · Transaction monitoring

Velocity checks

Also called velocity rules, frequency checks

Definition

Velocity checks are monitoring rules that count how often something happens, or how much value moves, within a set time window, and raise an alert when the count passes a limit. Firms use them to catch card fraud, account takeover, bot sign-ups and money laundering patterns such as structuring that single-transaction checks miss.

NORMALRISINGLIMITALERT
Fig. 1 · Velocity checks
SCA RTS, Article 2 · SCA RTS, Articles 11 and 16
Key rulesSCA RTS, Article 2 · SCA RTS, Articles 11 and 16
Applies toPayment service providers
RegionsGlobal · EU
01

How it works

A velocity rule pairs an entity, an event and a time window. The entity can be a card, account, device, IP address or email address. The event can be a payment, failed login, new payee, password reset or application. A rule might flag more than five card payments in ten minutes, three new payees in a day, or ten applications from one device in an hour. Amount-based versions add up value instead of counting events.

Fraud teams run velocity checks in real time, so a burst of card testing or a takeover attempt is stopped before more money leaves. AML teams use longer windows, such as cash deposits just under a reporting threshold over several days. Limits are tuned against customer segments to keep false positives down, and many firms feed velocity counts into machine learning models as features rather than relying on fixed limits alone.

Step 1Pick the entityChoose what to count against: card, account, device or IP.
Step 2Define the eventSelect payments, logins, payees or sign-ups to count.
Step 3Set the windowFix the time period, from minutes to weeks.
Step 4Set the limitChoose a count or value that triggers an alert.
Step 5Tune and reviewAdjust limits by segment to cut false positives.
02

The rules

EU · 14 September 2019SCA RTS, Article 2Commission Delegated Regulation (EU) 2018/389 on strong customer authentication and common and secure open standards of communication, Article 2

Requires transaction monitoring that detects unauthorised or fraudulent payments, taking into account factors including payment amounts, known fraud scenarios and compromised credentials.

Payment service providers
EU · 14 September 2019SCA RTS, Articles 11 and 16Commission Delegated Regulation (EU) 2018/389, Article 11 (contactless payments at point of sale) and Article 16 (low-value transactions)

Allow low-value payments without SCA only until a cumulative counter is reached, such as five consecutive transactions or a cumulative amount since the last SCA.

Payment service providers applying SCA exemptions
03

Common questions

What is an example of a velocity check?

Flagging a card used for more than five online payments in ten minutes is a common velocity check. It catches card testing, where fraudsters run small payments to see which stolen card numbers work.

Are velocity checks used in AML?

Yes. AML teams count cash deposits, transfers or new counterparties over days or weeks to detect structuring, mule activity and rapid movement of funds through an account.

Do velocity checks create false positives?

They can, because busy but legitimate customers trip fixed limits. Firms reduce this by setting limits per customer segment and combining velocity counts with other risk signals.