Rapid Dispute Resolution (RDR): What Visa's Rules Say
Visa defines RDR as automating the acceptance of liability. Here is the double refund trap and the 60 day clock that most RDR explainers leave out.
By Jeffrey Anderson
- Visa's glossary defines Rapid Dispute Resolution as a service that automates the acceptance of liability for a disputed transaction. It is a faster concession, not a defense.
- Outside the glossary, RDR appears in four places in the public rulebook, and all four deal with the cardholder being credited twice.
- If you refund a customer and RDR then auto-accepts the same dispute, Section 1.10.1.1 explicitly removes the usual protection: the RDR case is carved out of the normal double-credit route.
- Recovery runs on a tighter clock than any other compliance case. The pre-compliance attempt is due 29 calendar days from the dispute processing date and the filing 60 days, against a 90 day default.
- An RDR resolution does not count toward your VAMP ratio. Visa's fact sheet excludes disputes resolved through pre-dispute solutions from the calculation, which is the strongest argument for using RDR when you are near a threshold.
- Changing merchant name, data, or performance to dodge the monitoring programs can cost the acquirer USD 25,000 per merchant per month and permanently disqualify the merchant and its principals.
Rapid Dispute Resolution is a Visa service that accepts liability for a disputed transaction on your behalf, automatically, before a chargeback is ever filed. That is worth sitting with. RDR is not a way to win disputes. It is a way to concede them faster and cheaper.
Visa's own glossary is blunt about it. Rapid Dispute Resolution is "a pre-dispute resolution service that provides the ability for Merchants and Payment Facilitators to automate the acceptance of liability for a disputed Transaction" (Visa Core Rules and Visa Product and Service Rules, 18 April 2026, Glossary).
Most explanations of RDR skip that sentence. It changes what the tool is for.
What You Are Actually Buying
RDR sits in front of the dispute. You agree a rule set with your acquirer: refund anything under a ticket threshold, refund certain dispute conditions, refund certain card types. When a matching dispute arrives, the credit goes out and the case closes before it becomes a chargeback.
The upside is genuine. No representment package to build, no acquirer chargeback fee, and the cardholder has their money in hours rather than weeks.
The cost is just as genuine. Every RDR resolution is a refund you gave without ever seeing the claim. If it was friendly fraud, you paid it. If you had proof of delivery, you never got to use it.
Four Rules, One Failure Mode
Outside the glossary entry, RDR appears in exactly four places in the public rulebook. All four are about the same thing going wrong: the cardholder getting paid twice.
That is the risk the network wrote rules for, so it is the risk worth planning around.
The Double Refund Trap
The sequence is ordinary. You refund a customer on Monday. On Tuesday they dispute anyway, because the credit has not landed on their statement yet or they simply forgot. Your RDR rule fires, accepts liability, and issues a second credit. The cardholder is now whole twice over and you are out two sales.
Visa normally closes this door. Section 1.10.1.1 states that a cardholder must not be credited twice as a result of both a dispute and a merchant credit, and that if it happens it must be resolved through the dispute process rather than the compliance process. Then it adds a footnote: "This does not apply to Disputes resolved using Rapid Dispute Resolution" (ID# 0003287).
RDR is the carve-out. The dispute was auto-accepted, so there is no live dispute left to work with. Compliance is the only road back.
The 60 Day Clock
Table 11-152 (ID# 0030228) sets the condition. The issuer or cardholder was reimbursed twice for the same transaction because of both a credit or reversal processed on or before the dispute processing date, and a dispute processed through RDR. Your acquirer then has to certify the dates and amounts of both.
The deadlines are where this gets sharp.
| Step | RDR credit issued | Every other compliance case |
|---|---|---|
| Pre-compliance attempt | 29 calendar days from the dispute processing date | At least 30 calendar days before filing |
| Accept responsibility and credit | 30 calendar days from the pre-compliance attempt date | 30 calendar days from the pre-compliance attempt date |
| Compliance filing | 60 calendar days from the dispute processing date | 90 calendar days from the processing or violation date |
Read the first row twice. In an ordinary compliance case, the 30 days is a minimum waiting period before you may file. For RDR it flips into a deadline: 29 days from the dispute processing date, not 29 days from whenever you spot the problem.
The filing window is 60 days instead of 90. RDR gives you a third less time to recover a double refund than any other compliance case in that table.
That is a bad combination, because RDR resolutions are the ones you are least likely to notice. Not touching them is the entire point of the service.
Does RDR Count Toward Your VAMP Ratio?
It doesn't, and that's the strongest argument for using it.
The Core Rules are no help here. Section 10.4.3.1 says only that Visa identifies an acquirer under the Visa Acquirer Monitoring Program "if it meets requirements, as specified in the Visa Acquirer Monitoring Program Guide" (ID# 0029286), and that guide isn't public.
Visa's own VAMP fact sheet is. It defines the VAMP ratio as fraud (TC40) plus non-fraud disputes (TC15) divided by the count of settled transactions (TC05), and then lists the exclusions. The first one is disputes resolved through pre-dispute solutions (Visa Acquirer Monitoring Program fact sheet).
RDR is a pre-dispute solution. Visa's glossary defines it as exactly that. So a dispute RDR resolves is excluded from the ratio that decides whether you enter the program.
That is the real trade. You give up the sale, and in exchange the dispute doesn't count against you. Whether that's worth it depends entirely on how close to a threshold you are.
One thing the rulebook is entirely clear about is the line you must not cross. Section 12.5.3.2 (ID# 0030702) allows Visa to assess the acquirer USD 25,000 per merchant per month, and to permanently disqualify the merchant and its principals, if merchant name, merchant data, or merchant performance was changed in any way to circumvent the monitoring programs.
Where RDR Earns Its Place
It fits a narrow set of cases well:
- Small tickets where building a representment costs more than the sale
- Categories where you would refund on request anyway
- Disputes you would lose regardless, so the fee is the only saving left
- A merchant who needs dispute volume down now and can afford to buy it down
It is the wrong tool when the real problem is upstream. Auto refunding disputes caused by a confusing billing descriptor means paying for that confusion forever. Fix the descriptor and the disputes stop instead of repeating.
It is also the wrong tool when you have a defensible case. Representment can recover the sale. RDR never does.
Turn It On With Guardrails
Three habits keep RDR from costing more than it saves.
Cap the ticket. Set the threshold below what a representment actually costs you and route everything above it through the normal process.
Reconcile refunds daily. The double refund trap only bites when a manual credit and an RDR resolution cross paths. A daily match of your refund log against your RDR log catches those inside the 29 day window rather than after it.
Ask about the ratio and write down the answer. RDR changes how a dispute resolves. Whether it changes your chargeback ratio is your acquirer's answer to give, not a vendor's.
Frequently Asked Questions
Does RDR stop a chargeback?
It stops the chargeback from being filed, by issuing the credit and accepting liability first. Visa defines the service as automating the acceptance of liability, so the money still leaves your account.
Can I fight an RDR resolution?
No. Accepting liability closes the dispute. The only route back is a compliance filing, and only in the narrow case where the cardholder was credited twice.
What if I had already refunded the customer?
Table 11-152 covers exactly that. If a credit or reversal was processed on or before the dispute processing date and the dispute then ran through RDR, your acquirer can file for compliance with certification of the dates and amounts of both.
How long do I have to recover a double refund?
The pre-compliance attempt is due 29 calendar days from the dispute processing date, and the compliance filing 60 calendar days from that same date. Both are tighter than the 90 day default.
Does RDR count toward VAMP?
No. Visa's VAMP fact sheet says the ratio excludes disputes resolved through pre-dispute solutions, and RDR is one. The dispute still happened, but it does not count toward the ratio that puts you in the program.
Is RDR the same thing as a dispute alert?
No. An alert tells you a dispute is coming and leaves the decision with you. RDR makes the decision in advance and acts without you.
Not sure whether RDR belongs in your chargeback defense stack, or whether you would do better fixing what is causing the disputes? Apply free or talk to a specialist and we will look at your actual dispute mix first.
Jeffrey Anderson, Merchant Placement Specialist
Merchant placement specialist at Gray Merchants. Jeffrey works directly with acquiring-bank underwriting teams across the firm’s 70+ banking relationships to place high-risk and hard-to-place businesses, structure multi-MID accounts, and keep flagged merchants processing. His writing draws on the placement files he works every week: what underwriters ask for, why accounts get declined, and what keeps an approved account open.