What does Visa 11.3 mean?
The issuer is saying your side of the processing went wrong: the transaction was submitted without a valid authorization approval, against a declined authorization, after the authorization expired, or it was presented for settlement too late.
One correction worth stating plainly, because many code libraries still get it wrong: Visa retired reason code 12.1, Late Presentment, on April 12, 2024 and folded it into 11.3, renaming it No Authorization / Late Presentment. If you are looking for 12.1, this is where it lives now.
What causes a 11.3 chargeback?
- A transaction forced through after the authorization was declined.
- An authorization that expired before the charge was captured.
- A settlement submitted outside Visa's presentment timeframe, the old 12.1.
- A captured amount that doesn't match what was authorized.
Why do subscription businesses get 11.3?
Subscription businesses meet 11.3 through billing plumbing, not customers: a rebill retried against a stale authorization, a batch settled late after an outage, or a billing system that forces declined recurring payments through.
It deserves attention for one reason: every 11.3 still counts as a dispute in your VAMP ratio, and unlike the customer codes, this one is entirely within your control to eliminate.
Can a chargeback alert stop 11.3?
Alerts never see 11.3 coming.
Alert networks work because a cardholder contacts their bank before the dispute files. 11.3 has no cardholder in the loop: the issuer files it mechanically when the processing record is wrong. No call, no alert, nothing to intercept. The only prevention is processing hygiene, and the good news is that hygiene eliminates it completely.
Prevention here is processing hygiene, not alerts. Still worth knowing where your ratio stands, because these disputes count like any other.
How do you respond to a 11.3 dispute?
You win 11.3 by proving the processing was actually correct. Send:
- The authorization approval code for the disputed transaction.
- The authorization and settlement dates, showing presentment within the required window.
- Proof the captured amount matches the authorized amount.
- For recurring charges, the record of the valid authorization the rebill ran under.
Your processor sets your response deadline, usually 20 to 30 days from the chargeback.
How do you prevent 11.3?
- Never force a declined transaction through. A decline is an answer, not an obstacle.
- Settle promptly. Late presentment is a batch-timing mistake that a daily settlement schedule removes.
- Reauthorize before capturing when time has passed since the original approval.
- Capture the amount you authorized. Adjustments need a new authorization, not a bigger capture.
The cardholder gets Cardholder's bank can file up to 75 days to file. You usually get 20 to 30 days to respond. And the dispute counts the day it files, win or lose, which is why prevention beats response.
FAQ
What happened to Visa reason code 12.1?
Visa retired 12.1, Late Presentment, on April 12, 2024 and folded it into 11.3, which was renamed No Authorization / Late Presentment. Late-settled transactions now file under 11.3. Code libraries still listing 12.1 as active are out of date.
Can chargeback alerts stop 11.3?
No. Alerts work by catching the cardholder's call to their bank before the dispute files, and 11.3 has no cardholder in the loop. The issuer files it mechanically when the processing record is wrong. Prevention is processing hygiene: valid authorizations and prompt settlement.
How long does the bank have to file an 11.3 dispute?
75 days from the transaction, shorter than the 120 days cardholders get for fraud and consumer disputes. Authorization disputes run on the shorter clock because they are based on processing records rather than a cardholder's discovery of a charge.
Does 11.3 count toward my VAMP ratio?
Yes. VAMP counts disputes regardless of their reason code, so a mechanical 11.3 weighs the same as an angry customer's 13.2. That makes 11.3 the cheapest ratio improvement available: it is caused entirely by processing mistakes you control.
Checked against Visa's Dispute Management Guidelines (June 2024) and Visa's April 2024 dispute rule changes. Last reviewed August 28, 2026.