Visa · Processing Errors
Reason code 12.6.2: Paid by Other Means
The cardholder paid for the purchase through another method, such as cash, check, a different card, or a wallet, and was charged on their Visa card as well. The card transaction is therefore redundant, and the issuer is recovering a payment the merchant already received elsewhere. It shares the 12.6 family with duplicate processing but involves two different payment instruments rather than one instrument charged twice.
Issuer filing window
120 days from the transaction processing date
Merchant response window
typically 20-30 days to respond, depending on the acquirer
Why 12.6.2 chargebacks happen
- A declined-looking card payment was completed with cash or a second card, but the original card charge later settled anyway.
- An invoice was paid by bank transfer while an auto-billing system also charged the card on file.
- A customer switched payment methods mid-checkout and both attempts ended up captured.
- A phone order taken with one card was also processed against a stored card from a previous purchase.
- In-store staff ran the card, hit an error screen, took cash, and never voided the card transaction that had actually authorized.
How to fight a 12.6.2 chargeback
- Show that no alternate payment exists for this purchase by producing the full payment record for the order with the card transaction as its only settlement.
- If the customer is pointing to a different payment, tie that payment to a different order or invoice with documentation of both purchases.
- Provide receipts distinguishing the transactions, since alleged double payments often turn out to be two separate purchases on different days.
- Present the refund reference if you already returned the redundant charge, which moots the dispute.
- Concede confirmed cases where cash or another instrument genuinely covered the same order and no correction was issued.
How to prevent 12.6.2 chargebacks
- Void or reverse card authorizations immediately whenever a customer completes payment by another method.
- Link every payment to an order ID and block a second settlement against an order already marked paid.
- Reconcile invoice payments against auto-billing runs before each billing cycle so bank-transfer payers are not also card-charged.
- Train counter staff that an error screen does not mean the authorization failed, and require checking the terminal record before taking alternate payment.
- Send payment confirmations that state the method charged, prompting customers to flag double payments to you instead of their bank.
Frequently asked questions
- What is the difference between 12.6.1 and 12.6.2?
- Both live under the 12.6 duplicate umbrella, but 12.6.1 means one card was charged twice for the same purchase, while 12.6.2 means the purchase was paid by some other method and the card charge duplicates that payment. The evidence differs: for 12.6.1 you prove two distinct purchases, for 12.6.2 you prove the card was the only payment for the order. Identify which claim the issuer is making before assembling your response.
- A customer paid an invoice by bank transfer and my system also charged their card. Now what?
- Refund the card charge as soon as the duplicate is confirmed rather than waiting for the dispute to resolve. If the 12.6.2 has already been filed, respond with the refund reference; if it settles anyway, work the double credit back through your acquirer. Then fix the root cause by reconciling invoice payments against your auto-billing queue before each run.
- How do I prove the card was the only payment method used?
- Produce the complete payment ledger for the order showing a single settlement, plus the order confirmation identifying the card as the selected method. If the customer references a cash receipt or transfer, obtain its details and map it to a different order where possible. A clean order-to-payment audit trail is what wins these, so linking every payment to an order ID pays off directly.
Related Visa codes