Legacy Visa reason codes: 83, 76, 71 and 75
These four two-digit codes were retired when Visa launched the Visa Claims Resolution (VCR) framework in April 2018. They still turn up in historical chargeback files, old processor exports, archived acquirer documentation, dispute tickets, and legacy reporting — this page is an operator routing aid for identifying what they mean today, not a scheme determination.
Legacy Visa dispute codes are not authorization or network decline codes.
Dispute/chargeback reason codes and authorization/network decline codes are two separate numbering systems that both use small integers. The same number — 83, 76, or 75 — can mean a completely different thing depending on which system it comes from. Confirm which system a code came from before you act on it.
Quick mapping table
| Legacy code | Historical meaning | Current guidance | Mapping type |
|---|---|---|---|
| 83 | Fraudulent Transaction — Card-Not-Present Environment | Conditional — fraud branch may correspond to 10.4; processing-error branch may correspond to 12.4 | One-to-many / conditional |
| 76 | Incorrect Transaction Code / Incorrect Currency | Conditional — may correspond to 12.2 and/or 12.3 | One-to-many / conditional |
| 71 | Declined Authorization | Maps to 11.2 (Declined Authorization) | Direct (well-supported) |
| 75 | Cardholder Does Not Recognize Transaction | Retired — no direct current VCR equivalent | Obsolete |
Code 83
Historically, legacy code 83 meant "Fraudulent Transaction — Card-Not-Present Environment." It does not have a single current equivalent — it is a conditional mapping. The fraud branch may correspond to today's 10.4 (Other Fraud — Card-Absent Environment); the processing-error branch may correspond to 12.4 (Incorrect Account Number).
12.4 is not yet covered by this site's active reason-code lookup, so there is no internal page to link for that branch. If you're routing a record that looks like the processing-error branch of legacy 83, describe it in words internally and confirm the current definition against your acquirer or the Visa portal directly.
Separately, an authorization/network response code 83 (for example, an Elo network "Security decline") is a completely different code system, unrelated to dispute code 83. Do not assume a "code 83" in an authorization log is the same thing as a "code 83" in a dispute file.
Code 76
Historically, legacy code 76 meant "Incorrect Transaction Code / Incorrect Currency." Current guidance is a conditional, category-level mapping: legacy 76 may correspond to 12.2 (Incorrect Transaction Code) and/or 12.3 (Incorrect Currency).
The category-level split is well-supported. What's less certain is the sub-condition detail: acquirer crosswalks disagree on which sub-condition routes to 12.2 versus 12.3 — TD Merchant Solutions and Bank of America Merchant Services' 2018 VCR crosswalks do not fully agree at that level. If you need sub-condition precision for a specific historical record, verify it against the current acquirer or Visa portal rather than treating either crosswalk as final.
Separately, an unrelated authorization/decline code 76 (for example, an Elo network "Invalid account") is a separate code system from dispute code 76.
Code 71
Historically, legacy code 71 meant "Declined Authorization." This is the one well-supported direct relationship among the four codes on this page: legacy 71 maps to 11.2 (Declined Authorization), not 11.3. Three independent sources agree, including the current Visa Core Rules, which still lists 11.2 as a distinct, active dispute condition with the same definition it has carried since VCR's 2018 launch.
Keep two separate Visa events straight: the 2018 VCR restructuring that retired the two-digit legacy codes (including 71) is a different event from the April 2024 merger of Late Presentment (12.1) into 11.3. Legacy 71 belongs to the 2018 event and maps to 11.2 — it was never part of the 2024 change. No authorization-decline-code collision has been established for 71; unlike 83, 76, and 75, there's no evidence of an unrelated authorization/decline code sharing this number.
Code 75
Historically, legacy code 75 meant "Cardholder Does Not Recognize Transaction." It was retired with no direct current VCR equivalent — it was eliminated outright, not folded into another code. Do not translate an old record's code 75 into a current dispute condition; there isn't one.
If code 75 appears in an old record, work it the same way as any legacy code: (1) confirm whether it came from a dispute file or an authorization response; (2) identify the original acquirer/processor and the record date; (3) check the current dispute record in the acquirer or Visa portal; (4) do not translate by matching the number alone.
This is the code most likely to be confused with an unrelated live code: authorization decline code 75 means "Allowable PIN Tries Exceeded" — a current, active code already documented in this site's decline-codes glossary (see the warning above). That is a soft-decline authorization response, not a retired dispute reason code. The two are unrelated concepts that happen to share the number 75.
Why identical numbers can refer to different code systems
Visa dispute/chargeback reason codes and ISO-8583-style network authorization decline codes are two entirely separate numbering systems. Both happen to use small integers — often two digits — because that was a practical, compact convention decades ago. A number match between the two systems is a coincidence, not a meaning match. "Code 83" in a chargeback file and "code 83" in an authorization log are answering two different questions: one is about why a dispute was filed, the other is about why a transaction was declined at the point of authorization. Always check which system a code came from before mapping it to anything.
How to handle a legacy code in an operational queue
- Identify the source system — was this pulled from a dispute/chargeback file, or an authorization response log?
- Determine whether it is a dispute code or an authorization response — the same number means different things in each.
- Confirm the record date — legacy dispute codes predate April 2018; a record dated after that should not be using them.
- Check the current acquirer/Visa category for the equivalent — don't assume the mapping on this page is exhaustive for your specific sub-condition.
- Treat the legacy mapping as a routing aid, not a final scheme determination — verify before you act on it in a live dispute.
Current Visa reason-code lookup
For active, current Visa and Mastercard dispute codes, use the reason-code lookup tool — triggers, evidence checklists, and response deadlines for all codes in active use today. For the full narrative reference, see Visa Reason Codes: The Complete VCR Map and Scheme Chargeback Rules in 2026.