Règles de vélocité
Les règles de vélocité sont un élément essentiel de la prévention de la fraude, conçues pour détecter les modèles inhabituels de fréquence et de valeur des transactions.
Cardflo permet aux marchands de définir des limites précises sur le nombre de transactions, ou la valeur, qui peuvent être traitées par une seule carte, un client ou une adresse IP sur une période définie.
Cela aide à identifier et à bloquer les tentatives de fraude à volume élevé et à courte durée.
- Catégorie
- Risque
- Capacités
- 10
- Disponible sur
- Tous les plans
L'aperçu
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.
Comment ça marche
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.
Pourquoi c'est important
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.
Cas d'usage
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.
En chiffres
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.
Termes associés
Talk to our team about a live rollout on your acquiring stack.
What you get with Règles de vélocité
- Définissez des limites sur le nombre de transactions par carte, client ou IP sur une période donnée.
- Définissez des seuils pour la valeur totale des transactions par entité sur des périodes spécifiées.
- Surveillez la vélocité sur plusieurs comptes marchands ou unités commerciales.
- Déclenchez des alertes ou des rejets automatiques lorsque les seuils de vélocité sont dépassés.
- Personnalisez les fenêtres de vélocité (par exemple, horaire, quotidienne, hebdomadaire).
- Différenciez les règles de vélocité en fonction de la méthode de paiement ou du score de risque.
- 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 Règles de vélocité
Qu'est-ce qu'une règle de vélocité dans le traitement des paiements ?
Une règle de vélocité surveille la fréquence ou la valeur des transactions d'une entité spécifique, telle qu'une carte, un client ou une adresse IP, sur une période définie.
Elle est utilisée pour détecter une activité rapide et inhabituelle qui peut indiquer un comportement frauduleux, comme des tests de carte ou des tentatives de prise de contrôle de compte.
Comment les règles de vélocité préviennent-elles la fraude ?
Les règles de vélocité préviennent la fraude en identifiant des modèles qui s'écartent du comportement d'achat normal.
Par exemple, plusieurs transactions de grande valeur effectuées avec une nouvelle carte en quelques minutes peuvent déclencher une règle, conduisant à ce que la transaction soit signalée ou refusée, bloquant ainsi une fraude potentielle.
Puis-je ajuster les règles de vélocité de manière dynamique ?
Oui, Cardflo permet aux marchands d'ajuster les règles de vélocité de manière dynamique.
Cette flexibilité est importante pour s'adapter aux conditions commerciales changeantes, aux lancements de nouveaux produits ou aux tactiques de fraude en évolution, garantissant que votre prévention de la fraude reste efficace et pertinente.
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.
Prêt à accélérer ?
Parlez-nous de votre activité. Nous vous mettrons en relation avec les bons partenaires acquéreurs et la bonne route, généralement en moins d'une semaine.