On this page
- How it works
- Coverage (as-of 2025)
- Pricing (as-of January 2025)
- Decision mechanisms
- 1. Verifi-hosted Decision Engine (rules)
- 2. Decision API (merchant-hosted, beta from ~2025)
- 3. Notifications API
- RDR vs. CDRN vs. Ethoca
- RDR and VAMP
- Effectiveness benchmarks (as-of 2025)
- Counter-narrative: does RDR "save the sale"?
- Setup and onboarding (as-of 2025)
- Key terms
- Frontier links
RDR (Rapid Dispute Resolution)
RDR (Rapid Dispute Resolution)
RDR is Visa's automated pre-dispute resolution programme, operated by Verifi (a Visa subsidiary acquired in 2019). Launched in 2021, RDR intercepts card disputes before they escalate into formal Chargeback|chargebacks by automatically refunding cardholders whose disputes match merchant-configured rules — entirely within Visa's dispute processing platform (Visa Resolve Online (VROL)). For ecommerce merchants, RDR is the primary tool for reducing Visa dispute ratios at scale without manual intervention.
How it works
When a cardholder contacts their issuer to dispute a charge, the issuing bank logs the pre-dispute in VROL rather than immediately filing a formal chargeback. VROL checks whether the merchant is enrolled in RDR and, if so, evaluates the dispute against the merchant's pre-configured rules. If the dispute matches a rule, an automatic refund is issued immediately and the dispute is closed — no chargeback is posted. If no rule matches, the dispute follows the standard chargeback process. (ChargebackStop, March 2025, updated June 2026)
The process resolves in real time — Verifi's hosted decision engine completes each case in under 3 seconds (as-of March 2025). (Verifi Decision API FAQ, primary source, modified 2025-03-20)
Coverage (as-of 2025)
- Network: Visa only. RDR does not cover Mastercard, Amex, or Discover transactions.
- Issuer participation: 97% of US Visa issuers and 83% of global Visa issuers participate in RDR.
- Transaction coverage: approximately 97% of Visa card transactions are eligible, across both fraud and non-fraud dispute reason codes.
- Geography: global — covers North America, Europe, MENA, APAC; integrated into Visa's standard dispute framework worldwide since 2021.
(ChargebackStop, June 2026, citing Kount)
Pricing (as-of January 2025)
From 1 January 2025, Verifi standardised RDR to a flat $19 per resolved dispute across all merchant category codes, removing the previous MCC-tiered structure ($9 low-risk / $19 medium-risk / $29 high-risk). (ChargebackStop, June 2026; corroborated by multiple vendor sources)
Verifi confirmed that pricing does not vary by Decision Source: rules-based and Decision API cases are billed at the same rate. (Verifi Decision API FAQ, primary source, March 2025)
Decision mechanisms
Merchants configure RDR outcomes via one of three mechanisms:
1. Verifi-hosted Decision Engine (rules)
Standard integration. Merchants configure up to 10 rules in the Verifi portal, using up to 8 attributes per rule:
| Attribute | Description |
|---|---|
| PAN First 6 | First 6 digits of the card number (BIN) |
| Transaction date | Date of the original transaction |
| Authorization datetime | Date/time of authorisation |
| Transaction amount | Amount of the disputed transaction |
| Transaction currency | Currency of the transaction |
| Purchase identifier | Merchant's internal transaction ID |
| Dispute category | Fraud or non-fraud |
| Dispute condition code | Specific Visa dispute reason code |
(Verifi Decision API FAQ, primary source, March 2025)
Example rule patterns reported by practitioners: auto-refund disputes under $50; resolve disputes coded "duplicate charge"; exclude transactions above a threshold from automatic refunds. (ChargebackStop, June 2026)
2. Decision API (merchant-hosted, beta from ~2025)
Allows merchants to build their own decision engine rather than using Verifi's portal rules. The API sends 29 attributes per dispute case (vs. 8 in the rules engine), and merchants can incorporate data from their own systems — shipping status, refund status, cardholder history, fraud signals — enabling more sophisticated decisioning. (Verifi Decision API FAQ, primary source, March 2025)
Key design details (all from Verifi primary source):
- SLA: merchant must respond within 3 seconds (increased from 2 seconds, effective March 2025)
- Timeout handling: no response within SLA → Outcome: Declined, Status: Closed, Status Code 910; no backup rule possible
- Decision logic is a black box to Verifi; Verifi cannot audit or validate the merchant's rules
- Configuration level: per-Client (not per-Partner) — two Clients under one Partner can differ (rules vs. API)
Use case signals (from Verifi): declines where the disputed transaction was already refunded; goods/services already delivered; dispute shows signals of Friendly Fraud that could be won via Representment; cardholder history suggests abuse.
3. Notifications API
A lighter integration where merchants receive real-time notification of each RDR case outcome without controlling the decision. Useful for pausing subscription access when a dispute is received. Delivers data faster than the SFTP Daily Extract (which lags one day). (Verifi Decision API FAQ, primary source)
RDR vs. CDRN vs. Ethoca
| Dimension | RDR | CDRN (Cardholder Dispute Resolution Network)|CDRN | Ethoca |
|---|---|---|---|
| Network owner | Visa (via Verifi) | Visa (via Verifi) | Mastercard |
| Card coverage | Visa only | Visa only | Mastercard primary (some Visa/Amex/Discover) |
| Geography | Global | US-only | Global |
| Dispute coverage | ~97% of Visa disputes | ~50% of Visa disputes | ~60% Mastercard disputes |
| Automation | Fully automated | 72-hour manual window | Manual per-alert |
| Cost (2025+) | $19/resolved dispute (flat) | ~$35/alert | ~$35–$40 direct; bundled via aggregators |
| Ongoing management | Set rules once | Action every alert | Action every alert |
Sources: (ChargebackStop, June 2026; Ethoca concept page; Chargeback.io)
Practitioner layering strategy reported by multiple sources:
- All merchants: RDR + Ethoca (covers Visa and Mastercard globally)
- High-risk merchants (chargeback rate >1%): add CDRN for additional US Visa coverage
- Many merchants layer RDR and CDRN: RDR auto-resolves cases within configured rules; CDRN alerts cover edge cases requiring human review
(Chargeback.io; ChargebackStop, June 2026)
RDR and VAMP
Does TC40 RDR exclusion apply under VAMP?
Checkout.com (official PSP documentation, VAMP support page): "All disputes (fraud and non-fraud disputes) resolved through Rapid Dispute Resolution will continue to be excluded from the VAMP ratio."
Multiple vendor sources (covering the April 2025 VAMP rule update): Starting April 1, 2025, TC40 fraud alerts resolved through RDR now count toward the VAMP ratio; only TC15 non-fraud disputes remain excluded.
The VAMP ratio formula is (TC40 + TC15) ÷ settled CNP. If TC40-flagged RDR resolutions remain in the VAMP numerator, RDR provides less VAMP protection for fraud-driven disputes than previously understood. No Visa primary source URL has been confirmed that resolves this contradiction (as-of 2026-08-25). See also Visa Acquirer Monitoring Program (VAMP).
Effectiveness benchmarks (as-of 2025)
- Visa reports a 34% average reduction in chargebacks for merchants using RDR. (ChargebackStop, June 2026, citing Visa)
- JustAnswer (online expert Q&A): >50% decrease in disputes after implementing Verifi tools including RDR; maintained chargeback-to-sales ratio below 0.9%. (ChargebackStop citing Verifi case study, 2022)
- 50–70% resolution rate on eligible disputes cited as a common outcome. (ChargebackStop, June 2026)
Counter-narrative: does RDR "save the sale"?
"RDR prevents revenue loss" vs. "RDR reroutes revenue loss"
Verifi's positioning (Verifi Explainer Series): RDR "lowers operational costs" and "resolves chargebacks before they post," framing automatic resolution as a win.
Counter-position (YouTube, Dec 2025): Alert programmes including RDR, CDRN, and Ethoca do not save the sale — they convert a chargeback loss into a refund loss. The underlying revenue loss is similar; the benefit is avoiding chargeback fees and protecting the dispute ratio, not recovering the transaction value.
Whether RDR is commercially worth $19/alert depends on the counterfactual: if the merchant would have lost the chargeback via representment, RDR saves ~$20–$100 in chargeback fees per case. If the merchant would have won via Representment, RDR is a net loss of the full sale value plus the $19 fee.
Setup and onboarding (as-of 2025)
- RDR requires acquirer enrolment in the Verifi network; merchants typically access RDR through their acquirer or a Verifi-authorised reseller, not directly with Verifi.
- Setup time cited as 1+ week for RDR vs ~48 hours for Ethoca and CDRN (YouTube source, date unknown, youtube.com).
- Resellers can configure rules on behalf of merchants or enable Decision API integration; Verifi client support handles BIN/CAID enrolment even for Decision API clients.
Key terms
| Term | Meaning |
|---|---|
| VROL | Visa Resolve Online — Visa's dispute processing platform; RDR operates within VROL |
| Decision Engine | Verifi's portal-based rules for configuring RDR outcomes (up to 10 rules, 8 attributes) |
| Decision API | Merchant-hosted API for custom decision logic; 29 attributes; 3-second SLA |
| Notifications API | Real-time RDR case outcome notifications without merchant decision control |
| CDRN | CDRN (Cardholder Dispute Resolution Network) — Verifi's manual, US-only alert product |
| TC40 | Visa fraud transaction code; included in VAMP ratio numerator |
| TC15 | Visa non-fraud dispute code; VAMP exclusion applies to TC15 RDR resolutions (uncontested) |
| Status Code 910 | Assigned to timed-out Decision API cases (outcome: Declined) |
| Pre-dispute | Dispute signal lodged with VROL before a formal chargeback is filed |
| BIN/CAID | Bank Identification Number / Card Acceptor ID — enrolment identifiers for RDR setup |
Frontier links
CDRN (Cardholder Dispute Resolution Network) · Verifi · Order Insight · Visa Resolve Online (VROL) · Friendly Fraud · Notifications API (Verifi) · Kount · Chargebacks911 · Chargeback Ratio