Visa Reason Code 11.2: Declined Authorization

What Visa reason code 11.2 means

Reason code 11.2 is an Authorization dispute. The issuer is saying: we told you no, and you processed it anyway. The authorization request came back declined (or with a pick-up response), and a transaction still reached clearing.

That can happen deliberately, with a “forced” sale keyed in with a made-up or reused approval code. More often in ecommerce, it is a systems problem: an order platform that captures against the wrong authorization attempt, or a billing engine that treats a decline as a soft failure and settles anyway.

11.2 is an allocation code. Your acquirer accepts the liability or challenges it through pre-arbitration, and issuers generally have 75 days from the transaction processing date to raise it.

Common causes

• Subscription retries: a renewal is declined, retried, and the captured transaction references the failed attempt instead of the approved one
• Forced sales: staff enter a voice-authorization or approval code that wasn’t actually issued for this transaction
• Split shipments and reauthorizations: a later capture relies on an authorization that was declined when re-requested
• Offline processing during an outage, where the card was later declined
• Ignoring decline codes that indicate the card is closed or the cardholder has asked to stop payments

Evidence that wins an 11.2 dispute

1. The approval record for the disputed transaction: approval code, date, amount and transaction identifier from your processor.
2. The full authorization history where a decline was followed by an approval, showing the captured amount matches the approved attempt.
3. Order and clearing data tying the settled transaction to the approved authorization (order ID, amount, timestamp).
4. For subscription renewals, the billing log showing which retry succeeded and that no capture was made against a declined attempt.

Customer history and delivery proof don’t answer an authorization claim. The issuer wants to see a valid approval.

How to prevent 11.2 chargebacks

• Never force a sale after a decline. Ask for another payment method instead.
• Configure your billing platform so captures always reference an approved authorization.
• Respect decline codes. Visa limits retries on certain declines, and repeatedly retrying a closed or stopped card invites disputes and network fees. Your processor can tell you which codes not to retry.
• Use account updater services for stored cards so renewals don’t run against expired or replaced cards.

For recurring billing more broadly, see our guide to subscription chargebacks.

Should you fight or accept?

Fight when you have an approval for the exact transaction, including a successful retry. These disputes are often won on the authorization log alone.

Accept when the record really does show a decline followed by a capture with no approval. Fix the process that let it through: a forced-sale habit or a billing bug will keep generating 11.2s until it’s found.