Velocity of change tracks how frequently specific data elements shift between a new transaction and previous ones — the more alterations across points like phone number or address tied to a given card, the higher the risk signal.
Planning considerations
- Pre-select which fields to monitor and set thresholds for flagging
- Normalize addresses for in-house checks so formatting alone doesn't create false positives
- Use the shipping address for velocity checks, not the billing address
- Log every transaction attempt, not just completed sales
- Retain records for at least 12–18 months
- Choose pass/fail or a graduated risk scale
- Third-party, multi-merchant data sees more than any single merchant's own data can
How it actually runs
It needs a supporting database and two calls: one to increment the count on a data element, another to look it up — comparing paired elements, like a credit card number against a shipping address, and counting how often that pairing changes over a given interval.
Eight common pairings
Credit card–to–expiration date, card–to–address, card–to–phone, card–to–email, phone–to–address, phone–to–card, phone–to–email, and address–to–card.
What it catches
Stolen cards in active use, repeated fraud patterns from the same actor, identity morphing, and general account abuse.