Stop BFCM chargebacks before they ship
Learn how - Webinar Nov 17!
Stop BFCM chargebacks before they ship
Learn how - Webinar Nov 17!
/
Disputes & Chargebacks
September 22, 2024
Jun 5, 2026

Evolving Chargeback Reason Codes: What the Changes Mean for Merchants (2026)

White circular logo with interlocking shapes at the center surrounded by overlapping orbit-like elliptical lines and scattered blue diamond shapes.

Chargebacks?
No longer your problem.

Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000+ merchants.

600+ reviews
No credit card needed.

TL;DR:

Visa's current condition 11.3 covers No Authorization/Late Presentment. Visa CE3.0 applies to eligible condition 10.4 card-absent fraud claims. Use two qualifying prior transactions from the same merchant and payment credential, 120–365 days before the dispute date, with no active fraud report or fraud dispute. Match at least two core elements across both prior transactions and the disputed transaction; one must be IP address or device ID/fingerprint. Processing validity depends on transaction type, indicators and local rules; obtain the capture/clearing deadline from your processor. Confirm partial-authorization requirements for your region, MCC and card product, and submit dispute evidence by the deadline in your case notice. Automation can assist recordkeeping and submissions; it does not establish compliance or guarantee a decision.
Loading the Elevenlabs Text to Speech AudioNative Player...

Key Takeaways

  • Visa retired reason code 12.1 (late presentment) and now reports those cases under 11.3 (No Authorization/Late Presentment).
  • Compelling Evidence 3.0: Visa CE3.0 applies to eligible condition 10.4 card-absent fraud claims. Use two qualifying prior transactions from the same merchant and payment credential, 120–365 days before the dispute date, with no active fraud report or fraud dispute. Match at least two core elements across both prior transactions and the disputed transaction; one must be IP address or device ID/fingerprint.
  • Visa processing-validity windows depend on transaction type and indicators: generally 5 calendar days for other card-present transactions and merchant-initiated transactions, 10 for cardholder-initiated card-absent transactions, or 30 with eligible extended/estimated authorization. Local exceptions and your processor's capture window still apply.
  • Partial-authorization support depends on region, MCC and card product. Visa's April 2026 table includes automated fuel dispensers in Europe and the U.S., plus specified LAC debit/prepaid categories; ask your acquirer which requirements apply.
  • Automated evidence collection can support timely responses, but merchants and processors still need to validate payment processing, eligibility and compliance requirements.

Visa's April 18, 2026 public rules identify condition 11.3 as No Authorization/Late Presentment. Alongside reason-specific dispute responses, merchants need to distinguish CE3.0 qualifying evidence from payment authorization and processing requirements. This guide explains the checks to make with your acquirer and processor.

Visa ChangeWhat It Means for MerchantsRec­om­mended Action
Reason code 12.1 retired, merged into 11.3Late presentment is now handled under the authorization categoryAuthorize and clear transactions within network windows
Compelling Evidence 3.0Applies to qualifying Visa 10.4 card-absent fraud claims; eligibility must be validatedCapture two qualifying prior transactions, aged 120–365 days from the dispute date, with required matching core data
Standardized auth-to-clearing timeframesValidity depends on transaction type, authorization indicators and local exceptionsAutomate clearing; use Extended Authorization where needed
Partial authorization mandate (select MCCs)Check the region, MCC and card product in Visa's current participation tableEnable the partial-auth indicator with your processor

Chargeback reason codes point you in the right direction by showing the likely causes of chargebacks and how you can dispute them. Recurring chargebacks in the fraud category can place your business on fraud-related monitoring programs, hurting your reputation and your revenue.

Visa has made major changes to the 12.1 and 11.3 chargeback codes. The network also updated its compelling evidence rules and the authorization-to-clearing timeframes. These changes require an upgrade in how you respond to chargebacks and how quickly you act.

What does Visa's shift from reason code 12.1 to 11.3 mean for merchants?

Visa retired reason code 12.1 and now reports those cases under reason code 11.3. The now-defunct 12.1 dealt with transactions merchants did not present on time.

Moving from 12.1 to 11.3 streamlines the chargeback process, giving merchants:

  • A less complex chargeback process: late presentment shows that the authorization expired, so the current 11.3 condition groups no-authorization and late-presentment cases under its specific dispute rules.
  • Quicker resolutions: it is now easier to handle chargebacks that fall into that category.

Reason code 11.3 now covers the following scenarios:

  • A valid issuer authorization was required but was not obtained.
  • A valid authorization was obtained, but the transaction was not processed within the applicable timeframe.
  • If the processed amount exceeded the authorized amount, check the amount-specific dispute right and any valid incremental authorizations with your acquirer.

Implications for Merchants

By merging late presentment under 11.3, Visa reiterates the importance of proper authorization. Merchants must ensure timely authorization and submit transactions within the required timeframe to reduce the risk of chargebacks.

Automated record collection can help prepare a response, but your processor controls authorization, capture and clearing. Verify the actual records, case eligibility and submission deadline before relying on automation.

What is Visa's Compelling Evidence 3.0 rule?

Introduction to Compelling Evidence 3.0

CE3.0 is a specific Visa framework for eligible condition 10.4 card-absent fraud claims, effective from April 15, 2023. It is not a universal evidence standard for every dispute reason, refund claim or card network.

This is not about overruling cardholders who rightly contest a charge. But some chargeback claims are filed in error or as a deliberate move to defraud your business. With the right documents under Compelling Evidence 3.0, you have the upper hand in those disputes.

Here is the evidence needed:

  • Two qualifying prior transactions using the same merchant and payment credential, at least 120 and no more than 365 days before the dispute date, with no active fraud report or fraud dispute under Visa's criteria.
  • At least two core elements must match across both prior transactions and the disputed one: user ID, IP address, shipping address, or device ID/fingerprint. At least one matching element must be IP address or device ID/fingerprint. Telephone number is not one of these four core elements.

The required records can be delivered through the supported pre-dispute channel or the acquirer's post-dispute response process. Qualification and validation under Visa's rules determine the CE3.0 treatment; merely collecting two old orders does not guarantee a successful dispute response.

Practical Steps for Compliance

  • Confirm that your evidence collection workflow actually retains the required transaction, credential and matching data. Automation can gather available records, but it cannot create missing qualifying history or establish CE3.0 eligibility by itself.
  • Keep records of all deliveries and proof that cardholders received them without complaints.
  • Leverage modern technology for sharing evidence.

Submit through the permitted channel by the deadline in your actual processor or acquirer notice. A network stage deadline and a merchant submission deadline are different clocks; pre-dispute availability does not remove the need to validate qualifying records.

Impact on Merchant Operations

Chargeflow's prevention alerts let you stop disputes before they become costly chargebacks. Real-time alerts enable you to act immediately, protecting revenue and customer relationships.

This rule presents a few challenges, including data collection and management for submission when needed, and system integrations to capture the required data. You will need modern tools like Chargeflow to automate evidence collection and manage disputes without burdening your teams.

How do the authorization-to-clearing timeframes work?

Visa's general approval-response validity periods below start on the date of a valid authorization. They are processing rules, not a promise that every processor will keep a capture open for that long. Country-specific rules and additional clearing requirements can be shorter.

Trans­ac­tion typeGeneral maximumQual­i­fi­ca­tion
Other card-present transactions5 calendar daysGeneral table; country and specific use-case exceptions apply
Merchant-initiated transactions, including recurring5 calendar daysSeparate from cardholder-initiated e-commerce
Cardholder-initiated card-absent transactions10 calendar daysGeneral maximum from valid authorization; local exceptions apply
Eligible extended card-absent authorization, or estimated authorization for cruise, lodging or vehicle rental30 calendar daysRequires the appropriate indicator; not every rental qualifies

Implications for Different Merchant Categories

For an eligible cardholder-initiated card-absent transaction with the extended authorization indicator, Visa's general table allows 30 calendar days. Estimated authorizations for cruise lines, lodging and vehicle rental also have a 30-day general maximum; other rental categories can have shorter periods. Confirm eligibility and the actual capture deadline with your processor.

Recommended Actions for Compliance

  • Update your payment systems to submit transactions for clearing within the allocated timeframe.
  • Ask your payment processor how it monitors authorization validity, capture and clearing. Evidence-response automation is a separate workflow.
  • Monitor your transactions to ensure they are submitted on time.

What are the new requirements for partial authorizations?

Visa's April 2026 participation table varies by region, MCC and card product. It requires all-product support at automated fuel dispensers (MCC 5542) in Europe and the U.S., and debit/prepaid support for specified LAC merchant categories. This is not a blanket debit/prepaid mandate for every e-commerce store. Ask your acquirer to confirm participation, indicators and any commercial consequences for your specific setup.

When supported by the issuer and processor, a partial authorization can approve an amount available on the card instead of the entire purchase amount. It does not guarantee approval or remove the need to handle the unapproved balance.

Consequences of Non-Compliance

  • Increased transaction declines.
  • Any fee or contractual consequence depends on the applicable payment-brand and acquirer program; confirm it with your acquirer.

Audit the regions, MCCs and payment products you actually process. Enable partial-authorization indicators only through a supported processor flow and confirm how your checkout handles partial approval, the remaining balance and reversal.

Steps to Implement Partial Authorization

  • Communicate with your payment processors to add the necessary settings.
  • Update your payment processing systems and point-of-sale terminals to include partial authorizations.
  • Train your staff on how to handle partial authorizations.
  • Test the systems and monitor transactions using reporting tools.

How should you prepare for the new chargeback landscape?

Review all your chargeback management strategies, including the systems, hardware, and software you use. Update how you gather and report evidence. Review recent chargebacks, especially those in the late presentment category, and watch for vulnerabilities such as data security issues, incompatible system integrations, and human operational errors.

Leveraging Technology and Tools

The evolving landscape calls for efficient systems to handle transaction recording, monitoring, and evidence gathering. Chargeflow's AI Insights lets merchants analyze chargeback trends, detect fraud patterns, and proactively address potential disputes for better chargeback management and revenue protection.

Here is an example of how Chargeflow helps:

  • Scenario: a medium-sized retailer sees a rise in chargebacks under 11.3 ("No Authorization"). Managing these with manual processes is time-consuming and error-prone.
  • Solution: Chargeflow's automated system tracks authorization details, collects compelling evidence, and submits disputes well within deadlines.
  • Expected operational benefit: collecting records and tracking deadlines can reduce response mistakes. Review the case outcome and net recovery afterward; automation does not guarantee fewer chargebacks, compliance or pre-dispute resolution.

Strategic Next Steps with Chargeflow

Use the current condition 11.3 label and its reason-specific records for no-authorization or late-presentment cases. CE3.0 history belongs to qualifying condition 10.4 fraud claims. Keeping those workflows separate prevents a response from using the wrong evidence standard.

Staying updated on new regulations is crucial, and Chargeflow can help by keeping you informed. Trusted by 20,000+ merchants across 90+ countries, Chargeflow's suite of tools automates evidence collection and offers real-time monitoring on a success-based model, you only pay for disputes won, so you can focus on growing your business while it handles the complexities of chargebacks.

Frequently Asked Questions

What happened to Visa reason code 12.1?+

Visa retired reason code 12.1, which covered late presentment, and now reports those cases under reason code 11.3 (No Authorization/Late Presentment). Its specific evidence and processing rules determine the response.

What is Compelling Evidence 3.0?+

For eligible Visa condition 10.4 card-absent fraud claims, use two qualifying prior transactions from the same merchant and payment credential, aged 120–365 days from the dispute date, with no active fraud report or fraud dispute. At least two core elements must match across the prior and disputed transactions; one must be IP address or device ID/fingerprint. Eligibility and validation determine the outcome.

What are the authorization-to-clearing timeframes?+

Visa's general validity periods start at a valid authorization: 5 calendar days for other card-present and merchant-initiated transactions, 10 for cardholder-initiated card-absent transactions, and 30 for eligible extended/estimated authorizations. Indicators, country exceptions and processor capture deadlines matter; there is no universal 10-day window for all online renewals.

How can merchants stay compliant with Visa's chargeback changes?+

Validate authorization and processing windows with your processor, retain the evidence required for the actual dispute condition, support partial authorizations where your region/MCC/product requires them, and submit by the deadline in your case notice. Automation can assist these checks but does not establish compliance.

SHARE THIS ARTICLE
White circular logo with interlocking shapes at the center surrounded by overlapping orbit-like elliptical lines and scattered blue diamond shapes.

Chargebacks?
No longer your problem.

Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.

600+ reviews
No credit card needed.
subscribe

The latest chargebacks, fraud, and ecommerce content, in your inbox. Every week.

Sign up now and never miss out the latest trends!
By providing your email you're agreeing to our Terms of Service and Privacy Notice
Diagram with dashed and curved lines forming segmented arcs highlighted by three blue diamond markers on the left side.Abstract circular grid design with blue diamond markers on a half-black, half-white background.