What is a velocity check in card payments?
A velocity check in card payments is a risk rule that counts how often something happens within a time window: payment attempts per card, cards per device, orders per address or declines per IP address. When the count passes a limit, the payment is blocked or reviewed. It detects card testing and automated fraud.
In detail
A velocity check measures frequency. It asks whether a pattern of activity is normal for a genuine customer.
What it counts
- Per card: number of attempts or total amount in an hour or a day.
- Per device or IP address: number of different cards tried.
- Per customer account or email: number of orders or failed payments.
- Per shipping address: number of orders from different cards.
- Per merchant: sudden spikes in small authorizations or declines.
What it catches
Card testing is the main target. Fraudsters run many small payments to find which stolen numbers still work. The pattern is visible as many cards from one device, or many attempts on one card with different codes. Velocity checks also limit damage when an account is taken over.
Limits need tuning. A rule that is too tight blocks a family using one card or an office sharing a network. A rule that is too loose lets an attack through, and card schemes monitor merchants hit by testing attacks.
Velocity checks need no data from the cardholder, so they add no friction. They work alongside AVS and CVV, and the limits themselves are explained in velocity limits. Operators also rely on payment resilience so that an attack on one connection does not affect others.