Visa 11.3 - No Authorization
- Three ways in: a required authorization was missing, a valid authorization was processed too late, or no authorization was required but the processing rules weren't met
- What causes it: offline terminals, floor limits (the amount above which a sale must be approved online), a system failure, or a phone approval (voice authorization) nobody wrote down
- Floor limit is a Visa-established amount. Get the limit that applies to you from your acquirer; required-approval rules have their own exceptions
- The issuer's standard filing window is 75 calendar days from processing, not your response deadline. Time frames
- Answers include an overlooked credit or reversal, an invalid dispute, a corrected transaction date, and records disproving lateness. See Representment Options
- Late presentment lives here now. Visa retired 12.1 and folded it into 11.3. Clearing too late
Got this code?
Your deadline: The date on your notice wins. Behind it, Visa's default network limit for your acquirer's first action is 30 days counted from the dispute's processing date, with shorter domestic windows (Nigeria domestic 2 business days, Tanzania domestic 20 calendar days). Your processor can set an earlier date.
The claim: No Authorization/Late Presentment. A required authorization was missing, or processing fell outside the allowed period, or the processing rules weren't met where no authorization was required.
Records that answer it:
- Authorization logs: was an authorization actually obtained?
- A voice authorization approval code, if you used one
- System records of the authorization request and response
If you can't support it: A missing online approval isn't automatic full-amount liability. Check the three alternatives, the amount limits and any overlooked credit under Conditions for Valid Dispute before accepting.
Next: Decide whether it's worth fighting, then build the response with the Representment Workflow.
Overview
This code covers missing required authorization and late processing, including sales that had a valid authorization but cleared too late, and sales where no authorization was required but processing was late. Offline terminals, floor limits and system failures cause these. Amount limits and authorization exceptions apply, so a missing online approval alone isn't full-amount liability.
When This Code Applies
- A required authorization never went out
- The sale sat under a floor limit and was still processed late, or the processing rules weren't met
- A system failure killed the authorization
- Someone keyed the sale in manually
- Voice authorization happened but nobody documented it
- The sale cleared after the authorization window closed. That's late presentment, the old 12.1
Conditions for Valid Dispute
Issuer Must Verify
- One of the three: required authorization missing, valid authorization processed outside the allowed period, or no authorization required but the processing requirements not met
- You captured and settled it anyway
- The issuer took a financial loss, and certifies the account status on the dispute processing date: a credit problem, closed, or fraud. An ATM deposit adjustment is the exception. The customer doesn't have to deny the purchase
Scenarios
- The terminal was running offline
- The sale fell under a floor limit
- Paper or backup processing
- A timeout with no retry
Time Frames
| Scenario | Dispute Window |
|---|---|
| Standard purchase | 75 calendar days from the transaction processing date. The adjustment-date clock is narrower: 75 days from the adjustment's transaction date, only for US domestic adjustments of ATM cash withdrawals or PIN-authenticated Visa debit sales, and India and Nepal domestic adjustments of ATM cash withdrawals. Brazil domestic installments: the sale must have been processed between the approval response date and the first installment's processing date (Table 11-50, footnote 1) |
NETWORK Visa public rules, 24 October 2026 edition, section 11.9.3.4, Table 11-50, printed page 726. The adjustment-date clocks apply to US domestic ATM and PIN-authenticated Visa debit adjustments, and India and Nepal domestic ATM adjustments. Answer by the date on your notice.
Floor Limits
Current Floor Limits
A floor limit is a Visa-established amount. The public rulebook doesn't print a current numeric table here, so get the limit and configuration that apply to you from your acquirer. Required-approval rules carry specified exceptions. Zero-value account verification isn't a purchase floor limit.
| Transaction Type | Floor Limit |
|---|---|
| E-commerce | Ask your acquirer for the applicable Visa limit and configuration |
| Card-present | A Visa-established amount; confirm your configuration with your acquirer |
| Some hospitality | Special rules may apply |
Floor Limit Rules
- Confirm the applicable card-not-present floor limit with your acquirer
- Required approval has specified exceptions; check them before assuming a small sale was safe
- Floor limits are Visa-established. Your acquirer holds the applicable limit and configuration
- Airlines and hotels have special rules
Representment Options
Pull the authorization and processing records first. The permitted answers also cover an overlooked credit or reversal, an invalid dispute, a corrected transaction date, and records disproving lateness while proving the required authorization. The special-authorization route needs the sequence: the first request carrying the estimated indicator and later requests the incremental indicator, one shared Transaction Identifier, timely clearing, and certified start and end dates with the approved authorization dates, amounts and codes.
1. Authorization Was Obtained
Evidence required:
- Authorization code
- Authorization request/response logs
- Network records
- Matching timestamps
2. Voice Authorization
Evidence required:
- Voice authorization approval code
- Call recording (if available)
- Operator reference number
- Time and date of call
3. Special Circumstances
Evidence required:
- Outage records tied to a permitted route, such as deferred authorization where its indicators and timing apply. An outage on its own isn't a waiver
- Processor confirmation
- Good intent on its own isn't an answer. The records have to meet one of the routes above
Why This Happens
Common Causes
- Offline mode - the terminal lost its connection
- Floor limit assumption - thinking small amounts don't need authorization
- System failure - the authorization system went down mid-sale
- Manual processing - paper backup with no authorization code
- Incremental transactions - adding to an existing authorization
Which defenses hold up
| Defense Type | Relative strength |
|---|---|
| Proof of authorization | Answers a missing-authorization claim; lateness is tested separately |
| Voice authorization documented | A phone approval with its code and record |
| No authorization on file | Still check amount limits, exceptions and any overlooked credit |
Track your own win rate by reason code.
Common Mistakes
- Assuming offline is okay - deferred authorization only where its indicators and timing permit it
- Floor limit misunderstanding - confirm the Visa-established limit with your acquirer instead of assuming a figure
- Voice authorization without code - you need the operator's approval code
- Amount drift - check the final amount against the authorization and its permitted variations, with the right estimated or incremental indicators and the same identifier. An increment doesn't restart the processing clock
Late presentment: the retired 12.1
Late presentment sits inside 11.3 now. The current rules place it here, and that's where you argue the defense.
The transaction was presented for clearing past the allowed timeframe after authorization. Test lateness against the window that applies to that sale; amount limits can apply too.
Seeing 12.1 on a current notification? Ask your acquirer (the bank behind your processor) to identify the actual dispute condition on the case. Don't diagnose it from the printed code alone. Prove the transaction cleared inside the allowed window, or that an eligible exception applied.
The processing windows. In general, 10 calendar days for cardholder-initiated card-absent sales, and 5 for the stated other card-present and merchant-initiated rows, counted from a valid authorization. Extended cardholder-initiated card-absent sales with the extended-authorization indicator get 30; estimated-authorization lodging, cruise and vehicle rental get 30; other listed rentals get 10. Country overrides and a separate Europe contactless submission rule also apply. An incremental authorization doesn't restart this clock. These are processing windows, separate from the issuer's 75-day filing clock. Authorization Windows carries the split.
What causes it: delayed batching or settlement, a system failure that delayed clearing, manual processing delays.
| Defense | Evidence |
|---|---|
| Cleared within the window | Transaction date and time, clearing date and time, proof it was within the allowed window |
| An eligible extended window applies | The transaction type, its indicators and timing records. An MCC alone doesn't establish it |
| Customer agreed to the delay | Consent alone doesn't extend a Visa processing deadline. A booking record may support the eligible type and timing, nothing more |
If the sale was late under the window that applies to it, and no other route fits, accept the dispute.
Where it breaks. Batching causes these. Daily processing is the safer habit, but lateness is tested against the window for that sale; a seven-day schedule isn't automatically a violation.
Failed settlements are the quiet killer. A batch fails, nobody's watching the queue, and the window closes while it sits there. Alert on it and retry the same day.
Capture at fulfillment, not later. The longer you hold an authorization, the more ways to miss the clock.
Eligible types matter too. Lodging, cruise and vehicle rental can get the estimated-authorization window, but the type, indicators and timing have to line up. An MCC alone doesn't earn it.
Log timestamps for everything. Without them you can't prove you cleared on time.
Related Codes
- 11.1 - Card Recovery Bulletin
- 11.2 - Declined Authorization
- 12.1 Late Presentment (retired into 11.3)
Prevention Strategies
System Configuration
- Always online - no store-and-forward, no offline mode
- Floor limit - run the Visa-established limit your acquirer gives you, and require approval where the rules require it
- Authorization validation - block any capture that doesn't have a code
- Backup procedures - know what to do when authorization is down
Technical Controls
- Real-time monitoring - know when authorization is down
- Queue and retry - Don't skip authorization, wait for it
- Authorization code validation - verify the code before you capture
- Fallback alerts - somebody gets paged when a terminal drops
Process Controls
- No paper backup - or strict authorization requirements for paper
- Voice authorization procedures - log the code, the operator and the time
- Training - your staff knows an authorization is mandatory
- Daily reconciliation - catch the missing authorizations early
Next Steps
Prevent future 11.3 chargebacks:
- Never process without a required authorization, and clear inside the window for that sale
- Confirm the applicable floor limits with your acquirer
- Implement queue-and-retry for system outages
- Review authorization basics
See Also
- Reference - The whole reference section
- Time Frames - Dispute and response deadlines
- Is it worth fighting? - Weigh what responding costs against accepting this chargeback
- Authorization Basics
- Authorization Optimization
- Operations