What Visa Reason Code 11.3 Means
Visa reason code 11.3 falls under the Authorization category and is titled No Authorization. It is filed when a transaction is settled without a corresponding valid authorization record. Unlike code 11.2 (where an authorization was attempted and declined), 11.3 covers situations where no authorization was obtained at all — either because the merchant's system bypassed the authorization step, the transaction was processed offline without a subsequent match to an authorization, or the authorization record cannot be located in Visa's systems.
The core issue is a records mismatch: the issuer sees a settlement debit without an authorization approval that preceded it. This can happen due to technical failures, processing errors, or deliberate bypassing of authorization requirements.
Code 11.3 differs from 11.2 (Declined Authorization) in that 11.2 involves a received decline that was ignored, while 11.3 involves no authorization attempt at all. The defense strategy is different: for 11.3, your goal is to produce an authorization record that the issuer is not seeing. For 11.2, you must prove a valid approval existed after the decline.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Visa | 11.3 | No Authorization | This page |
| Visa | 11.2 | Declined Authorization | Authorization attempted but declined; then transaction processed |
| Mastercard | 4834 | Point of Interaction Error | Covers authorization processing errors |
Common Trigger Scenarios
- Offline transaction without matching authorization. A payment processed offline (e.g., during connectivity loss) may not have a corresponding authorization in Visa's records if the offline approval cannot be matched when the connection is restored.
- Voice authorization not properly recorded. Merchants who obtain a voice authorization approval but fail to record or transmit it correctly result in settlement without a traceable electronic authorization.
- Authorization and settlement amount mismatch. If the settled amount significantly exceeds the authorized amount (beyond tip adjustments or similar exceptions), Visa may treat this as a settlement without a valid authorization for the excess amount.
- Processing system errors. Gateway or POS bugs can occasionally submit settlement records without first completing the authorization step, particularly in batch processing environments.
- Incremental authorization failures. In lodging, car rental, and similar scenarios where incremental authorizations are expected, failure to obtain proper incremental auth for final amounts can trigger 11.3.
Key Deadlines & Timeframes
| Milestone | Timeframe | Notes |
|---|---|---|
| Cardholder Filing Window | 75 days | From the transaction date |
| Merchant Response Window | 30 days | From acquirer receipt of dispute; processor deadline may be shorter |
| Pre-Arbitration | 30 days | After representment rejection, if escalation is warranted |
Evidence You Will Need
Your primary goal is to produce an authorization approval that the issuer's records are not reflecting. This requires detailed records from your payment processor and gateway.
- Authorization approval code and the corresponding authorization date and time from your gateway or processor records
- Full authorization transaction log showing the request sent to the network and the approval response received
- Voice authorization records — if authorization was obtained by phone, include the date, time, approval code, and authorization center contact number
- Acquirer authorization report confirming the approval code was validated and is on record with the acquiring bank
- Settlement-to-authorization match documentation showing the authorization approval amount matches (or is within permissible variance of) the settled amount
- Technical incident documentation if a system failure explains the authorization gap, combined with proof that proper authorization was obtained by an alternate method
How Merchants Lose This Dispute
- Unable to produce an authorization record. If your gateway records show no authorization for the transaction, you cannot win a 11.3 dispute. The absence of records is equivalent to no authorization having occurred.
- Authorization amount differs significantly from settlement. Even with an authorization record, if the settled amount substantially exceeds the authorized amount, Visa will not consider the authorization valid for the excess.
- Voice auth code not documented. A verbal claim that you called for a voice authorization is not sufficient. You need the actual approval code and evidence of when it was obtained.
- Submitting the wrong authorization record. Providing an authorization from a different transaction on the same account or from a different date confuses the review and can be treated as misrepresentation.
Response Framework Overview
- Locate the authorization record immediately. Contact your payment processor and gateway to retrieve the full authorization log for the disputed transaction.
- Confirm the approval code is valid. Verify with your acquirer that the approval code you have is legitimate and traceable in their records.
- Match amounts. Confirm the authorized amount covers the settled amount within Visa's permissible thresholds.
- Document any special authorization circumstances. If voice authorization was used or offline processing was involved, document the process in detail.
- Submit a complete, sequenced authorization trail. Provide the authorization request, response, approval code, and timestamp as a single coherent record.
Prevention Tips
- Use real-time electronic authorization for every transaction. Eliminating offline modes, batch authorization systems, and manual overrides removes the primary sources of 11.3 disputes.
- Store authorization logs for at least 18 months. Chargebacks can arrive months after the transaction. You need records that go back far enough to cover the full dispute window plus processing time.
- Reconcile authorizations to settlements daily. Any settlement without a matching authorization should be flagged and investigated before it becomes a chargeback.
- Audit your offline processing procedures annually. If your business requires offline capability, ensure the procedures for obtaining and recording authorizations are current and followed consistently.
Frequently Asked Questions
What is the difference between Visa 11.2 and 11.3?
Code 11.2 (Declined Authorization) means you received a decline response but processed the transaction anyway. Code 11.3 (No Authorization) means you never attempted authorization at all — the transaction went directly to settlement without going through the authorization step. Both are serious violations, but 11.3 sometimes has more defense options if you can produce an authorization record that the issuer's records do not reflect.
Can voice authorization defend against a Visa 11.3 chargeback?
Yes, in some cases. If your terminal was offline or malfunctioning and you obtained a voice authorization approval code from the card network's authorization center, that approval code is a valid authorization. Document the voice auth date, time, approval code, and the phone number you called. This can overturn a 11.3 dispute if the approval code is legitimate and matches the transaction amount.
How long does the cardholder have to file an 11.3 dispute?
The cardholder has 75 days from the transaction date to file a Visa 11.3 chargeback. Your acquirer will notify you and you typically have 30 days to respond. Check with your processor for their internal deadline, which may be shorter than Visa's.
Does the below-floor-limit exception still apply to Visa 11.3?
Authorization floor limits (where small transactions below a threshold did not require electronic authorization) are largely obsolete in modern Visa processing. Visa expects real-time electronic authorization for essentially all transactions. If you are relying on an old floor limit exception, you should consult with your acquirer immediately about your current authorization obligations.