Visa Reason Codes: The Complete VCR Map (2026)

A reference map of every active Visa Claims Resolution code as of mid-2026, with workflow assignment, filing deadlines, and operator-relevant defense notes per code. For the narrative explanation of how VCR works in production — why the two-workflow split matters, how CE 3.0 auto-qualification changed defense economics, and how VAMP enforcement affects code-level strategy — see Scheme Chargeback Rules in 2026.

Quick reference: all active codes

Code	Category	Name	Workflow
10.1	Fraud	EMV Liability Shift — Counterfeit	Allocation
10.2	Fraud	EMV Liability Shift — Non-Counterfeit	Allocation
10.3	Fraud	Other Fraud — Card-Present	Allocation
10.4	Fraud	Other Fraud — Card-Absent (CE 3.0 eligible)	Allocation
10.5	Fraud	VFMP (rolled into VAMP March 2025)	Allocation
11.1	Authorization	Card Recovery Bulletin	Allocation
11.2	Authorization	Declined Authorization	Allocation
11.3	Authorization	No Authorization (absorbed 71–74 + 12.1 in 2024)	Allocation
12.2	Processing Errors	Incorrect Transaction Code	Collaboration
12.3	Processing Errors	Incorrect Currency	Collaboration
13.1	Consumer Disputes	Item Not Received	Collaboration
13.2	Consumer Disputes	Cancelled Recurring	Collaboration
13.3	Consumer Disputes	Not as Described or Defective	Collaboration
13.4	Consumer Disputes	Counterfeit Merchandise	Collaboration
13.5	Consumer Disputes	Misrepresentation	Collaboration

Merchant initial response deadline: 30 days across all codes. Maximum dispute resolution timeline: 70 days (Allocation) or 100 days (Collaboration).

Fraud (10.x) — Allocation workflow

Fraud codes use Visa’s Allocation workflow: liability is auto-assigned based on network data without a full issuer-merchant evidence exchange. The defense surface is narrower than Collaboration disputes — but 10.4 has the CE 3.0 exception, where historical transaction evidence can reverse the auto-allocation.

Code	Trigger	Defense notes
10.1	Counterfeit card used at a non-EMV-capable terminal	Liability typically shifts to acquirer/merchant. Limited merchant defense surface.
10.2	Legitimate card used fraudulently at a non-EMV terminal	Same liability dynamics as 10.1.
10.3	Unauthorized in-person transaction (card-present fraud)	Cardholder claims fraud at point of sale.
10.4	Unauthorized card-not-present transaction	The highest-volume fraud code for e-commerce. Only code eligible for CE 3.0 defense (see below).
10.5	Disputes initiated via the former VFMP	Code retained for legacy disputes. New monitoring runs through VAMP.

CE 3.0 (10.4 only): Visa Compelling Evidence 3.0 lets merchants reverse a 10.4 chargeback by submitting two prior undisputed transactions from the same cardholder, dated 120–365 days before the disputed transaction. From October 17, 2025, merchants on Visa Secure or Visa Data Only receive automatic CE 3.0 qualification — no manual filing required. CE 3.0-resolved disputes are excluded from the VAMP ratio. For full mechanics see the source article.

Authorization (11.x) — Allocation workflow

Code	Trigger	Defense notes
11.1	Transaction flagged via Card Recovery Bulletin	Acquirer/processor handling — limited merchant action surface.
11.2	Transaction processed despite a declined authorization	Defense rare; processing-stage error.
11.3	No authorization requested, authorization expired, transaction amount exceeded authorization, or late presentment	Major April 2024 consolidation. Absorbed former codes 71, 72, 73, 74 (consolidated “no authorization” variants) and 12.1 (Late Presentment, previously in the Processing Errors category). Legacy documentation referencing those codes as active is out of date.

Processing Errors (12.x) — Collaboration workflow

After the April 2024 consolidation moved Late Presentment (12.1) into 11.3, this category is materially thinner than it used to be.

Code	Trigger	Defense notes
12.2	Incorrect transaction code submitted in authorization	Processing-stage error; acquirer typically resolves.
12.3	Incorrect currency submitted	Currency mismatch between authorization and clearing.

Consumer Disputes (13.x) — Collaboration workflow

These codes use the Collaboration workflow — back-and-forth evidence exchange between issuer, acquirer, and merchant, up to 100 days to resolve. Active engagement and documentation matter here in a way they don’t for Allocation disputes.

Code	Trigger	Defense notes
13.1	Cardholder claims goods or services were not delivered or arrived late	High volume for marketplaces, digital goods, and logistics-heavy merchants. Tracking and delivery confirmation are the primary defenses.
13.2	Transaction charged after the cardholder cancelled a recurring arrangement	High volume for SaaS and subscription operators. Cancellation timestamps, retention save attempts, and policy ToS are the defense surface.
13.3	Merchandise defective or materially different from representation	Photos, shipping condition records, return policy compliance.
13.4	Cardholder claims goods are counterfeit	Authentication documentation, sourcing records.
13.5	False advertising or misrepresented transaction terms	Marketing copy archive, ToS at point of purchase.

For SaaS and subscription operators, dispute mix tends to be dominated by 10.4 (fraud) and 13.2 (cancelled recurring). For physical e-commerce, the dominant pair is 10.4 and 13.1 (item not received). Defense strategy should be built around your actual code distribution, not the full code list.

Code-level changes that matter (2018–2026)

Date	Change	Operator impact
April 2018	VCR launched; 22 legacy codes replaced with 4-category structure	The original consolidation. Two-workflow split (Allocation vs Collaboration) introduced.
April 2024	11.3 absorbs former codes 71–74 and Late Presentment (12.1)	Legacy documentation referencing 12.1 or 71–74 is out of date. Auth-stage disputes now route through a single code.
March 31, 2025	VDMP and VFMP retired; rolled into VAMP	Single consolidated monitoring metric across fraud and non-fraud disputes.
October 17, 2025	CE 3.0 auto-qualification activates for merchants on Visa Secure / Visa Data Only	10.4 defense becomes automated for enrolled merchants. CE 3.0-resolved disputes excluded from VAMP.
April 1, 2026	VAMP merchant Excessive threshold drops from 2.2% to 1.5% (NA/EU/APAC)	High-dispute-rate merchants enter Excessive territory at a lower ratio.
April 17, 2026	CE 3.0 fee structure introduced for successful qualifications	Confirm fee schedule with your acquirer.

Related references

• Scheme Chargeback Rules in 2026 — narrative explanation of VCR workflows, CE 3.0 mechanics, VAMP enforcement, and Mastercard Mastercom comparison.
• VAMP Operator Guide — full VAMP mechanics, fee structure, and remediation playbook.
• Chargeback Representment Playbook — merchant-side defense strategy by code type.
• AI Chargeback Representment Automation — automating defense for 10.4 disputes.
• Pre-Dispute Tools: RDR, CDRN, Ethoca — section in the source article covering Visa RDR, Verifi CDRN, and Mastercard Ethoca Alerts.

For term definitions — chargeback, dispute, authorization, chargeback ratio — see the Payments Glossary.