Can I win a Visa 11.2 chargeback?

Only if the premise is wrong, meaning you can show the settled transaction actually references an approved authorization. Gateway logs with the approval code, amount, and timestamp are the decisive evidence. If the capture genuinely followed a decline with no subsequent approval, the dispute is valid and fighting it is throwing money after bad.

Do payment retries on declined subscriptions cause 11.2 chargebacks?

Retries themselves are fine when each attempt is a new authorization request and you only capture approved attempts. The 11.2 risk appears when billing systems capture against the original declined authorization or force the transaction through. Separately, Visa charges misuse fees for excessive reattempts of the same declined transaction, so retry logic needs both correctness and restraint.

What does it mean to force-post a transaction?

Force-posting means submitting a transaction for settlement with a manually entered approval code instead of a real-time issuer approval. It was designed for voice-authorization fallbacks but is widely abused to push declined sales through. Any force-posted transaction that the issuer did not actually approve is an easy 11.2 for the issuer to win.

Visa · Authorization

Reason code 11.2: Declined Authorization

The merchant submitted a transaction for settlement after the issuer declined the authorization request. In other words, the sale was completed despite a decline, whether by forcing the transaction, resubmitting until something stuck, or a technical failure between the gateway and the processor. Issuers treat this as a hard rule violation, and valid cases are nearly impossible to defend.

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.2 chargebacks happen

Staff force-posted a transaction with a manual approval code after the terminal returned a decline.
A subscription billing system retried a declined recurring payment and captured funds against the original declined attempt instead of a new approval.
A gateway misconfiguration settled transactions from a batch that included declines.
The merchant split or resubmitted a declined amount in smaller pieces to sneak it past issuer controls.
An integration bug submitted the capture with a different amount or reference than the approved authorization, effectively settling against a decline.

How to fight a 11.2 chargeback

Locate a valid approval: if a subsequent authorization attempt was genuinely approved and the settlement references that approval, submit the full authorization log showing the approval code, date, and amount.
Provide gateway and processor records proving the settled transaction matches an approved authorization rather than the declined attempt.
If the issuer approved a downgraded or partial authorization that your records tie to the settlement, document that linkage precisely.
Concede quickly when the settlement really did follow a decline, because representment on a true 11.2 wastes fees you will not recover.
Check the 75-day issuer filing window before doing anything else.

How to prevent 11.2 chargebacks

Configure your gateway to make settlement impossible without a matching approved authorization.
Ban manual force-posting and voice-authorization overrides in your operations playbook, and remove the capability from staff accounts.
Audit recurring billing retry logic so each retry generates a fresh authorization request and only approved attempts are captured.
Reconcile authorization and settlement records daily to catch mismatches while they are still correctable.
Use smart retry timing on declined recurring payments instead of hammering the same card, which both reduces 11.2 exposure and protects your issuer decline rates.

Frequently asked questions

Can I win a Visa 11.2 chargeback?: Only if the premise is wrong, meaning you can show the settled transaction actually references an approved authorization. Gateway logs with the approval code, amount, and timestamp are the decisive evidence. If the capture genuinely followed a decline with no subsequent approval, the dispute is valid and fighting it is throwing money after bad.
Do payment retries on declined subscriptions cause 11.2 chargebacks?: Retries themselves are fine when each attempt is a new authorization request and you only capture approved attempts. The 11.2 risk appears when billing systems capture against the original declined authorization or force the transaction through. Separately, Visa charges misuse fees for excessive reattempts of the same declined transaction, so retry logic needs both correctness and restraint.
What does it mean to force-post a transaction?: Force-posting means submitting a transaction for settlement with a manually entered approval code instead of a real-time issuer approval. It was designed for voice-authorization fallbacks but is widely abused to push declined sales through. Any force-posted transaction that the issuer did not actually approve is an easy 11.2 for the issuer to win.

Related Visa codes