Redencodes voor terugboekingen bij Visa (Gids voor handelaren 2026)

A Visa chargeback reason code identifies why the issuing bank disputed a payment. Start with the exact code and allegation on your processor’s notice, then check the permitted evidence and response deadline.

If what a chargeback is is still new to you, start there for the underlying mechanics, then come back here for Visa's specific codes. Visa restructured its taxonomy in April 2018 under Visa Claims Resolution, consolidating a longer legacy list into four categories, and it made a further change in April 2024 by retiring reason code 12.1 and folding late presentment into 11.3. Both updates are reflected in the tables below.

Reason codes were built to track payment issues, not to reveal intent. A code like 10.4 (Other Fraud, Card-Absent Environment) reads the same whether a card was genuinely stolen or a cardholder is disputing a purchase they made and simply regret, a pattern known as friendly fraud. That is why the evidence a merchant needs to win depends far more on the underlying story than on the code number itself. For the codes merchants see most often, start with the most common chargeback reason codes.

{{cta}}

Visa Chargeback Reason Codes: Current and Historical Reference

Use this table to identify the dispute condition and records to review. Evidence examples are starting points, not a complete response checklist or a guarantee of winning. For examples across other networks, see our overview of chargeback reason codes.

October 2026 status: Visa’s published rules limit condition 11.1 to disputes processed through October 23, 2026. It remains below for historical cases. Condition 12.1 is also historical; late presentment moved to 11.3 for transactions completed on or after April 13, 2024. Source: Visa Core Rules, sections 11.8.1 and 11.8.3.

Cardholders generally have up to 120 days from the transaction or expected delivery date to file a dispute, with a maximum of 540 days for select codes. Merchants get a uniform 30-day window to respond at each phase, and you can track every network's deadlines in one place with our chargeback calendar. For the full breakdown of fees and time limits by phase, see our guide to Visa chargeback dispute rules, fees, and time limits.

What Changed in 2024: Reason Code 12.1 Was Retired

Visa retired reason code 12.1 (Late Presentment) effective April 13, 2024, and folded every late-presentment case into reason code 11.3, which Visa now labels "No Authorization / Late Presentment." If your chargeback reports still reference 12.1, or an older guide you have on hand lists it as a standalone code, that information is out of date. The evidence requirement did not change, a valid authorization and timely settlement still defeats the claim, only the code number and category did.

Reason Codes 10.1-10.5: Fraud

10.1: EMV Liability Shift, Counterfeit Fraud

Reason code 10.1 applies when a cardholder claims a counterfeit chip card was used at a terminal that was not EMV-compliant. The surest way to avoid it is to keep terminals EMV certified, obtain cardholder verification, and follow best practices on terminal handling.

10.2: EMV Liability Shift, Non-Counterfeit Fraud

Reason code 10.2 covers disputes where a cardholder claims someone used their lost or stolen card for an unauthorized transaction. Prevent it by processing PIN-preferring cards on EMV terminals, obtaining an imprint for every card-present sale, and requiring signature or PIN verification.

10.3: Other Fraud, Card-Present Environment

Reason code 10.3 applies to fraud-related chargebacks on card-present transactions where a merchant failed to read the chip, skipped a manual imprint on a key-entered sale, or did not properly mark a transaction as card-present. Upgrading terminals and avoiding manual key-entry lets built-in chip protections do their job.

10.4: Other Fraud, Card-Absent Environment

Visa uses reason code 10.4 for transactions the cardholder claims were made without authorization in a card-not-present setting. It covers two very different scenarios: genuine fraud from a stolen card, and friendly fraud, where a buyer disputes a purchase they actually made. This is the single most common e-commerce fraud code, and the only one eligible for Compelling Evidence 3.0, which lets you submit two prior undisputed transactions, 120 to 365 days old, sharing at least two of four data points (user ID, IP address, shipping address, device fingerprint), with one of those two matches being IP address or device fingerprint, to shift liability back to the issuer. Limit exposure by requiring authorization on every card-absent and recurring order regardless of dollar value, and by capturing AVS, CVV2, and device data at checkout.

10.5: Visa Fraud Monitoring Program

Reason code 10.5 identifies chargebacks the card issuer initiates for merchants flagged under Visa's fraud-monitoring rules, historically branded the Visa Fraud Monitoring Program (VFMP) and folded since April 2025 into the Visa Acquirer Monitoring Program (VAMP). Cardholders rarely trigger this category directly, issuers act on directives from Visa. Limit exposure with authorization holds, a separate authorization for add-on charges, and close monitoring of your combined fraud-and-dispute ratio.

Evidence merchants need to win representment:

• AVS and CVV2 match confirmation from the original authorization
• EMV chip-read data and terminal certification records for card-present fraud (10.1-10.3)
• For 10.4, two prior undisputed transactions meeting the Compelling Evidence 3.0 matching criteria above
• IP address, device fingerprint, and delivery confirmation tying the cardholder to the order
• Documented fraud-prevention controls (3-D Secure, velocity limits) if flagged under reason code 10.5 (formerly VFMP, now part of VAMP)

Common merchant mistakes that lose this dispute:

• Skipping AVS and CVV2 checks on card-not-present orders to reduce checkout friction
• Manually keying a card-present sale instead of reading the chip, forfeiting EMV liability protection
• Not retaining IP, device, and order-history data long enough to build a Compelling Evidence 3.0 case
• Treating every 10.4 dispute as criminal fraud when a large share are friendly fraud disputes that need a different evidence strategy

Reason Codes 11.1-11.3: Authorization

11.1: Card Recovery Bulletin (Historical)

Visa limited this condition to disputes processed through October 23, 2026. It concerned specified transactions completed without authorization when the account appeared in the applicable Card Recovery Bulletin. Retain it for older case records; do not describe it as a current condition for newly processed disputes.

11.2: Declined Authorization

Reason code 11.2 means the merchant received a decline or pickup response but processed the sale anyway. On a decline, end the transaction or request a different payment method, never force a declined card through.

11.3: No Authorization / Late Presentment

Reason code 11.3 now covers two scenarios: transactions completed with insufficient or no authorization, and, since April 2024, transactions not submitted for settlement within the required processing window (the case formerly handled by reason code 12.1). Ensure every transaction receives timely approval, request an alternate payment method on failed approvals, and forward completed sales to your processor the same day when possible.

Evidence merchants need to win representment:

• The valid authorization approval code, amount, and timestamp
• Proof the transaction settled within the required processing window
• Confirmation the settled amount did not exceed what was authorized, or that a follow-up authorization was obtained
• Records showing the card was not listed on the Card Recovery Bulletin at time of sale

Common merchant mistakes that lose this dispute:

• Forcing a sale through after a decline or pickup response
• Settling for a higher amount than the original hold without a follow-up authorization
• Letting too much time pass between authorization and batch settlement
• Assuming 12.1 still applies, and pulling the wrong evidence for what is now an 11.3 case

Reason Codes 12.2-12.7: Processing Errors

12.2: Incorrect Transaction Code

Reason code 12.2 applies when a transaction was processed with the wrong transaction code, a sale instead of a credit, for example. Train staff on the difference between sale, credit, and reversal codes, and double-check entries before processing.

12.3: Incorrect Currency

Reason code 12.3 covers currency conversion errors or Dynamic Currency Conversion (DCC) disputes. Disclose when the local currency differs from the payment currency, show any added fees, and allow payment in local currency where possible.

12.4: Incorrect Account Number

Reason code 12.4 covers transactions posted to the wrong account number. Keep terminals current and double-check entries before processing to limit human error.

12.5: Incorrect Amount

Reason code 12.5 identifies disputes where the settled amount differs from the authorized amount. Review totals before authorization and never alter a completed transaction amount without new consent.

12.6: Duplicate Processing and Paid by Other Means

Reason code 12.6 splits into two sub-conditions: 12.6.1 for a transaction processed two or more times, and 12.6.2 for a purchase the cardholder settled through another payment method entirely. Examine receipts before depositing, present batches one at a time, and refund duplicate charges promptly.

12.7: Invalid Data

Reason code 12.7 applies to chargebacks caused by incorrect transaction data, the wrong date, Merchant Category Code, or country or state code. Review transaction data before clearing and address faulty hardware or network issues that can corrupt what gets transmitted.

Evidence merchants need to win representment:

• The original receipt and settlement batch record showing the correct code, currency, account number, and amount
• Settlement logs proving a transaction was not submitted twice (12.6.1)
• Proof the cardholder did not already pay through another channel (12.6.2)
• A currency disclosure or DCC consent screen shown before the transaction completed (12.3)
• Records confirming the correct MCC, transaction date, and country or state code (12.7)

Common merchant mistakes that lose this dispute:

• Keying the wrong transaction code (sale instead of credit or reversal)
• Re-running a transaction "just in case" the first attempt failed
• Applying DCC without a documented cardholder opt-in
• Batching and settling late, especially around holidays or system outages

Reason Codes 13.1-13.9: Consumer Disputes

13.1: Merchandise/Services Not Received

Reason code 13.1 covers chargebacks where the customer says merchandise or a service was not delivered by the promised date. Reduce risk by notifying cardholders of delays, shipping with insurance and tracking, keeping a clear refund policy, and requesting proof of delivery.

13.2: Cancelled Recurring Transaction

Reason code 13.2 applies when the cardholder says they were charged for a recurring payment after cancelling. Prevent it with transparent billing, clear subscription terms, easy cancellation, and fraud detection on renewal charges. See our full breakdown of Visa reason code 13.2 for the complete evidence checklist.

13.3: Not as Described or Defective Merchandise/Services

Reason code 13.3 covers disputes where the customer says the merchandise has an undisclosed defect or differs from your description. Review orders before shipping, package fragile goods carefully, and keep product descriptions accurate.

13.4: Counterfeit Merchandise

Reason code 13.4 applies when merchandise is identified as counterfeit. Source from reputable manufacturers, avoid misleading images, and disclose non-affiliation with brands when relevant.

13.5: Misrepresentation

Reason code 13.5 applies when the customer claims you misrepresented a transaction or used false advertising, covered in full in our guide to fighting reason code 13.5. Keep product and service descriptions accurate and include photos or video where it helps.

13.6: Credit Not Processed

Reason code 13.6 applies when a customer says you issued a receipt for a void or credit, yet the transaction was never reversed. Make sure the cardholder understands your return policy, process refunds promptly, and confirm issued credits with a reference number.

13.7: Cancelled Merchandise/Services

Reason code 13.7 covers disputes where a cardholder returned merchandise or cancelled a subscription but has not received the matching credit. Outline your return and cancellation policy before checkout, process credits quickly, and communicate delays.

13.8: Original Credit Transaction Not Accepted

Reason code 13.8 covers disputes where the cardholder claims a voided transaction was never processed; it applies to merchants in Europe and inter-regional territories. Know the rules governing original credit transactions in your region and keep accurate records.

13.9: Non-Receipt of Cash or Load Transaction Value

Reason code 13.9 applies when a cardholder says they did not receive the cash from an ATM withdrawal, or that a load transaction, funds added to a prepaid or gift card, never posted the expected value. Keep ATM dispense logs and load-transaction confirmations on hand, and reconcile terminal cash counts promptly after any reported shortfall.

Evidence merchants need to win representment:

• Tracking and signature-confirmed proof of delivery matching the billing or shipping address (13.1)
• Subscription terms, renewal notice, and cancellation timeline (13.2, 13.7)
• The product description shown at checkout, matched against what was delivered, plus photos (13.3, 13.5)
• Sourcing and authenticity documentation from the manufacturer or authorized distributor (13.4)
• Refund or credit confirmation with date, amount, and reference number (13.6, 13.8)
• ATM dispense logs or load-transaction confirmation showing the value was delivered (13.9)

Common merchant mistakes that lose this dispute:

• Not archiving checkout-page copy, leaving no record of what the cardholder actually agreed to buy
• Making cancellation difficult enough that customers dispute instead of cancelling directly
• Issuing a refund without a reference number the issuer can match to the original transaction
• Ignoring an early dispute alert that could have resolved the issue before it became a formal chargeback

Oude Visa-redencodes en hun huidige equivalenten

Older acquirer reports, processor exports, and training material still refer to the two-digit Visa reason codes that existed before Visa Claims Resolution took effect in April 2018. If a notice or a reconciliation file shows reason code 30, 53, 83, or 85, this table translates it to the dispute condition Visa uses today.

Source: Visa's dispute conditions quick reference as republished in acquirer VCR guides, including TD Merchant Solutions' Visa Claims Resolution FAQ. Legacy codes not listed here were retired without a direct successor. For the current cardholder and merchant time limits attached to each condition, see the Visa chargeback rules, fees and time limits guide.

Visa vs. Mastercard Reason Codes: What Changes for Dual-Network Merchants

Merchants who process both networks quickly notice that the same customer complaint gets a different code depending on which network the card runs on. The categories map closely, but the numbering schemes do not, so a rule built around a Visa code will not automatically catch the Mastercard equivalent.

For the full breakdown of every individual Mastercard code and the evidence each one needs, see our companion guide to Mastercard chargeback reason codes. American Express uses letter codes such as F29 and C08 instead; see the Amex chargeback reason codes guide.

Why Reason Code Accuracy Matters More in 2026

A Mastercard-sponsored Datos Insights study estimates that sellers will lose $15 billion to fraudulent chargebacks in 2025 alone, and getting the reason code wrong at intake, and therefore pulling the wrong evidence, is one of the most common reasons a winnable dispute gets lost anyway.

Network monitoring adds a separate pressure point. Under the Visa Acquirer Monitoring Program (VAMP), standard Excessive Merchant criteria in Asia Pacific, Canada, EU and US (effective April 1, 2026) apply when the acquirer is not Above Standard or Excessive: at least a 1.5% ratio using the sum of the TC40 fraud count and TC15 dispute count, divided by the count of settled TC05 card-not-present VisaNet payments in the same month, AND at least 1,500 monthly fraud-and-dispute reports. Do not treat a ratio alone or a universal per-case fee as the enrollment rule; confirm assessments with your acquirer's applicable notice. TC40 fraud and TC15 dispute report counts, not reason-code labels alone, determine the numerator, subject to the applicable exclusions and reporting period.

Check the Visa fact sheet and your acquirer's applicable notice. The standard merchant criteria above apply when the acquirer is not Above Standard or Excessive; other regional, local and acquirer criteria differ. The VAMP ratio is the sum of the TC40 fraud count and TC15 dispute count, divided by the count of settled TC05 card-not-present VisaNet payments in the same month. Certain pre-dispute resolutions and qualifying CE3.0 TC40 records are excluded, depending on extract timing; one payment can appear in both reports. A ratio alone does not establish enrollment, fines or closure, and being below these standard merchant thresholds does not guarantee freedom from acquirer or processor review.

Compelling Evidence 3.0 has specific eligibility rules for condition 10.4. Matching an IP address or a successful CVV check alone is not enough. See Visa’s CE3.0 merchant guidance and confirm the current permitted submission with your acquirer.

How to Respond to a Visa Chargeback Reason Code

Respond to a Visa reason code in four steps.

Some disputes never need representment at all. Enrolling in Visa Rapid Dispute Resolution lets pre-approved refund rules resolve eligible cases, mostly 13.x consumer-dispute codes, before they escalate into a formal chargeback.

Because fraud-code evidence bars are stricter than consumer-dispute evidence bars, the fastest win is often prevention. Stronger checkout-level defenses, the kind covered in our ecommerce fraud prevention guide, keep fewer 10.x disputes from reaching representment in the first place, and a chargeback alert service can flag a dispute while it is still a bank inquiry, giving you a window to refund or intervene before Visa's formal chargeback clock starts.

One emerging complication for 2026 is transactions initiated by an AI shopping agent rather than the cardholder directly. Visa's current reason codes were not written with that scenario in mind, and merchants are already asking how AI agent chargeback liability will be assigned when a card-on-file agent completes a purchase the cardholder never personally clicked "buy" on.

{{cta}}

Veelgestelde vragen

Hoeveel redencodes voor Visa-terugboekingen zijn er?

Visa groups dispute conditions into fraud, authorization, processing errors and consumer disputes. Counts depend on the effective date and whether 12.6 subconditions are counted separately. This reference marks historical conditions explicitly: 12.1 is retired, and Visa limited 11.1 to disputes processed through October 23, 2026.

What happened to Visa reason code 12.1?

Visa retired reason code 12.1 (Late Presentment) effective April 13, 2024. Every case that would have been coded 12.1 now falls under reason code 11.3, which Visa relabeled "No Authorization / Late Presentment." The evidence needed to win did not change, only the code number did.

Hoe lang hebben handelaren de tijd om te reageren op een Visa-geschil?

Use the due date on your processor’s case notice. Deadlines vary by stage, network rule and processor workflow; the cardholder’s filing window is a different clock. For example, Stripe’s response guidance describes a usual merchant window of 7 to 21 days, depending on the card network.

Welke Visa-redencode heeft betrekking op ‘friendly fraud’?

Most friendly fraud surfaces under reason code 10.4 (Other Fraud, Card-Absent Environment), which is the only Visa code eligible for Compelling Evidence 3.0.

What is Visa Compelling Evidence 3.0?

Compelling Evidence 3.0 lets a merchant defend a 10.4 dispute by submitting two prior undisputed transactions from the same cardholder, 120 to 365 days old, that share at least two of four data points (user ID, IP address, shipping address, device fingerprint) with the disputed order, with at least one of those matches being IP address or device fingerprint.

What is Visa reason code 13.9?

Reason code 13.9 covers disputes where a cardholder says they did not receive cash from an ATM withdrawal, or that a load transaction, money added to a prepaid or gift card, never posted the expected value.

Match the Code, Pull the Evidence, Win the Dispute

Chargeback resolution comes down to identifying the right code, pulling the evidence it specifically demands, and submitting before the deadline. Use this guide as your quick reference, and pair it with our companion list of Mastercard chargeback reason codes if you process both networks.

Chargeflow automates evidence gathering and submission across every reason code, with a 100% submission rate and pay-only-if-we-win pricing. Contact our team to recover Visa chargebacks on autopilot.