Alerts Don't Protect Your VAMP Ratio: What Sellers Miss

The catch, as FeeDecoder states it Why a TC40 matters even with no chargeback Why this article hedges the claim What to buy alerts for instead What can actually move the numerator FAQ

The catch, as FeeDecoder states it

Chargeback alerts sound like prevention. When a customer starts a dispute, Ethoca (Mastercard issuers), Verifi CDRN (Visa issuers) and Visa's Rapid Dispute Resolution (RDR) give you a 24-to-72-hour warning — or, in RDR's case, act automatically under rules you set — so you can refund and stop the dispute becoming a formal chargeback. FeeDecoder's October 2026 alert-fee analysis calls that trade by a sharper name: chargeback conversion, not chargeback prevention. You trade the dispute fee and the chargeback count for an alert fee and a refund. And then comes the catch that changes the value proposition, in FeeDecoder's words: alerts from Ethoca, CDRN and RDR still count toward your VAMP ratio, because the TC40 fraud report is filed even when the chargeback itself is prevented. Only Order Insight, FeeDecoder says, can potentially prevent TC40s, by resolving the inquiry before it becomes a dispute at all.

If that claim is right, it reframes the purchase completely. A merchant buying alerts to stay under a monitoring threshold — to protect the account, not just the month's fees — is buying the wrong tool for that job. FeeDecoder's conclusion follows directly: buy alerts for fee avoidance, not ratio protection. They protect your wallet from fees, not your account from monitoring. But "if that claim is right" carries real weight here, because the evidence behind it is thinner and more contested than the confident phrasing suggests. The rest of this article keeps the claim visible, labels it honestly, and shows what to do given the uncertainty.

Why a TC40 matters even with no chargeback

To see why the claim matters, you need the VAMP formula, as stated in this site's own VAMP threshold guide for merchants: VAMP ratio = (TC40 fraud reports + TC15 non-fraud disputes) divided by settled card-not-present transactions, count-based, not dollar-weighted. A TC40 is an issuer-reported fraud notification; a TC15 is the dispute itself. One fraudulent transaction that is both reported and disputed therefore counts twice. And a TC40 can count without any chargeback ever posting.

The merchant line that alerts are supposedly bought to protect is, since April 1, 2026, 1.5% with at least 1,500 fraud reports and disputes in the month in the standard regions (US, Canada, Europe, Asia-Pacific, Latin America and the Caribbean); in CEMEA the line is 2.2% with 150 events plus USD 75,000. Those figures are re-verified here from the live VAMP guide on this site — this article states no other threshold. Winning a dispute, the same guide notes, recovers the money but leaves the ratio entry in place. So the question FeeDecoder raises is precise: when an alert converts a would-be chargeback into a refund, does the TC40 side of the entry survive? If it does, the prevented chargeback removed only the TC15 half of a fraud case — or, for a fraud-coded case, possibly neither half in full.

Run your own numbers before deciding anything: the VAMP Threshold Checker computes your ratio and headroom against the 1.5% line, and the Chargeback Alert ROI Calculator — the companion tool for this article — prices alerts against the fees they actually avoid.

Why this article hedges the claim

This is the section a merchant should read before quoting the headline to anyone. FeeDecoder's TC40 claim is a secondary claim, hedged, not a Visa network rule, for three reasons found while checking it on November 2, 2026.

First, no primary confirmation was found. Verifi's and Ethoca's primary documentation was checked at build, and no Verifi or Ethoca primary page confirming the blanket version — that Ethoca, CDRN and RDR alerts always leave the TC40 in place — was found. FeeDecoder's analysis cites no Visa rulebook passage for the claim either; Visa's rulebooks are not public. A claim about how a network counts events, sourced only to a fee explainer, cannot be stated as network rule.

Second, other secondary sources describe the opposite treatment. Checkout.com's scheme-monitoring documentation lists disputes resolved within the same month through CDRN, Ethoca, RDR and Verifi among the exclusions from its VAMP counts. Another secondary guide states the reverse — that a dispute resolved through a pre-dispute alert never posts as a counted TC15 — while agreeing the TC40 side is the open question. These sources cannot all describe the same rule in the same period, which is itself evidence that treatment has varied by product, by timing, or by data extract.

Third, the treatment has changed over time. A March 2025 Verifi announcement, reported by MidMetrics, said Visa would begin including disputes with corresponding TC40 records resolved via RDR and CDRN in VAMP calculations, reversing an earlier position that such resolved disputes would not count. A merchant reading a 2024 guide and a merchant reading FeeDecoder in October 2026 may therefore both be accurately quoting their source — for different periods. And a fourth caution: VAMP is a Visa program counting Visa card-not-present traffic, while Ethoca alerts cover Mastercard issuers. An Ethoca alert cannot itself create a Visa TC40. FeeDecoder lumps Ethoca in with the Visa-side products; the TC40 question, strictly, bites on Visa-side CDRN and RDR fraud reports. Quote the claim with that scope correction attached.

What is broadly agreed, and safe to act on: an alerted-and-refunded dispute never posts as a TC15 chargeback, so alerts do reduce the chargeback count and the dispute fees attached to it. What is not settled by primary evidence in this build is whether the TC40 side always survives for CDRN and RDR fraud cases. Until your acquirer confirms the treatment for your traffic and your month's data extract, do not budget alerts as ratio protection, and do not tell a board or an acquirer that they are.

What to buy alerts for instead

None of this makes alerts worthless. It makes them a fee-avoidance purchase, and fee avoidance can be priced honestly. FeeDecoder's October 2026 dated price points — attributed, provider-quoted, and variable by provider — put RDR alerts at around $12 through discount providers (competitors listing around $19) and Ethoca alerts at $18 to $29, with a typical range of $15 to $40 per delivered alert plus a monthly platform fee through most processors. Set those against the dispute fee avoided, which FeeDecoder puts at $15 to $25, plus the lost sale on a refund either way. The honest arithmetic is cost per prevented chargeback: total monthly alert fees divided by chargebacks prevented. FeeDecoder's framework is blunt about the rest of the cost too — on a $100 transaction "prevented" via an alert, the merchant still refunds the sale and absorbs product, fulfilment, marketing and processing costs, so the prevented dispute is not a saved sale. Use the Chargeback Alert ROI Calculator to run that division on your own volumes before renewing or expanding an alert subscription.

FeeDecoder's decision framework, attributed here rather than adopted as rule, is: use RDR's automatic refunds for low-value volume where review labour exceeds the sale, and manual review (Ethoca or CDRN alerts) for high-value cases; track alert coverage rate, prevention rate and cost per prevented chargeback; and if coverage is under roughly half, expand issuer enrollment before spending more. This article states no prevention rate and no win rate for alerts — published prevention percentages vary by vendor, period and traffic mix, and none was verified from a primary source for this build. Your own coverage and prevention rates, from your own processor data, are the only rates worth budgeting on.

What can actually move the numerator

If the goal is the ratio itself rather than the month's fees, the levers with support in the sources checked here are narrower — and slower — than buying alerts:

Resolve inquiries before they become disputes. Order Insight lets issuers pull richer merchant data while the cardholder is still asking questions, and FeeDecoder presents it as the only product that can potentially prevent TC40s. That "potentially" is load-bearing: it is FeeDecoder's hedged claim, supported in direction by a secondary guide noting Order Insight often avoids the TC40 entirely, but not confirmed as a network rule in this build. Treat it as the most promising pre-dispute lever, and confirm its effect on your own VAMP extract before relying on it.

Qualifying Compelling Evidence 3.0. This site's VAMP guide states that only pre-dispute solutions and qualifying Compelling Evidence 3.0 fraud can be excluded from the ratio, depending on timing. For fraud-coded disputes, CE 3.0 evidence — prior undisputed transactions from the same card and customer — is the documented route to invalidating the dispute, and secondary guides describe it as one of the few controls that can clear both sides of the TC40-plus-TC15 double count. It requires the evidence to be captured at checkout, so it is a build, not a purchase.

Root-cause prevention. The durable fix is the unglamorous list FeeDecoder itself ends on: clear billing descriptors, easy cancellations, fast customer service, accurate product pages. A dispute never filed has no TC40 and no TC15. That is also the lesson of the Justt 2026 Benchmark, where service disputes — not fraud — are now nearly a quarter of contested chargebacks: the disputes most worth preventing are the ones your own service flow creates.

Bottom line for sellers: buy alerts to dodge dispute fees, price them with the Alert ROI Calculator, watch your ratio with the VAMP Threshold Checker, and do not let an alert subscription substitute for the work that actually keeps the ratio down. If a vendor tells you alerts protect your VAMP ratio, ask them to show you the Visa rule or your own extract proving it — and if they cannot, treat the claim the way this article treats FeeDecoder's: interesting, plausible, unproven.

FAQ

Do chargeback alerts protect my VAMP ratio?

Not certainly, and that uncertainty is the point of this article. FeeDecoder claims Ethoca, CDRN and RDR alerts still count toward VAMP because the TC40 fraud report is filed even when the chargeback is prevented. Other secondary sources describe exclusions for disputes resolved through those same products, and no Verifi or Ethoca primary document confirming FeeDecoder's blanket version was found for this build. Treat alerts as fee avoidance, not proven ratio protection, until your acquirer confirms the treatment for your traffic.

What is a TC40, and why does it matter separately from a chargeback?

A TC40 is an issuer-reported fraud notification to Visa. A TC15 is the dispute (chargeback) itself. Visa's VAMP ratio counts both: (TC40 fraud reports + TC15 disputes) divided by settled card-not-present transactions. One fraudulent transaction can therefore count twice, and a fraud report can count even when no chargeback ever posts. That is why preventing the chargeback alone may not remove the whole VAMP entry.

What actually lowers the VAMP numerator?

Three things with support in this site's own VAMP guide and the sources cited here: resolving an inquiry before it becomes a dispute (Order Insight is presented by FeeDecoder as the only product that can potentially prevent TC40s, hedged as above), qualifying fraud evidence under Compelling Evidence 3.0, and root-cause prevention — clear descriptors, easy cancellations and fast customer service — that stops disputes being filed at all. Winning a dispute does not remove its ratio entry.