Visa 12.6.1: Duplicate processing (customer says they were charged twice)
The network's own name for this condition: Duplicate Processing
What the cardholder is actually claiming
The cardholder says a single transaction was processed two or more times.
The response window, and the arithmetic
- Network window
- 30 calendar days
- Counted from
- the dispute date on your notice
- Last day to respond
- dispute date + 30 days
- Worked example
- notice dated 22 November 2026 → respond by 22 December 2026
Visa gives the merchant 30 days to respond at each dispute phase. Your payment processor usually sets an earlier cut-off.
These are calendar days, not business days: a weekend or public holiday inside the window still counts towards it. Because the network window is the outer limit and your processor usually sets an earlier cut-off, treat the earlier of the two dates on your paperwork as your real deadline.
The builder dates this for you from the dispute date you enter — open it with Visa 12.6.1 selected.
The evidence checklist (5 items)
Each item carries the weight the published evidence list gives it for this code, and where to get it from your own systems.
- 01
Settlement and batch logs showing the transaction was submitted once
Decisive · answers the claim directlyVisa's stated evidence for 12.6.1 is documentation showing the two transactions in question are separate; the batch log is where that starts.
Where to get it: Export the settlement report and the batch file for the date from your processor.
- 02
Proof the two charges are separate purchases
Decisive · answers the claim directlyTwo different orders, dates or products answer a duplicate claim directly.
Where to get it: Pull both order records with their items, dates and reference numbers.
- 03
Distinct receipts with different dates or reference numbers
Strong · strongly supports the answerShows the cardholder received two separate receipts, not the same one twice.
Where to get it: Export both receipts as sent to the customer, not as re-created from your admin.
- 04
Void or credit for a genuine duplicate
Strong · strongly supports the answerIf you did charge twice, show the credit. Contesting a real duplicate costs credibility on the next case.
Where to get it: Find the void or credit in your processor and export the confirmation.
- 05
Order records showing two orders were placed
Supporting · supports the answer at the marginSupporting evidence that the customer bought twice rather than being billed twice.
Where to get it: Export the customer's order list for the period with timestamps.
What tends to decide these cases
The published evidence list for Visa 12.6.1 marks 2 items as decisive — the ones that answer the claim itself rather than supporting it:
- Settlement and batch logs showing the transaction was submitted once
Visa's stated evidence for 12.6.1 is documentation showing the two transactions in question are separate; the batch log is where that starts.
- Proof the two charges are separate purchases
Two different orders, dates or products answer a duplicate claim directly.
Below those, Distinct receipts with different dates or reference numbers, Void or credit for a genuine duplicate are strong supporting items — worth attaching, but not a substitute for the decisive ones.
The claim here is specific: The cardholder says a single transaction was processed two or more times. So the question being decided is whether that is true, not whether the customer is unhappy. Evidence that speaks to the claim carries the case; a general account of good service does not.
Rebut does not publish win rates and does not predict an outcome. What it does is tell you, from the checklist you can actually fill, how thin or complete your file is.
Questions merchants ask about Visa 12.6.1
- What does Visa 12.6.1 mean?
- Visa calls this condition "Duplicate Processing". The cardholder says a single transaction was processed two or more times.
- How long do I have to respond to a Visa 12.6.1 chargeback?
- Visa gives the merchant 30 days to respond at each dispute phase. Your payment processor usually sets an earlier cut-off.
- What evidence do I need to answer Visa 12.6.1?
- The published evidence list for Visa 12.6.1 has 5 items. The 2 that answer the claim directly: Settlement and batch logs showing the transaction was submitted once; Proof the two charges are separate purchases. Everything else supports that answer rather than replacing it. Each item on the page says where to get it from your own systems.
- Does Rebut guarantee the outcome of a Visa 12.6.1 dispute?
- No. Rebut does not publish win rates and does not predict an outcome. It checks the file you actually hold against the published evidence list for this code, shows which decisive items are missing, and writes the rebuttal letter for you to submit.
Sources
The evidence list above was last reviewed on 8 November 2026; the response window is the merchant window the network publishes. Where a network keeps its full rulebook behind a merchant login, the network's own public page is cited rather than a third-party summary. Networks revise their rules, so confirm both against the notice from your processor before you submit.
Build the rebuttal for this code
Opens the builder with Visa 12.6.1 already selected. Enter the dispute date and order value, tick the evidence you hold, and you get the dated deadline, the ranked gaps and a filled-in letter. No account, no email.
Open the builder with Visa 12.6.1 selectedRelated Visa codes
- 12.5Incorrect amount (customer says they were charged a different figure)
- 10.4Fraud — card not present (customer says they never bought it)
- 10.5Visa monitoring programme (your business is enrolled in a VFMP)
- 13.1Goods or services not received (customer says nothing arrived)
