ZocumentsOn this page
- Read the noticeCapture the network, code, condition, claim, transaction date, and deadline.
- Translate cautiouslyUse the table below as orientation, not as a substitute for the live case.
- Answer the claimSelect records that address what the issuer says happened.
- Submit through the acquirerThe processor or acquirer determines the fields and evidence path available to you.
Current Visa dispute conditions
| Condition family | What it covers | Start with |
|---|---|---|
| 10 — Fraud | 10.1 EMV Liability Shift Counterfeit Fraud; 10.3 Other Fraud — Card-Present; 10.4 Other Fraud — Card-Absent; and 10.5 Visa Fraud Monitoring Program. | Match the environment and condition to chip, terminal, authentication, account, device, IP, and fulfillment records. |
| 11 — Authorization | 11.1 Card Recovery Bulletin, 11.2 Declined Authorization, and 11.3 No Authorization/Late Presentment for transactions completed on or after 13 April 2024. | Check the authorization response, transaction date, terminal or receipt, and when the transaction was processed. |
| 12 — Processing errors | 12.3 Incorrect Currency; 12.6.1 Duplicate Processing; 12.6.2 Paid by Other Means; and related transaction-data, amount, and account conditions. | Reconcile the receipt, capture, amount, currency, dates, and any cash, check, or other-card tender. |
| 13 — Consumer disputes | 13.1 not received, 13.2 cancelled recurring, 13.3 not as described or defective, 13.4 counterfeit, 13.5 misrepresentation, 13.6 credit not processed, and 13.7 cancelled merchandise/services. | Match the claim to delivery, product, cancellation, refund, authenticity, or service records. |
Common legacy numbers and their modern context
| Number seen | Historical label or common context | Do not assume |
|---|---|---|
| 30 | Services not provided or merchandise not received. | That the current notice will use the same number; read the claim and look for condition 13.1. |
| 53 | Not as described or defective merchandise. | That every quality complaint belongs to one universal Visa code; the product claim and condition 13.3 matter. |
| 70 | Card Recovery Bulletin or Exception File in older Visa terminology. | That it is the same as a modern fraud condition or a generic decline response. |
| 72 | No authorization in older Visa terminology. | That an authorization decline or missing authorization proves the transaction was fraudulent. |
| 75 | Cardholder does not recognize transaction in older Visa materials. | That it is the current name for every unrecognized-transaction claim or that it is still used unchanged. |
| 78 | Service code violation in older Visa references. | That it is a generic product or service complaint. |
| 80 | Incorrect transaction amount or account number in older Visa references. | That the amount is wrong without reconciling the receipt, capture, and account data. |
| 83 | Fraudulent transaction in a card-absent environment in older Visa materials; modern references use condition 10.4 for other card-absent fraud. | That a bare 83 identifies the network, date, or current evidence fields without the rest of the notice. |
What to save before you look up a code
Case identifiers
- Network and payment method
- Exact code, condition, and processor category
- Transaction date, settlement date, and reason text
- The customer or issuer claim document
- Response deadline and evidence fields
- The processor or acquirer that owns submission
For the merchant-facing next step, use the broad reason-code directory and then open the reason-specific evidence guides. When the claim is clear, use the chargeback response and rebuttal template and response packet guide to organize the records. Visa's merchant resource library and current Dispute Management Guidelines are the appropriate references when the live case conflicts with a summary page.
