Most merchants think about fraud prevention in reactive terms: a fraudulent transaction gets processed, a chargeback arrives weeks later, and then you deal with it. That reactive posture is understandable — chargebacks are how you find out a fraudulent transaction happened — but it's also backward. By the time the chargeback arrives, the damage is done. The fraudster has their goods, the legitimate cardholder has been made whole by their bank, and the merchant has lost both the product and the revenue.

Proactive fraud screening — catching suspicious transactions before they authorize rather than after — is what prevents that loss from occurring in the first place. Rule-based fraud screening, which is what CyoGate's iSpyFraud system provides, lets merchants configure custom filters at the gateway level that automatically review every transaction against merchant-defined criteria and block those that don't pass — before authorization, not after the fact.

This guide explains how rule-based fraud screening works mechanically, what the most valuable rules are for different merchant categories, and how to configure iSpyFraud without creating so many false positives that you're blocking legitimate customers alongside fraudulent ones.

How Rule-Based Fraud Screening Works

When a customer submits a payment on your checkout — entering card details, billing address, and other transaction information — that data flows through your payment gateway before it ever reaches the card network for authorization. Rule-based fraud screening operates at this gateway layer, evaluating the incoming transaction data against a set of conditions you've defined.

If a transaction passes all configured rules, it proceeds to authorization normally. If it triggers a rule — for example, the transaction amount exceeds a limit you've set, the IP address is from a geography you've blocked, or a card has been used more than your allowed frequency threshold in a single day — iSpyFraud can decline the transaction before it even reaches the card network, log the event for your review, or flag it for manual review depending on how you've configured the rule's action.

The evaluation happens in milliseconds and is invisible to legitimate customers — their transactions clear the rules and proceed through the normal checkout flow without any added friction. Only transactions that trigger a configured rule see any different outcome.

Importantly, iSpyFraud evaluates transactions both before and after authorization. Pre-authorization rules can decline transactions before they ever reach Visa or Mastercard. Post-authorization rules can void a transaction after it's been authorized but before it's been captured and settled — useful for catching fraud signals that only become apparent after the card network has returned authorization data (such as AVS mismatch patterns that signal a stolen card being tested).

The Core Rule Categories

iSpyFraud rules fall into several categories, each targeting different fraud patterns. Understanding what each type catches — and what it might accidentally catch — is essential for configuring rules that protect you without causing excessive false declines.

Transaction amount limits. Setting a maximum transaction amount rule — for example, declining any single transaction above $500 on an account where your typical order is $50–$100 — blocks the most common pattern of stolen card fraud: running a large transaction quickly before the card is reported stolen. The rule needs to be set high enough not to block legitimate high-ticket purchases, but low enough to flag the outliers. For merchants with variable ticket sizes, a per-day amount limit (maximum charge amount per card number within a 24-hour window) is often more useful than a per-transaction limit.

Velocity limits by card number. How many transactions can a single card number run in a day, a week? Fraudsters testing stolen card lists run rapid-fire small transactions to identify which cards are active before running larger charges. A velocity rule that limits any single card to, say, three transactions per 24 hours catches card-testing patterns without affecting normal customers, who almost never make more than one or two purchases from the same merchant in a day.

Velocity limits by IP address. Similar to card velocity, IP velocity limits catch situations where the same IP address is being used to attempt multiple transactions — often a sign of automated fraud tooling running through a list of stolen cards from a single server. A rule blocking more than a small number of attempts per IP per day filters out the automated attack pattern while leaving normal customer behavior unaffected.

Geographic restrictions. If your business doesn't ship internationally, or if certain countries or regions are a disproportionate source of fraud for your specific product type, iSpyFraud allows you to block transactions from specific geographies — by IP country, billing country, or both. This is one of the highest-leverage rules for merchants whose fraud overwhelmingly originates from specific regions. It should be used carefully — overly broad geographic blocks can decline legitimate international customers — but for businesses whose legitimate customer base is entirely domestic, blocking non-US IP addresses is often a high-impact, low-risk rule to enable.

AVS mismatch rules. Address Verification System (AVS) responses indicate whether the billing address provided by the customer matches the address on file with the card issuer. A full AVS mismatch — where neither the street address nor the ZIP code matches — is a strong signal of a stolen card being used by someone who doesn't know the cardholder's address. iSpyFraud allows you to configure automatic declines on specific AVS response codes, turning AVS from an informational signal into an active screening gate.

CVV failure rules. A CVV (card security code) failure — where the customer-provided CVV doesn't match the issuer's records — is the most direct indicator of a stolen card number. Someone who has the card number and expiration date but not the physical card won't have the CVV. Configuring iSpyFraud to decline transactions with CVV mismatches eliminates a significant category of card-not-present fraud at the gateway level.

The baseline combination: For most ecommerce merchants, the highest-impact starting configuration is: CVV mismatch declines, per-card velocity limits, per-IP velocity limits, and a transaction amount maximum appropriate to your typical order range. This combination catches the most common fraud patterns — card testing, bulk stolen card use, and large-ticket fraud — with minimal impact on legitimate customers who almost never trigger these limits. Start with these, review your flagged transaction log for two to four weeks, then tune based on what you're actually seeing.

The False Positive Problem: Tuning Rules Without Blocking Good Customers

The risk of overly aggressive fraud rules is false positives — legitimate customers whose transactions get blocked because they happen to match a fraud pattern. A legitimate business traveler placing an order from a foreign IP address, a high-value customer making a large purchase that exceeds your amount limit, a customer who genuinely made three purchases in one day because they kept adding to their order — these are real scenarios where fraud rules can create friction for good customers.

The right approach is calibrated configuration rather than maximum restriction. Reviewing your fraud filter logs regularly — iSpyFraud's reporting system gives you a detailed record of every transaction reviewed and every rule triggered — lets you see whether your rules are catching actual fraud or catching legitimate orders. If a rule is generating mostly false positives, it needs to be loosened. If a rule is catching fraud you weren't seeing before, it's working and worth keeping.

Thresholds should be set based on your actual transaction patterns, not generic recommendations. If your typical order range is $200–$800, a maximum transaction limit of $500 is going to generate significant false positives. Set it at $1,200 — high enough to cover your legitimate high-end orders while catching the truly anomalous large transactions. Your iSpyFraud configuration should reflect your business, not a one-size-fits-all template.

iSpyFraud Alongside Other Fraud Tools

Rule-based screening is one layer in a fraud prevention stack, not a complete solution by itself. Understanding how it fits alongside other tools helps you build a layered defense rather than over-relying on any single mechanism.

3D Secure authentication. Where iSpyFraud screens transactions before they reach the card network, 3D Secure 2.0 adds an authentication step that involves the card issuer directly — verifying that the person completing the transaction is the actual cardholder. For transactions that clear iSpyFraud rules but still carry fraud risk signals, 3DS2 provides a second layer of verification and shifts chargeback liability to the issuer for authenticated transactions.

Chargeback prevention alerts. iSpyFraud prevents fraudulent transactions from processing in the first place. But some fraud slips through — particularly friendly fraud, where a legitimate cardholder disputes a transaction they actually authorized. CyoGate's chargeback prevention service catches these disputes before they become formal chargebacks, giving you a window to resolve the issue before it affects your ratio. The two tools serve different parts of the fraud lifecycle: iSpyFraud at authorization, chargeback prevention at the dispute stage.

Manual review for flagged transactions. Not every suspicious transaction needs to be automatically declined. For higher-value transactions that trigger a rule — particularly in B2B contexts where a large legitimate order might match a fraud pattern — configuring the rule to flag for manual review rather than automatic decline lets a human look at the specific transaction and make a judgment call. This is more work than automatic rules, but it preserves revenue from legitimate large orders while still catching fraud.

Who Needs iSpyFraud Most

Not every merchant carries the same fraud risk, and iSpyFraud's value is proportional to your exposure. The merchants who benefit most from active rule-based screening:

High-risk category merchants. Nutraceuticals, digital goods, subscription businesses, electronics, and other categories known for elevated fraud rates benefit from aggressive gateway-level screening. The combination of iSpyFraud with proper AVS and CVV verification significantly reduces the true-fraud chargeback rate that high-risk merchants disproportionately experience.

Merchants with digital or downloadable products. Fraud is particularly damaging for merchants selling digital goods — software, game keys, digital media, access credentials — because there's no physical fulfillment to delay. A fraudster who buys a digital product has received it instantly and irreversibly, making post-delivery recovery essentially impossible. Pre-authorization screening is the only meaningful defense.

Merchants approaching chargeback thresholds. If your chargeback ratio is creeping toward the Visa or Mastercard threshold levels that trigger monitoring programs, reducing inbound fraud through gateway-level screening is one of the fastest ways to bring the ratio down. Every fraudulent transaction that iSpyFraud blocks at the authorization stage is a chargeback that never enters your ratio calculation.

iSpyFraud is available through the CyoGate payment gateway. If you're already a CyoGate gateway account holder, access the iSpyFraud configuration through your merchant control panel. If you're new to CyoGate, the gateway account — including iSpyFraud access — is set up as part of the merchant account application process.