11.2

Visa Reason Code 11.2: Declined Authorization

A sale went through after the card was declined. That is what 11.2 means, and here is what to do about it.

Network
Visa
Published

Visa reason code 11.2 is Declined Authorization. It is part of Dispute Category 11. That group covers authorization problems. The claim is simple. The merchant finished a sale after the authorization request got a decline or pickup response. In short, the network said no, and the sale went through anyway. If you get a chargeback with this code, the card issuer is saying a sale went through that should not have.

What is Visa reason code 11.2?

A Visa dispute is how a card issuer sends a contested transaction back. When the issuer files an 11.2 dispute, it claims your system pushed the sale through even though the card network said no.

If the dispute is valid, the acquirer takes the disputed amount from your merchant account and tells you. You can accept the dispute. Or you can reject it by sending supporting documents to your card processor. Each step has a set time limit, so a late answer can lose the case.

Common causes of 11.2 chargebacks

Most 11.2 disputes trace back to a few setup mistakes.

  • Your terminal was set to force a sale after a decline. This is sometimes called a forced sale.
  • Staff reran the card by hand after the system said no.
  • Your payment software ignored the decline response and kept the order alive.
  • A decline was treated as a network error, so the sale was retried until it went through.

None of these are cardholder fraud claims. The dispute is between the issuer and your process, not between you and the customer.

How to prevent 11.2 chargebacks

The fix is to make your system obey the decline.

  • Turn off any setting that lets staff override a decline.
  • Train staff that a decline is final. They should ask for another payment method, not rerun the card.
  • Check that your payment software stops the order when it gets a decline response.
  • Review your retry logic. A retry after a decline should never complete the same purchase.

A quick audit helps. Pull some declined authorizations. Check whether any of them became sales. If you find matches, you have found the leak.

How to respond to an 11.2 chargeback

First, decide whether the dispute is valid. If your records show the sale went through after a decline, accept it. Fighting a valid case wastes the fee and your time.

If you believe the dispute is wrong, gather your proof. Evidence must be easy to read and in English, or come with an English translation. Your reply should show the authorization response you got for that sale.

The acquirer may send a Dispute Response. It cannot if you already accepted the dispute through Rapid Dispute Resolution. An acquirer may respond only once to the original dispute, so make that one response count.

If the issuer pushes on to pre-Arbitration, it must deal with the evidence. That is the evidence the acquirer gave in its Dispute Response. After a Dispute Response, the issuer may switch dispute conditions only if the first condition was valid.

For the steps that follow your reply, see what happens after you answer a chargeback.

What makes an 11.2 dispute invalid?

There is one clean defense. An 11.2 dispute is invalid if a later authorization approved the same purchase after a decline response. The first try was declined. Then a second, separate authorization was approved. That approved one is the sale.

If you can show that, the dispute fails on its own terms. Keep the records that show the decline and the later approval.

Code 11.2 has neighbors worth knowing. Visa once used different codes. 7.1 declined authorization covered the same problem. 7.2 no authorization covered sales with no authorization request at all. Today that second case lives beside 11.2 as code 11.3.

The difference matters for your reply. An 11.2 claim says the network said no and you sold anyway. An 11.3 claim says there was no authorization attempt to answer at all. The proof that beats one will not beat the other.

If you are not sure what your notice is telling you, start with how to read a chargeback notice.

Sources