chargeback

reason codes.

Visa Chargeback Reason Code 11.3: No Authorization/Late Presentment

Black Visa credit card with chip on the left and the Visa logo in white and orange on the bottom right.Black Mastercard credit card with chip and overlapping red and orange Mastercard logo in upper right corner.Black American Express credit card with chip and blue American Express logo.Black Discover credit card with a chip on the left and the Discover logo on the right.
Futuristic digital interface with blue and white glowing hexagonal and circular elements connected by lines on a dark background.

Visa Chargeback Reason Code 11.3: No Authorization/Late Presentment

What is Visa Chargeback Reason Code 11.3?

Visa condition 11.3: No Authorization/Late Presentment addresses specified authorization and late-presentment conditions. It is not simply a finding that the cardholder did not consent to a purchase. Visa’s April 18, 2026 public rules, section 11.8.3, define its rights, limits and response requirements.

Effective-date context: the June 2024 merchant guide identifies the combined condition for transactions completed on or after April 13, 2024, while 12.1 Late Presentment is labeled effective through April 12, 2024. Read your provider’s case description and applicable rule edition before choosing a response.

Read the alleged authorization or timing failure in the case notice. A fraud complaint and a missing or expired authorization are different issues; an approval record alone does not establish cardholder consent or answer every late-presentment allegation.

Card authorization verifies the card’s ability to cover the transaction. The request goes out to the issuer before the payment is processed. This process should be automatic once the cardholder taps, swipes, or inserts the card for payment (depending on the payment terminal).

Authorization is also essential for internet, phone, or mail orders. Processing payments when the authorization request is not sent or without approval will most likely lead to chargebacks under this reason code.

Careful handling of transactions should prevent this chargeback from happening. Nevertheless, the causes of chargebacks under this reason code are not limited to merchant errors. Cardholders may also be responsible for the chargeback even when you’ve done everything correctly.

We recommend following all authorization procedures when processing payments. Bypassing them will undoubtedly result in this chargeback, causing discomfort and loss if you are in the wrong. We’ll show you how to fight it, but your efforts will only yield results if you follow the correct procedures.

Investigate the transaction records before assigning a cause. The code identifies a condition under the network rules, not a final finding of customer misuse or merchant fault.

Why Did It Happen?

Chargebacks with reason code 11.3 occur when authorization is not obtained before processing a transaction. Two things stand out, as shown below:

The correct processing procedure requires the following:

  • A proper authorization request
  • A valid authorization approval

The authorization must be correct and valid. Once the request is received, you should receive a message with an “Approved” response. Any other response not giving the issuer’s approval to continue the transaction will likely cause a chargeback.

In that case, the card may be stolen, lost, or compromised somehow. That is why authorization is needed to prevent this chargeback. With that in mind, the following are reasons this chargeback may occur:

  • No authorization request was sent for the transaction
  • The authorization request was sent after the transaction was completed

Faulty payment terminals may cause any of the above reasons, leading to chargebacks. Anything that prevents you from sending authorization requests and receiving approval will cause chargebacks under this reason code.

Cardholders may be persuasive in asking merchants to push a payment through even without sufficient authorization. That will require turning off the safety features that should detect this error. However, doing that can cause the issuer to file chargebacks that are impossible to fight.

Another likely cause of this chargeback is obtaining authorization for one amount and using it to process a different amount, usually higher. This error might fall under another reason code, but since authorization is taken from one and applied to another, you can get it here, too.

Regardless of how persuasive cardholders are, insist on getting authorization approval before processing payment. Also, avoid using terminals that can bypass authorization requests.

{{COMPONENT_IDENTIFIER}}

How to Fight Visa Chargeback Reason Code 11.3: No Authorization/Late Presentment

Issuer filing clock: Visa’s April 2026 rules specify 75 calendar days from the Transaction Processing Date for the general 11.3 filing limit, with adjustment-specific provisions. This is not your merchant response window. Use the deadline and time zone shown on the provider’s case.

Evidence limit: identify the permitted defense under the specific condition. Relevant records can include required authorization details, a transaction receipt and clearing dates, or a credit that was not addressed. An authorization approval alone does not answer a late-presentment objection. Confirm permitted material and submission stage with your acquirer.

Our approach to fighting this chargeback will come back to your end and what you did correctly or wrongly. With that in mind, here are the methods you can use:

  • If required authorization was obtained: provide the matching approval record, amount and dates through your provider. Explain how they answer the actual condition; approval does not guarantee reversal.
  • If you have contacted the cardholder and resolved the issue: Provide evidence that you have resolved the case with the cardholder. It should also include credit details like the amount and the transaction date. These prove that you already issued a refund before the chargeback.
  • If the cardholder says the complaint is withdrawn: retain the correspondence and ask the provider what must still be submitted. Do not assume a customer message closes the case automatically.
  • If the clearing records list has an incorrect transaction date: Show evidence that the transaction date is erroneous. Ensure you provide the correct transaction date.

Some payments require special authorization. These transactions require a unique approach to fighting chargebacks. You should provide all the response codes to your authorization requests, including the following:

  • The initial transaction date
  • The final transaction date
  • The amounts from the start to the finish

You’ll also have to proof the following:

  • The initial authorization request was for an estimated amount
  • You increased the transaction amounts subsequently
  • All the authorization requests have the same transaction identifier

One or more of the above may be required.

How to Prevent Visa Chargeback Reason Code 11.3: No Authorization/Late Presentment

Follow the authorization and processing timeframes that apply to the transaction. Keep approval records and clearing timestamps together so a processing or late-presentment issue can be identified and answered.

The following are ways to prevent chargebacks under reason code 11.3:

  • Ensure transactions receive an immediate and clear approval response before proceeding.
  • Flag transactions with failed authorization approval and request an alternative payment method.
  • Train your staff on following Visa rules and regulations for transactions requiring special authorizations. Each authorization level should be confirmed and recorded before proceeding to the next.
  • Upgrade your payment terminals to the latest version to avoid bypassing authorization requests.
  • Do not bypass authorization requests, no matter how persuasive the cardholder is.

Use the reason-code directory for lookup and the reason-code explainer to map the allegation to evidence. Keep the different filing and response clocks separate.

Chargeback reason codes getting you down?
Switch to automated chargeback management with Chargeflow today.