Browse apps

Security

Shopify Chargeback Rate Thresholds: Block Fraud Pre-Checkout

TL;DR

Payment processors flag dispute activity above 0.75% as excessive, while Visa VAMP and Mastercard ECP monitoring thresholds trigger at a 1.5% ratio alongside monthly dispute floors. Because winning or refunding a chargeback does not remove it from your network ratio, pair manual payment capture with LabX Fraud Filter to block bad checkouts server-side before capture.

Keeping your store safely below the Shopify chargeback rate threshold is one of the most important operational metrics in e-commerce. Many merchants assume that as long as they submit tracking numbers, fight bogus claims, or refund suspicious orders after checkout, their payment gateway standing will stay healthy. Unfortunately, card networks do not grade your store on how many disputes you win—they grade you on how many disputes and fraud reports are filed in the first place.

Once your dispute activity crosses processor warning lines or breaches the Visa and Mastercard chargeback monitoring thresholds, the consequences escalate fast: per-dispute fees, rolling payout reserves, monthly network assessments, or losing your ability to accept credit cards altogether.

In this guide, we break down how processors and card networks calculate your dispute ratio, how the Shopify Payments chargeback fee works, why post-order cancellations still leak margin, and how to prevent friendly and criminal fraud before capture by combining manual payment capture with storefront bot filtering and server-side Cart and Checkout Validation Functions in LabX Fraud Filter. For a full overview of our two-layer architecture, read our Shopify fraud prevention guide.

What is the Shopify chargeback rate threshold and how do Visa and Mastercard measure it?

When merchants search for the Shopify chargeback rate threshold, they face two overlapping sets of guardrails: internal processor risk reviews (such as those enforced by Stripe, which powers Shopify Payments) and formal card network compliance programs operated by Visa and Mastercard.

As documented in Stripe’s guide to measuring disputes and excessive dispute activity, the credit card processing industry generally recognizes dispute activity above 0.75% as excessive—and a sudden spike or steep upward trend can trigger processor intervention, payout reserves, or account review even before you reach 0.75%.

At the card network level, Visa and Mastercard enforce monthly monitoring programs with specific count and ratio triggers. According to Stripe’s reference on dispute and fraud card monitoring programs, here is how the primary Visa and Mastercard chargeback monitoring thresholds work:

Program & Card NetworkRatio FormulaThresholds & Monthly TriggersNetwork Consequences
Processor Warning BenchmarkDisputes received in period ÷ captured payments0.75% dispute activity (or sudden upward spikes)Processor risk review, remediation plan, or rolling payout reserves
Visa Acquirer Monitoring Program (VAMP) — Disputes & Fraud(TC15 disputes + TC40 early fraud warnings) ÷ settled card-not-present payments from prior monthNon-compliant: ≥ 0.5% ratio and ≥ 5 VAMP count
Excessive (US, EU, UK, CA, AP, LAC): ≥ 1.5% ratio and ≥ 1,500 VAMP count (CEMEA: ≥ 2.2%, ≥ 150 count, $75,000 volume)
Per-event assessments on Excessive (and potentially Non-Compliant) tiers; double-counting if one order generates both a TC40 and TC15
Visa VAMP — Enumeration (Card Testing)Enumerated card-testing attempts (approved or declined) ÷ total authorizationsExcessive: ≥ 20% enumeration ratio and ≥ 300,000 enumerated transactionsMandatory card-testing mitigation and remediation plan
Mastercard Excessive Chargeback Merchant (ECM)Current month’s chargebacks ÷ preceding month’s captured Mastercard payments1.5%–2.99% chargeback rate and 100–299 chargebacks in a monthMonthly fines from month 2 ($1,000 to $100,000/month) plus $5/chargeback over 300 disputes; requires 3 consecutive months below threshold to exit
Mastercard High Excessive Chargeback Merchant (HECM)Current month’s chargebacks ÷ preceding month’s captured Mastercard payments≥ 3.0% chargeback rate and 300+ chargebacks in a monthEscalating monthly fines from month 2 ($1,000 to $200,000/month)
Mastercard Excessive Fraud Merchant (EFM)Current month’s fraud chargebacks (codes 4837/4863) ÷ preceding month’s e-commerce payments> 0.50% fraud rate (> 0.20% in AU), > $50,000 net fraud volume ($15,000 in AU), ≥ 1,000 payments, and low 3DS usageMonthly fines from month 2 ($500 to $100,000/month) until 3 consecutive compliant months

Three Calculation Traps That Catch Merchants Off Guard

  1. Dispute Activity vs. Dispute Rate: As explained in Stripe’s dispute measurement docs, card networks track dispute activity (disputes received this month divided by payments captured this month—or, for Mastercard, divided by last month’s captured payments). Because cardholders can file chargebacks up to 120 days after buying, a high-volume holiday month followed by a quiet January can spike your January ratio when December disputes land against January’s smaller sales denominator.
  2. Visa VAMP Counts Both Fraud Warnings (TC40) and Disputes (TC15): Under Visa’s VAMP rules, if a stolen card is used at checkout, the issuing bank may submit an Early Fraud Warning (TC40) and a formal dispute (TC15). Unless resolved through qualifying pre-dispute tools or Compelling Evidence 3.0, a single fraudulent transaction appearing in both TC40 and TC15 reports counts twice toward your VAMP count and ratio.
  3. Statement Descriptors Split Your Denominator: Visa tracks accounts by acquiring bank and the static prefix of your statement descriptor. Using different statement descriptors without a shared static prefix splits your transaction volume into smaller pools, making it easier for a few disputes to cross percentage limits.

How much does a Shopify Payments chargeback fee really cost your store?

When a cardholder opens a formal chargeback, the financial impact goes beyond the order total. Under Shopify’s chargebacks and inquiries policy, two deductions happen immediately:

  • Full reversal of the disputed amount: Shopify Payments deducts the disputed transaction total from your payout balance while the cardholder’s bank reviews the case.
  • The flat Shopify Payments chargeback fee: A dispute fee (for example, $15 USD for US merchants on Shopify Payments, with regional currency equivalents elsewhere) is debited alongside the order funds. (If the bank sends a preliminary inquiry instead of a formal chargeback, funds and fees are not immediately withdrawn.)

What happens next highlights why relying on dispute representment or post-capture refunds is a losing strategy:

  • If you lose the chargeback: You permanently lose the order revenue, the shipped inventory, the original non-refundable payment processing percentage fee, and the $15 Shopify Payments chargeback fee.
  • If you win the chargeback: Shopify Payments returns the disputed amount and refunds the chargeback fee. However, winning the dispute does not remove the chargeback from your Visa or Mastercard monitoring ratio. As noted in Stripe’s monitoring program guidelines, card networks count all disputes regardless of outcome.
  • If you cancel and refund an order after payment capture: Even if you catch a fraudulent order after checkout and refund it before the cardholder contacts their bank, payment processors keep their original transaction fee (typically 2.4%–3.9% + $0.30) on captured payments. Moreover, if the issuer still submits a Visa TC40 fraud report, the refunded payment still counts toward your VAMP metrics.

Why is blocking fraud before checkout better than fighting disputes or post-order refunds?

Because every captured fraudulent checkout either forfeits gateway processing fees (on a refund) or permanently increases your dispute ratio (on a chargeback), when you enforce your rules determines what you lose:

Fraud Defense StageExecution PointGateway Processing Fee Lost?Chargeback Ratio Impact?Can Attackers Bypass It?
Post-Dispute RepresentmentWeeks after fulfillmentYes (if lost)Counts in network ratio even if you winN/A — fraud already occurred
Post-Order Auto-Cancel (after Automatic Capture)Shopify Admin after order creationYes — processor keeps 2.4%–3.9% + $0.30 fee on refunded capturesAvoids dispute only if refunded before bank inquiry or TC40 reportN/A — payment already captured
Manual Payment Capture + VoidAfter authorization, before capture (Settings > Payments)No capture fee if voided before settlementAvoids settlement, though bot authorizations still count in Visa VAMP enumerationNo — funds settle only when captured
Storefront Blocking (Fraud Guard App Embed)Visitor’s browser on page load$0 lost — stops browser bots and scrapers earlyZero impact — no checkout or authorizationYes — bypassed by disabling JS or calling Cart APIs directly
Server-Side Checkout Protection (Shopify Validation Function)Shopify’s servers during cart/checkout submission$0 lost — rejects checkout before payment authorizationZero impact — blocks payment submission completelyNo — runs server-side on Shopify’s infrastructure

To protect your chargeback ratio across both stages, LabX Fraud Filter pairs Layer 1 storefront visitor blocking with Layer 2 server-side Checkout Protection:

  • Technical transparency on Layer 1 (Storefront): The Fraud Guard theme app embed runs in the visitor’s browser. Rules travel inside a Shopify metaobject with the page (zero extra network requests for non-geo rules, and one 30-minute cached GeoIP lookup per session for location, Tor, and datacenter checks). Because Shopify serves storefront pages from its CDN, no app can intercept requests before the browser receives the page—so an attacker who disables JavaScript or calls the Cart API directly can bypass storefront rules. Additionally, datacenter blocking is not consumer VPN blocking (it blocks cloud/hosting server IPs where automated bots run, leaving shoppers on residential VPNs unaffected), and storefront content protection (blocking right-click, copy shortcuts, and text selection) is a deterrent against casual copying, not a security barrier against OS screenshots or DevTools.
  • Unbypassable enforcement on Layer 2 (Checkout): Checkout Protection executes as a compiled Rust WebAssembly Shopify Cart and Checkout Validation Function (cart.validations.generate.run) on Shopify’s servers. As detailed in our walkthrough of Shopify Checkout Validation Functions for fraud, server-side checkout rules cannot be bypassed by disabling JavaScript, using checkout permalinks, or calling storefront APIs.

How do you prevent friendly and criminal fraud before capture on Shopify?

To prevent friendly and criminal fraud before capture, configure rules targeting both criminal fraud (stolen cards, carding bots, and reshipper schemes) and friendly or first-party fraud (repeat abusers who falsely claim non-delivery or dispute valid charges instead of requesting a return).

1. Stop Card Testing Bots Before They Trigger Visa VAMP Enumeration

High volumes of automated card testing—even declined attempts—count toward Visa VAMP enumeration monitoring, while the cards that pass turn into fraud chargebacks. To stop card testing attacks on Shopify:

  • Enable Storefront Bot, Tor, and Datacenter switches: In LabX Fraud Filter > Settings > Mitigator, turn on Block datacenter traffic, Block Tor traffic, Auto-block unknown bots, and Auto-block suspicious crawlers (with Unknown user agent and Headless hints). A built-in allowlist of 25 verified search engine, social, AI, and SEO crawlers runs before your bot switches and block rules so your SEO stays intact (see our traffic and bot blocking guide and bot protection user guide).
  • Block throwaway email domains at checkout: Storefront disposable-email blocking only covers newsletter signup forms. To block throwaway emails at checkout, go to Checkout Protection > Add rule, select Condition: Email and Match type: Contains, and click the built-in quick-add chips (+ @mailinator.com, + @tempmail.com, + @yopmail.com)—see our guide to blocking customer emails and domains on Shopify.

2. Block Triangulation, Freight Forwarders, and Drop Addresses Server-Side

Attackers running triangulation fraud on Shopify or reshipper schemes enter stolen billing details (to pass AVS) while shipping to third-party buyers or export warehouses. Build up to 100 server-side rules in Checkout Protection:

  • Postal code and street address blacklists (Zip & Address): Block industrial freight-forwarder postal codes (Zip — Exact match or Contains) and known drop-warehouse street lines (Address — Exact match).
  • Burner phone normalization (Phone): LabX Fraud Filter strips non-digit formatting characters on Shopify’s servers and matches pure digits (0–9), catching reformatted VoIP burner numbers automatically.
  • Unserviceable shipping countries (Country): Block checkouts targeting high-risk countries outside your supported delivery markets.

3. Lock Out Repeat Friendly Fraud Abusers Across Account and Guest Checkouts

When a buyer files an illegitimate “item not received” dispute despite confirmed delivery, native Shopify does not prevent them from ordering again. Block repeat friendly fraud across every identifier:

  • Block tagged accounts (Customer tag): Tag the customer profile in Shopify Admin (for example, chargeback-history) and create a Checkout Protection rule with Condition: Customer tag and Match type: Buyer has any of these tags. (LabX Fraud Filter only requests the optional read_customers permission when you save a Customer tag rule.)
  • Block their email, phone, name, and street address for guest checkout: Because a blocked user can log out and check out as a guest, add their exact email (Email), phone digits (Phone), delivery name (Name — Full Name), and street address (Address) to Checkout Protection. Both storefront and checkout layers fail open (blockOnFailure: false) so real customers are never locked out if a service or config is unreachable.

What operational checklist keeps your Shopify dispute ratio safely below 0.75%?

Combine pre-checkout blocking with Shopify’s recommended chargeback prevention practices and payment authorization controls:

  • Save your Admin bypass link first: In LabX Fraud Filter > Settings, open your store once with your rotatable Admin access link so your browser bypasses storefront rules while testing.
  • Turn on Storefront Datacenter, Tor, and Bot mitigation: Enable datacenter, Tor, unknown-bot, and headless-crawler blocking in Settings > Mitigator to cut off automated carding and scraping traffic early.
  • Add server-side Checkout Protection rules: Block disposable email domains, burner phone numbers, freight-forwarder ZIP codes, and repeat dispute abusers (Customer tag, Email, Phone, Address) on Shopify’s servers before payment submission.
  • Switch payment capture to Manual (or conditional hold): In Shopify Admin > Settings > Payments, set payment capture to Manual for high-value or mismatched-address orders so you can void suspicious authorizations before capture without losing gateway fees.
  • Standardize your Shopify Payments statement descriptor: Ensure your billing descriptor in Settings > Payments clearly shows your brand or domain name with a consistent static prefix so buyers recognize the charge and Visa does not split your VAMP denominator.
  • Ship with tracked delivery and signature confirmation: Upload tracking numbers promptly and require signature confirmation on high-ticket orders to deter friendly fraud claims.

Frequently asked questions

Does winning a chargeback dispute remove it from my chargeback rate?

No. While winning a dispute returns the disputed order amount and refunds the Shopify Payments chargeback fee, card network monitoring programs count every dispute filed against your ratio regardless of whether you win, lose, or accept it. Preventing the transaction before payment capture is the only way to keep it out of your dispute ratio altogether.

Does refunding a suspicious order after capture prevent a chargeback?

Issuing a full refund before a cardholder contacts their bank usually prevents a dispute, though processors keep their original transaction processing fee on captured orders. However, if a cardholder has already initiated a dispute or if an issuer submits an Early Fraud Warning (TC40) on a Visa card, refunding the order does not remove that fraud report from your Visa VAMP count.

Can fraudsters bypass storefront blocking rules to place orders on Shopify?

Yes, if you rely only on storefront rules. Storefront blocking runs in the visitor browser via the Fraud Guard theme app embed, so disabling JavaScript or sending requests directly to the Shopify Cart API bypasses browser scripts. Pairing storefront rules with server-side Checkout Protection—which runs as a Shopify Cart and Checkout Validation Function on Shopify servers—ensures your checkout rules cannot be bypassed.

How do I stop repeat friendly fraud buyers from checking out again?

Tag the customer account in Shopify Admin (for example, chargeback-history) and add their email address, phone number, and street address or ZIP code to server-side Checkout Protection in LabX Fraud Filter. This blocks both logged-in repeat attempts and guest checkouts using the same contact or delivery details before payment can be submitted.

Sources

  1. Stripe Documentation — Dispute and Fraud Card Monitoring Programs (VAMP & ECP)
  2. Stripe Documentation — Measuring Disputes and Excessive Dispute Activity
  3. Shopify Help Center — Chargebacks and Inquiries
  4. Shopify Help Center — Preventing Chargebacks and Inquiries
  5. Shopify Help Center — Payment Authorization and Capture
  6. Shopify Dev Docs — About Cart and Checkout Validation Functions

Part of our guide: Shopify fraud prevention →

Put your first blocking rule live in minutes

Install LabX Fraud Filter free on Shopify, turn on the Fraud Guard embed and add your rules.

Install free on Shopify

Free plan available