Visa 12.1 (Retired) - Late Presentment
- No live 12.1 can exist. Visa merged authorization and clearing into one clock on 13 April 2024 and the old filing windows have closed
- A 12.1 on a current notification means a stale template or a legacy system. Ask your acquirer for the real condition and expect 11.3
- Current windows are 10 calendar days card-not-present and 5 card-present, counted from the authorization approval date
- The substance doesn't change either way. Prove you cleared inside the window, or that an industry exception applied
12.1 no longer exists. Visa folded late presentment into 11.3 (No Authorization) for transactions completed on or after 13 April 2024.
Working a dispute today? Use 11.3 - No Authorization. Late presentment is now a condition inside it. That's where you argue the defense.
Seeing 12.1 on a current notification? No live 12.1 can exist. The change covered transactions completed on or after 13 April 2024, and the filing windows for anything older closed long ago. So a 12.1 today is stale material: an old processor template, a legacy internal system, or out-of-date vendor docs. Ask your acquirer for the real dispute condition on the case. Expect 11.3, and answer that. The substance doesn't change either way. Prove the transaction cleared inside the allowed window, or that an industry exception applied.
Everything below describes how 12.1 worked while it was live. It's preserved because old notifications, archived case files and legacy vendor content still cite the code. The presentment windows themselves still matter under 11.3.
The transaction was presented for clearing past the allowed timeframe after authorization. Miss the window and you owned the liability. It didn't matter whether the sale itself was good.
When This Code Applies
- Transaction cleared too long after authorization
- Delayed batching or settlement
- System failure causing delayed clearing
- Manual processing delays
Time Frame Limits
Standard Presentment Windows (historical, pre-13 April 2024)
The windows below describe the old framework. Back then Visa ran authorization validity and clearing as two separate clocks. On 13 April 2024 it merged them into one authorization-to-clearing timeframe, and every number changed. Card-not-present is now 10 calendar days, card-present is 5.
Don't use this table for anything current. See Authorization Windows Reference for the rules in force today.
| Transaction Type | Presentment Window |
|---|---|
| Standard card-present | 2 days |
| Card-not-present | 1 day |
| T&E (hotels, car rental) | 15-31 days |
| Cruise lines | 60 days |
| Delayed delivery | Varies by industry |
Counting Days
- Day 0 = Authorization date
- Extensions require specific MCC codes
Under the current framework it's all calendar days, counted from the authorization approval date.
Conditions for Valid Dispute
The issuer had to show three things. The transaction was presented late, an authorization was obtained, and the window was exceeded.
Late presentment was automatic liability. Without a valid exception, you didn't have a case.
Representment Options
1. Within Presentment Window
Evidence required:
- Transaction date/time
- Clearing date/time
- Proof within allowed window
2. Valid Exception Applies
Evidence required:
- Industry exception documentation
- MCC code showing exception eligibility
- Delayed delivery proof (if applicable)
3. Cardholder Authorized Delay
Evidence required:
- Pre-authorization agreement
- Cardholder acknowledgment of delayed charge
- Booking/reservation records
Special Industry Rules
Hospitality (Hotels)
- Pre-auth at check-in
- Final charge at checkout
- Extended window for final charges
- Incidentals must be charged promptly
Car Rental
- Pre-auth at pickup
- Final charge at return
- Extended window for damage discovery
- Fuel charges may have extended window
Airlines
- Auth at booking
- Extended window for travel dates
- Ancillary charges follow standard rules
Win Rate Expectations
| Defense Type | Expected Win Rate |
|---|---|
| Within window (with proof) | 85-95% |
| Valid industry exception | 70-85% |
| Late presentment confirmed | Under 5% |
Where This Breaks
Batching causes almost all of these. If you're settling weekly, you're already late. Settle daily, or more often.
Failed settlements are the quiet killer. A batch fails, nobody's watching the queue, and the window closes while it sits there. Alert on it and retry the same day.
Capture at fulfillment, not later. The longer you hold an auth, the more ways to miss the clock.
Your MCC mattered too. Hotels, car rental and cruise lines got extended windows, but only under the right code. On the wrong code you got the standard window and nothing to argue.
Log timestamps for everything. Without them you can't prove you cleared on time, and that's the only defense that ever worked.
Related Codes
- 11.3 - No Authorization (the live condition that absorbed 12.1)
- 11.2 - Declined Authorization
- 12.5 - Incorrect Amount
Next Steps
Holding a notification that cites 12.1?
- Confirm the real condition → Ask your acquirer; expect 11.3
- Check transaction timestamp vs. settlement date → How late?
- Verify your MCC → Some categories have extended windows
- If clearly late → Accept the dispute (limited defense)
Prevent future late presentment disputes (now filed under 11.3):
- Settle batches daily (or more frequently)
- Monitor for failed settlements → Retry immediately
- Automate batch closing → Don't rely on manual process
- Review settlement process