A processing-error code triggered when the merchant settled the transaction too long after the original authorization.
Visa 12.1 is not a claim about whether the merchant performed. The buyer may have ordered, received, and used the product. The issuer is enforcing a network rule about timing, and the evidence that wins is documentation of the authorization-to-settlement gap and any explicit cardholder consent to a delayed charge, not proof of delivery.
How the dispute actually arrives
A merchant receives a 12.1 notification through their processor when the issuer's automated review flags the time between authorization and settlement against the presentment window in Visa rules. The notification cites the original authorization date and the settlement date, and the merchant has 30 days to respond.
A 12.1 against an e-commerce seller usually arrives on a pre-order or back-order that authorized at checkout and settled when the goods finally shipped. A 12.1 against a hotel or rental business arrives when an authorization held against a reservation settled weeks or months later. Both patterns share the same root: the operational window between authorize-and-settle widened without the merchant tracking against the network rule.
What the issuer is looking for
Issuers reviewing a 12.1 ask two questions. Was the presentment window exceeded, and is there documented cardholder consent to a delayed charge.
The merchant cannot win the first question retroactively. The authorization date and the settlement date are both fixed in the processor's logs, and the gap is what it is. The case rests on the second question: did the cardholder agree, in writing or at point of sale, to a charge that would settle later than the standard window.
A pre-order disclosure that stated the card would be charged on shipment, a hotel folio signed at check-in that authorized the final charge at check-out, or a subscription term that defined the billing date are the records the issuer wants. Where consent is documented, the dispute is defensible. Where consent is implicit or buried, the dispute is harder.
Common scenarios merchants see
A pre-order that authorized at checkout and settled weeks later when stock arrived. The defense is the pre-order disclosure at checkout that named delayed settlement as the model. Without it, the case is weak.
A hotel or rental authorization held against the reservation that settled at check-out. Hospitality has carve-outs in Visa rules for this exact pattern, but the merchant must cite them and produce the signed folio or rental agreement.
A subscription where the renewal was authorized but the settlement batch slipped. This is usually an operations issue at the merchant. If the gap is brief and the cardholder's account shows continued service, the dispute may still be winnable on a small-window argument.
A merchant operations failure where batches were not closed on time. These cases are usually lost. The right move is often to issue the refund, fix the batching process, and not represent.
What this code is not
Reason code 12.1 is not a fraud claim and not a claim about non-receipt. If the buyer says the charge was unauthorized, the dispute belongs under Visa 10.4 (card-absent fraud). If the buyer says the goods never arrived, it belongs under Visa 13.1 (merchandise or services not received). Merchants who submit proof-of-delivery evidence on a 12.1 are arguing the wrong case.
Where this fits in our service
Visa reason code 12.1 is a code we draft rebuttal letters against where the merchant has documented consent to a delayed charge. The letter cites the authorization date, the settlement date, the specific Visa rule provision that permits the delay in the relevant business model, and the cardholder's acceptance record. If the gap exists without documented consent, we will say so before drafting. If you are reading this because you just received one, you can start with a free first letter.
Official source: Visa rules. Last reviewed 2026-05-11.