Does Rapid Dispute Resolution (RDR) Remove Chargebacks from Your VAMP Ratio?
Shawn Kelley · Last updated August 2026
If you’re on a chargeback team and you’ve had alerts running for two full quarters, seen your dispute counts fall, but your ratio barely moves? It’s probably because of this small distinction.
The statement that RDR “protects your chargeback ratio” is only half right, and the wrong half is the one that gets you placed in a monitoring program.
First, some chargeback vocabulary
This subject is buried under acronyms, most of which are internal Visa file codes that leaked into vendor marketing. Just in case you aren’t familiar, here are the definitions for the key chargeback terms we’re discussing in this article:
The three records that decide your VAMP ratio
Your VAMP ratio is built from three settlement records. They are named after the transaction codes Visa uses internally, which is why they sound like part numbers.
| Record | What it actually is | When it gets created |
|---|---|---|
| TC40 | A fraud report. The cardholder’s bank tells Visa a transaction was fraudulent. | When the cardholder calls their bank and says “I didn’t make this charge,” whether or not they ever file a dispute. |
| TC15 | A dispute record. The formal chargeback against you. | The moment the dispute is filed. Nothing that happens afterward removes it. |
| TC05 | A settled card-not-present sale. Your denominator. | Every completed online or over-the-phone transaction you process. |
There are two consequences a lot of teams discover late:
A single transaction can generate both a fraud report (TC40) and a dispute record (TC15). This means one disputed transaction that the bank flagged as fraud counts against you twice. So, if you’re reconciling against your own dispute log, you’ll consistently under-predict your actual ratio, because the dispute log doesn’t contain the fraud reports.
A TC40 fraud report exists whether or not you lose a dollar. It records a phone call, not a loss. If you track this by revenue impact, you will miss most of them.
How the VAMP ratio is built
VAMP is count-based, not dollar-based, and covers card-not-present transactions only:
Because the denominator is a transaction count rather than revenue, average order value is irrelevant. That means if you average $70 orders or you average $700 orders, you have the same regulatory pressure at the same transaction count. Raising prices does nothing for your ratio. Selling to fewer, unhappier customers makes it worse.
What each chargeback prevention tool actually removes
| Tool | Removes TC15 | Removes TC40 | Net effect on your ratio |
|---|---|---|---|
| RDR (Rapid Dispute Resolution) | Yes | No | Partial — fraud-flagged transactions still count |
| CDRN (Verifi alerts) | Yes | No | Partial — same limitation |
| Order Insight with CE 3.0 | Yes, when the bank accepts it | Yes | Full removal from the numerator |
| Winning a representment | No | No | None |
The last row is the one that reorders priorities, and it is worth stating flatly: winning a chargeback does not lower your chargeback ratio.
The dispute record was created when the dispute was filed. Fighting it and winning returns the money and leaves the record where it is. So, you can win most of your disputes and still walk into an “Excessive” classification.
The 2026 VAMP thresholds
Since April 1, 2026, the merchant Excessive threshold is 1.50% in AP, Canada, EU, and the US — down from 2.20% — with fines of $8 per fraudulent or disputed transaction, administered through your acquiring bank.3 The threshold is regional: LAC was already at 1.50% and didn’t move, and CEMEA remains at 2.20%. Check which region your acquirer measures you under before assuming the 1.50% figure applies to you.
In the regions where it moved, the threshold dropped 70 basis points. A merchant that was comfortably compliant at 2.20% and changed nothing operationally can be formally Excessive today on identical volume.
There is a separate Enumeration threshold of 20.00% covering card testing — what Visa calls an enumeration attack, the systematic submission of card-absent transactions into the Visa system to fraudulently obtain or validate payment information.4 It applies only above a floor of roughly 300,000 enumerated transactions per month, and Visa identifies those transactions using its Visa Account Attack Intelligence (VAAI) score rather than a plain count of declined authorizations. The practical effect: a card-testing attack can push you toward the threshold on attempted volume alone, with no fraudulent charge ever clearing and no dispute ever filed.
Your acquirer’s limits are tighter than yours
Visa enforces the merchant threshold at Excessive. Acquiring banks face their own, far stricter ones: an Above Standard threshold of 0.50%, enforced since January 1, 2026, and Excessive at 0.70% — measured across the acquirer’s entire merchant portfolio rather than per merchant.3
That gap explains something that confuses a lot of people: the remediation demand that arrives when you are nowhere near 1.50%.
If you’re sitting at 1.0%, you’re comfortably inside Visa’s merchant limit while actively pushing your acquirer toward a program tier of their own. The constraint that reaches you first is almost never the network’s rule about you. It is your bank’s rule about itself.
What to do with this
Find out how many of your disputes carry a fraud report. If a meaningful share do, an RDR-only program is paying to remove one of the two entries in your numerator. Your acquirer or processor can give you the overlap. Pull it before the next renewal.
Route fraud-coded transactions toward CE 3.0 instead of auto-refunding them. Bank acceptance through Order Insight is the only path that clears both records, which turns dispute response into a compliance lever rather than a recovery function.
Check whether your “fraud” disputes are actually fraud. Mis-coding is the most common finding in this data. In one enterprise ecommerce case, 90% of disputes tagged as fraud were first-party misuse. That means a real customer who received the order and disputed anyway. The mis-tag pushes transactions into the fraud count and simultaneously points your response strategy at the wrong evidence.
Model the ratio forward rather than backward if you aren’t already. Last quarter’s ratio was measured against the old threshold. Rerun it against 1.50% before deciding you’re fine.
Related
- Understanding VAMP Thresholds: The Complete Merchant Reference
- Visa’s VAMP Program in 2026: The Merchant Guide
- Chargeback Glossary
Sources
-
Visa Core Rules and Visa Product and Service Rules, 18 April 2026 edition, §10.4.3.1 “Visa Acquirer Monitoring Program (VAMP),” Rule ID 0029286, p.633. visa-rules-public.pdf ↩
-
Visa Core Rules and Visa Product and Service Rules, 18 April 2026 edition, Glossary, “Rapid Dispute Resolution,” Rule ID 0031030, p.890. ↩
-
Visa, “Visa Acquirer Monitoring Program Overview” (fact sheet), corporate.visa.com, accessed August 2026. PDF ↩ ↩2
-
Visa Core Rules and Visa Product and Service Rules, 18 April 2026 edition, Glossary, “Enumeration Attack,” Rule ID 0024631, p.857. ↩
08Frequently asked questions
What is RDR?
Rapid Dispute Resolution (RDR) is a Visa service that automatically refunds a disputed transaction according to rules the merchant sets in advance, before the dispute is formally filed. The merchant accepts the loss deliberately in order to avoid the chargeback.
What is the difference between TC40 and TC15?
TC40 is a fraud report filed by the cardholder’s bank when a cardholder reports a transaction as fraudulent, whether or not a dispute follows. TC15 is the record of the dispute itself. Both count in the VAMP numerator, and a single transaction can generate both.
Does RDR count against VAMP?
Partially. RDR removes the TC15 dispute record but not the TC40 fraud report, so a fraud-coded transaction resolved through RDR still counts in the VAMP numerator.
Does winning a chargeback lower my VAMP ratio?
No. The TC15 dispute record is created when the dispute is filed, so winning at representment recovers the revenue but leaves the ratio unchanged. Only Compelling Evidence 3.0 accepted through Visa Order Insight removes entries from the VAMP numerator.
What is the VAMP threshold in 2026?
The merchant Excessive threshold has been 1.50% since April 1, 2026, down from 2.20% — in AP, Canada, EU, and the US. LAC was already at 1.50% and didn’t change; CEMEA remains at 2.20%. Fines run $8 per fraudulent or disputed transaction. Acquiring banks are held to tighter numbers than merchants, measured across their whole portfolio rather than per merchant: 0.50% Above Standard and 0.70% Excessive.
Shawn Kelley is the co-founder of Disputed. He ran dispute operations at SeatGeek before starting the company.