Velocity rules
Velocity rules are a critical component of fraud prevention, designed to detect unusual patterns in transaction frequency and value.
Cardflo enables merchants to set precise limits on how many transactions, or how much value, can be processed by a single card, customer, or IP address within a defined period. This helps identify and block high-volume, short-burst fraud attempts.
- Category
- Risk
- Capabilities
- 10
- Available on
- All plans
The overview
Velocity checks constitute a fundamental layer of a merchant risk management framework, operating as a proactive defence against automation-led fraud.
These rules monitor the frequency and volume of transactions associated with specific identifiers, such as a Card Primary Account Number, IP address, device fingerprint, or email address.
In the context of the payments stack, velocity engine logic typically resides within the gateway or payment orchestration layer, evaluating transaction data before it is sent to the acquirer for authorisation.
By establishing upper limits on the number of attempts or the total monetary value processed within a discrete temporal window (ranging from seconds to weeks), merchants can disrupt brute-force attacks like card testing.
This mechanism is particularly effective at identifying abnormal consumer behaviour that deviates from historical norms, allowing for real-time intervention such as hard declines or routing to Step Up authentication through 3DS. Correct configuration involves balancing fraud prevention with the preservation of legitimate conversion rates.
How it works
Define Identifier Parameters
The system selects specific data points to track, including the card BIN, the merchant-assigned customer ID, or the physical IP address of the checkout session.
These identifiers act as the anchor for counting subsequent transaction events across the merchant account or multiple MIDs within the business entity.
Establish Temporal Windows
Merchants configure specific time intervals for monitoring, such as sixty-second bursts to catch bots or thirty-day windows to identify slower, systematic fraud. These sliding windows continuously update as new transactions enter the gateway, ensuring that the risk engine maintains an accurate real-time count of activity.
Set Threshold Logic
Numerical limits are applied to the defined identifiers. For example, a rule might permit a maximum of three transactions per card per hour.
Thresholds can be based on discrete attempt counts, total cumulative transaction value, or even the frequency of specific decline codes received from the issuer.
Automate Response Actions
When a threshold is breached, the orchestration layer executes a pre-defined action. This can range from flagging the transaction for manual review, forcing a 3-D Secure challenge for SCA compliance, or immediately issuing a hard decline to prevent further exposure to scheme fees or chargebacks.
Why it matters
Mitigation of Card Testing
Automated scripts often attempt to validate stolen card details by processing many small-value transactions in rapid succession. Velocity rules identify these high-frequency patterns immediately, blocking the attempts before they cause significant scheme-fee accumulation or trigger monitoring programmes from the card schemes.
This proactive approach protects the merchant's reputation with their acquirer and minimises technical overhead.
Reduction in Chargeback Ratios
By preventing high-volume fraudulent bursts, merchants can maintain their chargeback-to-transaction ratio within acceptable scheme limits.
Since velocity checks stop unauthorised users from making multiple large purchases on a single compromised card, the potential financial liability from friendly fraud or account takeover is capped at the threshold set by the risk manager.
Use cases
Digital Goods Merchants
Businesses selling instant-access vouchers or software often face rapid-fire theft. Velocity rules prevent a single user from purchasing dozens of codes in minutes, which is a common indicator of a compromised payment instrument.
Subscription Services
Recurring billing entities use velocity checks during the initial sign-up phase to prevent massive bot-net attacks that attempt to create thousands of fake accounts using stolen credit card data sets.
Marketplace Platforms
Platforms with diverse sub-merchants use velocity monitoring to ensure no single buyer is disproportionately targeting specific sellers, which can help in identifying collusion or sophisticated money laundering attempts.
By the numbers
This range reflects industry-standard results for merchants who implement automated velocity blocks on card-testing bursts compared to those relying solely on issuer-side declines.
Typically, well-tuned velocity thresholds flag a small minority of transactions for manual review, ensuring that risk teams focus on high-probability fraud without overwhelming operational capacity.
Most modern gateway risk engines execute velocity check logic within this timeframe, representing a negligible impact on the total checkout response time for the end consumer.
Related terms
Talk to our team about a live rollout on your acquiring stack.
What you get with Velocity rules
- Configure maximum transaction attempts per unique card within a sliding sixty-minute window.
- Limit total transaction value per customer email address over a rolling twenty-four-hour period.
- Restrict the number of distinct cards used from a single IP address daily.
- Apply stricter velocity thresholds for transactions originating from high-risk MCCs or geographic regions.
- Trigger mandatory 3-D Secure authentication when a customer exceeds a mid-tier velocity limit.
- Automate hard declines for entities surpassing maximum frequency caps to avoid acquirer penalties.
- Monitor velocity trends across individual MIDs or aggregate data at the organisational level.
- Exempt whitelisted customers from standard velocity caps to prevent friction for high-value repeat buyers.
- Analyse frequency of soft-decline responses to detect systematic card-testing or probing behaviour.
- Differentiate velocity rules for guest checkouts versus authenticated, logged-in user sessions.
A short scoping call, then a written plan for your MIDs.
Questions about Velocity rules
How do velocity rules assist in preventing card scheme monitoring programmes?
Card schemes like Visa and Mastercard monitor merchants for high decline rates and card-testing activity. If a merchant experiences a surge in unauthorised attempts, they may be placed into monitoring programmes that carry significant monthly fines.
Velocity rules interrupt these automated attacks by blocking the transactions at the gateway level before they reach the issuer. This ensures that the bulk of fraudulent activity does not count towards the merchant's official decline or fraud ratios seen by the scheme.
Can velocity rules be adjusted based on the specific payment method used?
Yes, risk profiles vary significantly between payment types. Merchants often apply more stringent velocity limits to credit and debit card transactions compared to more secure methods like Apple Pay or Google Pay, which utilise biometric tokenisation.
Similarly, Alternative Payment Methods (APMs) that are non-reversible or involve bank transfers might necessitate different threshold logic because the risk of a chargeback is substantially lower than with traditional card payments.
What is the risk of false positives when implementing aggressive velocity caps?
Aggressive velocity rules can inadvertently block legitimate customers, such as power users making multiple purchases or businesses using corporate cards for several employees. To minimise this, merchants should analyse historical transaction data to set thresholds slightly above the 99th percentile of normal customer behaviour.
Implementing a 'shadow mode' where rules flag transactions without blocking them allows risk teams to refine thresholds before going live.
Is it possible to track velocity across multiple merchant IDs (MIDs)?
Payment orchestration platforms allow for the aggregation of transaction data across multiple MIDs. This is vital because fraudsters often rotate through different sub-stores or regional websites to evade detection on a single account.
Cross-MID velocity tracking creates a unified view of the customer identity, ensuring that if a card is blocked on one merchant account due to high frequency, it is globally restricted across the entire organisation.
How does velocity monitoring interact with Strong Customer Authentication (SCA)?
Velocity rules can serve as an intelligent trigger for SCA. Instead of a binary pass/fail, a rule can be configured so that the first two transactions are permitted, but any subsequent attempts within the same hour require a 3DS challenge.
This balances a frictionless experience for the majority of users with the necessary security overhead for transactions that exhibit higher-risk frequency patterns.
What data points are most effective for velocity tracking beyond the card number?
While the Primary Account Number is common, sophisticated fraudsters use multiple cards. Effective velocity strategies incorporate device fingerprinting, shipping address hashes, and email domains.
Tracking the frequency of attempts from a single device ID or a specific subnet of IP addresses is often more effective than card-based tracking alone, as it identifies the underlying infrastructure used by the attacker.
Related features.
Ready for velocity?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.