Visa · Authorization
Reason code 11.3: No Authorization
The merchant settled a transaction without obtaining any valid authorization, obtained it after the transaction date, or settled for an amount exceeding what was authorized. This differs from 11.2 in that no decline occurred; the merchant simply never secured a proper approval covering the settled amount. Common triggers include expired authorizations, late captures, and captures that exceed the approved amount.
Issuer filing window
75 days from the transaction processing date
Merchant response window
typically 20-30 days to respond, depending on the acquirer
Why 11.3 chargebacks happen
- The capture happened after the authorization expired, often because of shipping delays on backordered goods.
- The settled amount exceeded the authorized amount, for example when adding shipping, tips, or upsells after approval.
- An order management system captured a transaction whose authorization was never actually requested due to an integration bug.
- Incremental or delayed charges, such as damage fees or subscription overages, were settled without fresh authorization.
- A fulfillment hold pushed capture weeks past the sale while the original approval quietly lapsed.
How to fight a 11.3 chargeback
- Produce the authorization record showing an approval that covers the settled amount and predates the capture, including the approval code and dates.
- For incremental amounts, show the additional authorizations you obtained for each increment rather than a single original approval.
- If the settled amount differed for a legitimate operational reason within Visa rules, such as documented gratuity tolerances in eligible segments, provide that justification.
- Confirm the dispute arrived within the 75-day issuer window and challenge late filings.
- Where no valid authorization exists, weigh conceding against your representment costs, because true no-authorization cases are effectively unwinnable.
How to prevent 11.3 chargebacks
- Capture within the authorization validity window, and request a fresh authorization whenever fulfillment slips past it.
- Never settle for more than the authorized amount; authorize the final total including shipping and taxes before capture.
- Use incremental authorization support for order additions instead of inflating the capture.
- Alert on stale uncaptured authorizations in your order pipeline so delayed shipments trigger reauthorization automatically.
- Test integration changes against an authorization-to-capture reconciliation suite before deploying billing code.
Frequently asked questions
- How long is a Visa authorization valid before capture?
- It depends on the merchant segment and transaction type, with ecommerce authorizations generally needing capture within a defined settlement window before they expire; many card-not-present merchants work to roughly a 7-day standard for final authorizations. If fulfillment slips past the window, the safe play is a new authorization before capture. Settling on an expired approval invites an 11.3 with no defense.
- What is the difference between 11.2 and 11.3?
- 11.2 means the issuer said no and the merchant settled anyway; 11.3 means the merchant never obtained a valid approval covering the settlement, whether because authorization was skipped, expired, or exceeded. The evidence to fight 11.3 is an approval record matching the captured amount and timing. Both share the 75-day issuer filing window.
- Can I capture more than the authorized amount?
- Outside narrow tolerance allowances in specific segments, no. If the final total grows because of shipping, upsells, or added items, obtain a new or incremental authorization for the difference before capture. Settling above the approved amount exposes the entire transaction to an 11.3 dispute, not just the overage.
Related Visa codes