12.2

What Visa Reason Code 12.2 Means for Merchants

A 12.2 dispute says you ran the wrong kind of transaction. Here is what that means and how to answer it.

Network
Visa
Published

Visa reason code 12.2 is called Incorrect Transaction Code. It is one of the codes in Dispute Category 12, which covers Processing Errors. When you see 12.2 on a notice, the card issuer is saying you ran the wrong kind of transaction. It is not saying the cardholder never made it. If you are new to these notices, start with how to read a chargeback notice.

What is Visa reason code 12.2?

The code covers a narrow set of mistakes. Under 12.2, a credit went through as a debit, a debit as a credit, or a refund replaced a reversal. In plain terms, money moved the wrong way, or you fixed a transaction with the wrong tool.

The cardholder is not claiming fraud here. They are claiming a bookkeeping error on your side. That shapes what proof will work and what will not.

Common causes of a 12.2 chargeback

Most 12.2 disputes trace back to a few habits at the register or in your back office.

  • A staff member pressed the wrong key and charged instead of refunding.
  • A refund was run as a new sale, so the customer got billed twice.
  • A reversal was needed after a void failed, but a refund was sent instead.
  • A terminal or software setting flipped credits and debits during a batch upload.

Any of these can leave the cardholder with a charge they did not expect. Their bank sees the mismatch and files under 12.2.

How to respond to a 12.2 dispute

First, check your own records. Pull the original transaction, the batch it settled in, and any refund or void tied to it. Compare what your system shows against what the notice claims.

Then pick one of two paths. A merchant can accept a Visa dispute, or reject it by sending supporting documents to its card processor. Accept when your records show the error is real and the fix is cheaper than the fight. Reject when the notice is wrong, or when you already corrected the transaction the right way.

Do not sit on either choice. Each step of a Visa dispute has a set time limit, so a late answer can lose the case. Your notice or your processor's portal shows the date. Mark it the day the notice arrives.

Evidence requirements for 12.2

Your proof must show the transaction was processed correctly, or that the error was fixed properly. Match the paper to the claim.

  • Transaction records showing the correct type of entry, debit or credit.
  • Receipts or invoices for the original sale.
  • Proof of a proper refund or reversal, with dates and amounts.
  • Batch or settlement reports that show how the transaction cleared.

Keep it simple. Visa dispute evidence must be easy to read and in English, or come with an English translation. Label each document so the reader knows what it shows. A pile of unlabeled papers helps no one.

Time limits and next steps

If you do not answer at all, you lose by default. If a Visa dispute is valid, the acquirer takes the disputed amount from the merchant account and tells the merchant. Silence has the same result.

If you do respond, know the limits of that response. An acquirer may respond only once to the original Visa dispute. The acquirer may send a Dispute Response unless the merchant already accepted the dispute through Rapid Dispute Resolution. So make your one reply count.

The issuer then reads your proof. If it still disagrees, the case can move to pre-Arbitration. In pre-Arbitration, the issuer must deal with the evidence the acquirer gave in its Dispute Response. It cannot skip it. One more rule works in your favor: after a Dispute Response, the issuer may switch dispute conditions only if the first condition was valid.

For what each later round looks like, see what happens after you answer a chargeback. Until then, keep a copy of everything you send, and watch your processor's portal for the next notice.

Sources