Transaction velocity
Transaction velocity is the rate at which events occur, measured as a count or a total value inside a time window, for example payments per hour or distinct beneficiaries per week. A velocity rule fires when that measure passes a limit set for the window.
In more detail
Velocity answers a question that a threshold cannot. A threshold judges one transaction in isolation, so activity that stays under the limit on every individual payment passes every time. Velocity aggregates the same payments across a moving window, where a pattern becomes visible even though no single payment would have raised an alert.
The window length decides what is caught. A short window, such as attempts per minute, suits scripted activity where the pace is the signal. A longer window suits an account being drained gradually. A velocity limit applied identically to every account will be too tight for busy accounts and too loose for quiet ones.
The system evaluates each new event, receives the running count for the window, and triggers an alert when the count passes the limit.
Example
An attacker with stolen card details tests them with eight small purchases in ten minutes. Each purchase is trivial, but the count in that window is far above anything the card has shown before, so the velocity rule fires.
Related capability
Writing velocity rules in the rules engine
Related terms
Discuss your transaction monitoring requirements
Tell us which transaction flows you need to monitor, which systems Akoben would integrate with, and how your fraud team works today.
Request a demo