What Visa reason code 12.1 means
Every Visa transaction has two steps. Authorization reserves the funds, and presentment (clearing) sends the final record so the money actually moves. Visa expects the clearing record within a set window after the transaction date, commonly 30 calendar days for most transactions, with different rules for some transaction types. When the record arrives late and the account is closed, frozen or otherwise not in good standing on the processing date, the issuer can use 12.1 to send the transaction back. The cardholder often never contacted the bank about the purchase itself.
Typical triggers for a 12.1 chargeback
-
A batch was not closed or settled on time, so transactions sat unsent for days or weeks.
-
Orders were authorized at checkout but captured much later, for example pre orders or delayed fulfillment.
-
A terminal or gateway outage held transactions until after the window passed.
-
The transaction date in the clearing record was set incorrectly, making a timely transaction look late.
Time limits for Visa 12.1
For processing error codes the issuer typically has 90 days from the processing date to raise the dispute. Your response window is set by your processor and is much shorter, often between 7 and 21 days. In Stripe the deadline appears as the evidence due date on the dispute. Missing it loses the dispute automatically.
Evidence that wins a 12.1 dispute
-
The authorization record with its date and approval code.
-
The capture or clearing record showing the date the transaction was presented.
-
A timeline proving presentment fell inside the allowed window for that transaction type.
-
Settlement or payout reports from your processor that include the transaction.
-
Proof the account was in good standing on the processing date, if your acquirer can provide it.
What to avoid when you respond
-
Do not argue that the customer received the goods as your only point. The dispute is about timing.
-
Do not send screenshots without dates or transaction identifiers.
-
Do not refund after the dispute is opened, because the funds are already withdrawn.
-
Do not wait for a full report from your acquirer while the deadline runs out.
How to prevent Visa 12.1 chargebacks
-
Settle batches daily and alert on any batch left open.
-
Capture authorized payments as soon as the order ships, and avoid long gaps between authorization and capture.
-
Re authorize instead of capturing an old authorization when fulfillment takes weeks.
-
Monitor processor outages and confirm held transactions cleared once service returns.
How 12.1 appears in Stripe
Stripe usually groups Visa 12.1 under the reason general, because it has no dedicated late presentment reason. The raw network code is always in the network reason code field of the dispute (payment_method_details.card.network_reason_code). NoChargeback reads that field, pulls the authorization and capture timestamps from the charge, and builds the timeline for you. See Stripe chargeback protection and dispute automation.
Rebuttal letter opening for Visa 12.1
We are responding to the dispute filed under Visa reason code 12.1. The transaction was authorized on the date shown in the attached authorization record and was presented for clearing within the time limit that applies to this transaction type. The capture record and settlement report below confirm the presentment date.
Can a merchant win a Visa 12.1 chargeback?
Yes. If your records show the transaction was presented on time, or that the account was in good standing on the processing date, the issuer has no valid basis for the dispute.
Does a late capture always cause a 12.1 dispute?
No. The issuer can only use 12.1 when presentment was late and the cardholder account was not in good standing. A late capture on an active account usually settles normally.
Who has the timestamps I need for 12.1?
Your processor holds the authorization and capture times. In Stripe they are on the charge and its balance transaction, and NoChargeback collects them automatically.