Visa reason code 12.6.1:
Duplicate Processing

What Visa 12.6.1 means

The cardholder claims a single transaction was processed more than once using the same payment credential, on the same transaction date, for the same amount.

Common causes

• Customers double-clicking 'Pay' or refreshing during checkout
• Batches sent to the processor twice
• Two receipts created for the same purchase
• Customers mistaking a pending authorization plus capture for two charges

Evidence that answers it

• Order records showing two separate purchases (different order IDs, items, times or shipments)
• Processor records showing one charge was voided or refunded
• Proof of a credit or reversal for the duplicate

How to prevent it

• Use idempotency keys and disable the pay button after the first click
• Reconcile settlement batches daily to catch double submissions
• Explain pending authorizations in order emails

Time limits and caveats

Collaboration workflow. Issuer time limit: 120 calendar days from the transaction processing date. 12.6.1 and 12.6.2 share the parent condition 12.6.

How Verdikx helps with 12.6.1

Verdikx's duplicate playbook for 12.6.1 requires each charge to be tied to its own order and fulfillment, with any refund of the duplicate. Its guidance is explicit: do not contest a true duplicate, refund it. When the charges are separate orders, the AI draft shows that for your review.