Visa reason code 11.2
Visa 11.2: Declined Authorization
What the cardholder is claiming
The issuer says you received a decline and pushed the transaction through anyway, whether by force-posting, resubmitting until something stuck, or capturing against a declined attempt.
The evidence that actually wins
Bank analysts skim responses in minutes against a checklist for this exact code. Lead with the strongest fact; never make them dig.
- ✓The approval code and full authorization log for the transaction that settled, showing a clean approval rather than a forced post
- ✓If a decline preceded the sale, proof that a new and separate authorization was requested and approved before goods or services were delivered
- ✓Processor documentation of stand-in processing if the approval came from Visa stand-in rather than the issuer
- ✓Records showing the settled amount and date match the approved authorization, not the declined attempt
The honest read
If you force-posted after a decline, you lose, and repeatedly retrying declines can also trip Visa's monitoring programs on top of the chargeback. The trap that catches honest merchants is capture logic that settles against a declined attempt after a later retry succeeded, so pull the actual auth log before deciding anything. Fight only when you can show a clean approval code tied to the settled transaction; if the trail shows a decline was overridden, refund and fix the process.
Nobody can promise you a win; the cardholder's bank decides. What you control is submitting the strongest complete case your records support, on time. Our plain-language guarantees say exactly what that means.
Fighting a 11.2 right now?
Send us the dispute and a person builds the complete, submission-ready response: the narrative mapped to 11.2, your evidence compiled and ordered, and the field-by-field walkthrough. 24-hour rush available. If our review says yours isn't worth fighting, we tell you for free.