速度規則
速度規則是欺詐預防的關鍵組成部分，旨在檢測交易頻率和價值的異常模式。 Cardflo 讓商戶可以精確設定單張卡、單個客戶或單個 IP 地址在定義的時間段內可以處理的交易數量或價值限額。
這有助於識別和阻止高頻、短時間內的欺詐嘗試。
- 類別
- 風險
- 功能數
- 10
- 適用於
- 所有方案
概覽
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.
運作方式
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.
為何重要
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.
應用案例
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.
數據概覽
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.
相關術語
Talk to our team about a live rollout on your acquiring stack.
What you get with 速度規則
- 在指定時間範圍內設定每張卡、每個客戶或每個 IP 的交易數量限制。
- 為指定時間段內每個實體的總交易價值定義閾值。
- 監控多個商戶賬戶或業務單位的速度。
- 當速度閾值被突破時觸發警報或自動拒絕。
- 自訂速度窗口（例如，每小時、每日、每週）。
- 根據支付方式或風險評分區分速度規則。
- 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 速度規則
支付處理中的速度規則是什麼？
速度規則監控特定實體（例如卡、客戶或 IP 地址）在設定時間段內的交易頻率或價值。 它用於檢測可能表明欺詐行為（例如卡測試或帳戶盜用嘗試）的快速、異常活動。
速度規則如何防止欺詐？
速度規則透過識別偏離正常購買行為的模式來防止欺詐。 例如，新卡在幾分鐘內進行多次高價值交易可能會觸發規則，導致交易被標記或拒絕，從而阻止潛在的欺詐。
我是否可以動態調整速度規則？
是的，Cardflo 讓商戶可以動態調整速度規則。 這種靈活性對於適應不斷變化的業務條件、新產品推出或不斷演變的欺詐策略非常重要，確保您的欺詐預防保持有效和相關。
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.