Do RDR resolutions count as chargebacks?
An RDR resolution refunds a disputed transaction before a chargeback is ever filed. Because no chargeback exists, it does not add to your chargeback count. Because it is a pre-dispute resolution, Visa's own VAMP fact sheet also lets it stay out of your dispute ratio, subject to one timing rule worth understanding before you rely on it. That is a different outcome from winning a representment, which returns the same money but leaves the dispute sitting in the ratio it already joined.
What actually happens when RDR resolves a dispute
Rapid Dispute Resolution is Verifi's rules engine, built on the Visa network. You configure accept or decline rules ahead of time using attributes Verifi exposes, including issuer BIN, transaction date, amount, currency, and dispute condition code. Verifi describes the mechanism plainly: merchants "automatically resolve Visa disputes with a customizable decision engine that instantly credits the cardholder before a chargeback is initiated," and the case is resolved "without the merchant ever needing to login into the system" (Verifi, Resolve Disputes and The Power of CDRN and RDR, both checked July 22, 2026).
The resolved case routes through your acquirer, not around it: "RDR pre-disputes route through to the acquirer, where the pre-dispute is automatically resolved by Visa/acquirer per the rules defined by the merchant." That routing detail matters, because it is what makes the resolution a formal, acquirer-visible event rather than a quiet refund you issued on your own.
This all happens in the pre-dispute window, the same stage CDRN and Ethoca alerts operate in, before the issuing bank files anything as a chargeback. A chargeback alert gives you a case to act on manually. RDR skips that step and resolves the accepted case automatically, against rules you wrote in advance.
Does an RDR resolution count as a chargeback?
No. A chargeback is a specific, filed event: the issuer debits the acquirer, the acquirer debits you, and a record enters the dispute count that feeds Visa's monitoring programs. RDR resolves the case before any of that happens. There is no filing, so there is nothing counted.
Compare that with representment, where a chargeback has already been filed, argued, and decided in your favor. The chargeback exists the moment it is filed, days or weeks before you submit evidence. Winning changes who keeps the money. It does not undo the filing.
Redo's pre-filing deflection layer exists because of that distinction. It ingests RDR, CDRN, and Ethoca signals through Disputely's network integrations and resolves them against the Shopify order before a chargeback can be filed at all, rather than trying to win one after the fact.
Does it keep the dispute off my VAMP ratio?
Usually, yes, and this is where the visible guides on this topic tend to get vague. Visa's Acquirer Monitoring Program fact sheet defines the ratio as a single count:
VAMP ratio = Count of [Fraud (TC40) + Disputes (TC15)] ÷ Count of Settled Transactions (TC05).
It then lists two exclusions, in the fact sheet's own wording: the ratio "excludes disputes resolved through pre-dispute solutions, contingent on the timing of the data extract," and separately excludes TC40 fraud that qualifies for Compelling Evidence 3.0, on the same timing condition (Visa, Acquirer Monitoring Program fact sheet, checked July 22, 2026).
RDR is a pre-dispute solution by definition: it resolves before a chargeback initiates, which is the exact language Visa uses to define the exclusion. Verifi states the outcome directly from its own side: "Disputes resolved before a chargeback initiates do not count against Visa's dispute ratio" (Verifi, Resolve Disputes, checked July 22, 2026).
The condition worth taking seriously is "contingent on the timing of the data extract." Visa pulls the data used to calculate the ratio on its own schedule, and a resolution that lands very close to that extract can be swept into the count before the exclusion is applied to it. The practical read is not "RDR always keeps it off," and it is not "nobody can know." It is that a resolution earlier in the reporting cycle is on much safer ground than one that lands in the last day or two of it. Ask your acquirer, in writing, how they see this timing on their end.
RDR resolution versus a won representment, side by side
| RDR resolution | Won representment | |
|---|---|---|
| When it happens | Before a chargeback is filed | After a chargeback is filed, argued, and decided |
| Chargeback record created | No | Yes, at filing, regardless of outcome |
| Money outcome | Cardholder is credited, transaction settled | Merchant keeps the funds |
| Counts toward the VAMP ratio | Generally excluded, contingent on data extract timing | Counted, no exclusion applies |
| Requires evidence assembly | No, resolved by rule | Yes, roughly 20 to 45 minutes per case |
| Who decides the outcome | The merchant's own pre-set rule | The issuer, based on submitted evidence |
That table is the whole argument in why winning a chargeback does not fix your dispute ratio, applied to one specific mechanism. Representment is a revenue lever. RDR, when it fires early enough, is a ratio lever.
The honest limitation
RDR is not a substitute for prevention, and it is not free of its own gaps.
Enrollment is a real gate. RDR requires registering your Visa BIN and CAID with Verifi, and merchants on a shared BIN through an aggregating acquirer often cannot enroll at all. Confirm your BIN and CAID situation with your acquirer before assuming RDR is available to you.
A badly scoped rule refunds orders silently. Because RDR resolves without a login, a rule set too broadly credits cardholders on cases you might have won on evidence, and nothing logs the outcome for you to review later. Set narrow rules and audit what they accepted monthly.
The refund happens regardless of whether the customer would have escalated. Some pre-disputes get abandoned by the cardholder or resolved by the issuer without ever becoming a chargeback. RDR credits the cardholder anyway, and you never learn which cases would have gone away on their own.
Coverage is Visa only. RDR does not see Mastercard, Amex, or Discover disputes. For those, CDRN or an Ethoca feed is doing the work, if anything is.
Redo's Alerts product is not a self-serve signup. It is a demo and partner-program product, priced against your card mix and dispute volume, because coverage depends on which networks and issuers actually reach you. Nothing about it is free, and nothing here should be read as implying otherwise.
Frequently asked questions
Does an RDR resolution count as a chargeback?
No. RDR resolves the case during the pre-dispute window, before the issuer files anything as a formal chargeback. Since no chargeback is filed, no chargeback record exists to count.
Does RDR keep a dispute off my Visa VAMP ratio?
Generally yes. Visa's Acquirer Monitoring Program fact sheet excludes disputes resolved through pre-dispute solutions from the ratio, contingent on the timing of the data extract. RDR resolves before a chargeback initiates, which is the definition of a pre-dispute solution, so it typically qualifies for that exclusion.
Is an RDR resolution the same as winning a chargeback?
No. Winning a representment means a chargeback was filed, counted, argued, and decided in your favor after the fact. RDR prevents the chargeback from being filed at all, so there is nothing in the count to begin with.
Does RDR only work on Visa transactions?
Yes. RDR is a Visa-only product operated through Verifi. Mastercard, Amex, and Discover disputes route through other mechanisms, such as CDRN or issuer-specific alert networks, if they are covered at all.
The test I'd run: pull the RDR-resolved cases from last month and check two things against your acquirer's own reporting, not just your processor dashboard. First, whether each one actually landed inside the pre-extract window rather than at the edge of it. Second, whether your acquirer's VAMP count for that month matches what you would calculate from Visa's formula yourself. If the two disagree, that gap is worth a written answer before you build a plan around the exclusion.