What Visa reason code 11.2 means
Every card payment starts with an authorization request. When the issuer answers with a decline or a pick up response, the merchant must not complete the sale. 11.2 is the issuer's remedy when a declined transaction still reached settlement. It happens through forced posting, through retry logic that settles an old declined attempt, or through a mismatch between the approved request and the settled transaction. Unlike fraud codes, 11.2 does not require the cardholder to say anything. The issuer only needs its own authorization log.
Typical triggers for an 11.2 chargeback
-
A terminal or staff member forcing a sale through after a decline, sometimes with a made up approval code.
-
Billing systems that retry a declined renewal and then settle the original declined attempt.
-
Offline transactions submitted later and declined, while the goods were already handed over.
-
A settled transaction that does not match the approved one in amount, date or card details.
Time limits for Visa 11.2
Issuers typically have around 75 days from the transaction processing date to file authorization chargebacks, but confirm current timelines with your acquirer. Your response window is set by your processor, often between 7 and 21 days, and the due date is the one that counts.
Evidence that wins an 11.2 dispute
-
The authorization record with the approval code, date, amount and card details matching the settled transaction.
-
If the first attempt was declined, proof of a later approved authorization for the same transaction that was the one you settled.
-
Logs showing the settled transaction is linked to the approved request, not to the declined one.
-
Proof of a refund or credit issued before the dispute.
What to avoid when you respond
-
Do not argue that the customer received the goods or used the service. Delivery does not cure a declined authorization.
-
Do not send a voice or manual approval code you cannot trace in the issuer's records.
-
Do not settle declined subscription renewals. Retry for a new approval or stop service.
How to prevent Visa 11.2 chargebacks
-
Never force post a declined transaction. Ask for another payment method instead.
-
Make sure retry logic settles only the attempt that was approved.
-
Respect pick up responses and stop retrying that card.
-
Reconcile settled transactions against approval codes daily so a mismatch is caught early.
How 11.2 appears in Stripe
On Stripe a declined payment does not create a charge that can be settled, so 11.2 is uncommon. When it does appear, Stripe usually shows authorization codes like this under the reason general, and the raw code 11.2 is always in the network reason code field. NoChargeback reads the charge outcome and authorization details and attaches them as evidence. See Stripe chargeback protection and dispute automation.
Rebuttal letter opening for Visa 11.2
We are responding to the dispute filed under Visa reason code 11.2. The transaction was approved by the issuer: the attached authorization record shows the approval code, date and amount, and these match the settled transaction exactly, so the transaction was not completed after a decline.
Can a merchant win a Visa 11.2 chargeback?
Yes, when you can show a valid approval for the exact transaction you settled. If the transaction was settled after a decline, the dispute is usually lost.
What is the difference between Visa 11.2 and 11.3?
11.2 means the issuer declined the authorization and the sale went through anyway. 11.3 means no valid authorization was obtained at all, or it did not cover the settled amount or date.
Do subscription businesses get 11.2 disputes?
Sometimes, when billing systems settle a declined renewal attempt. Settling only approved attempts prevents it.