Visa Reason Code 11.3: No Authorization
Visa reason code 11.3 applies when a transaction was processed without a valid authorization. That includes no authorization at all, an approval that expired before capture, or a capture above the approved amount. For ecommerce, delayed and inflated captures are the usual culprits. Win with an approval that covers the amount and date.
What Visa reason code 11.3 means
Reason code 11.3 is the broadest Authorization code. The issuer says the transaction lacked a valid authorization. That covers several situations:
- No authorization was requested when one was required.
- The authorization had expired before the transaction was captured. Visa approvals are only valid for a limited period, which depends on the transaction type.
- The captured amount was higher than the approved amount, beyond any tolerance Visa allows for that merchant type.
- Authorization was obtained on an expired card, the situation the retired code 73 used to cover.
It is an allocation code, so your acquirer accepts the liability or challenges it through pre-arbitration. Issuers generally have 75 days from the transaction processing date to file.
Common causes
For ecommerce merchants, 11.3 is almost always about when and how much you capture:
- Pre-orders and backorders authorized at checkout and captured weeks later, after the approval lapsed
- Delayed capture at shipment when fulfillment takes longer than the authorization lasts
- Order edits: the customer adds an item or upgrades shipping, and you capture the new total against the old approval
- Split shipments where the combined captures exceed the original authorization
- Hospitality and rentals: final bills or added tips well above the estimated authorization
Evidence that wins an 11.3 dispute
- The authorization record: approval code, approved amount and date, showing it covers the captured transaction.
- Proof the approval was valid on the capture date, or a fresh authorization obtained before capture.
- For amount differences, the reauthorization or incremental authorization covering the higher total, or proof the difference was within Visa’s allowed tolerance for your merchant type.
- For split shipments, each capture mapped to its authorization, showing the totals don’t exceed what was approved.
If the cardholder doesn’t dispute the purchase itself, say so. But the issuer’s question is narrow: was there a valid approval for this amount on this date?
How to prevent 11.3 chargebacks
- Reauthorize before capturing when a pre-order, backorder or slow fulfillment pushes capture past your processor’s authorization window.
- Reauthorize when the total goes up. Never capture more than you were approved for unless your processor confirms a tolerance applies.
- Use account updater services so stored cards aren’t charged after they expire.
- Ask your processor for the authorization validity periods that apply to your transactions, and set capture rules in your order platform accordingly.
Should you fight or accept?
Fight when you have an approval for the full amount that was still valid when you captured, or a reauthorization that covers it.
Accept when the approval had expired or the capture exceeded it with no fresh authorization. You can’t add evidence after the fact to cure a missing approval. Fix your capture rules, because one backorder process can generate these at scale.
Frequently asked questions
What is Visa reason code 11.3?
Why do ecommerce merchants get 11.3 chargebacks?
How do I win a Visa 11.3 chargeback?
What did Visa 11.3 replace?
Related reason codes
Browse every Visa, Mastercard, Amex and Discover reason code →