12.5

What Visa Reason Code 12.5 Means for Merchants

The cardholder says the amount you charged is wrong. Here is what counts as a 12.5 dispute and how to answer it.

Network
Visa
Published

A cardholder looked at their statement and saw a number that did not match what they agreed to pay. Their bank sent the charge back to you. The notice points to Visa reason code 12.5, which is Incorrect Amount. Here is what that means and what to do about it.

What Visa reason code 12.5 is

Visa dispute condition 12.5 is Incorrect Amount. It belongs to Dispute Category 12, which is Processing Errors. That category covers mistakes made while handling a payment, not fraud and not a fight over the goods.

Under 12.5, the charged amount is wrong. Maybe an adding error happened, or two digits got swapped when the total was keyed in. The cardholder says they agreed to one price and you took a different one.

A Visa dispute is how a card issuer sends a contested transaction back. If the dispute is valid, the acquirer takes the disputed amount from your merchant account and tells you. You can accept it, or reject it by sending supporting documents to your card processor.

Common scenarios that trigger a 12.5 dispute

Most 12.5 cases come from a small slip at the register or the terminal. Watch for these.

  • A clerk typed the total by hand and hit the wrong key.
  • Two digits were swapped, so $46 became $64.
  • A tip or add-on was added twice.
  • A discount or coupon was not taken off before the card was charged.
  • A partial payment was not subtracted, so the card was charged for the full price.

The error can also sit on your side of the counter. A terminal set up wrong, or a price file loaded with the wrong numbers, can charge every customer the wrong amount for weeks.

When a 12.5 dispute is not valid

Some claims do not fit this code. A 12.5 dispute is invalid for a No-Show Transaction. It also does not cover a T&E gap between the quoted price and the actual charges at a hotel or similar business. Those are different situations with their own rules.

It is also not the right code when the cardholder agreed to the amount and simply regrets it. If the number on the receipt matches the number they approved, the claim is not about a processing error.

Note that 12.5 is not the only amount-related code. If the charge went through in the wrong currency, that is 12.3, incorrect currency. If the wrong account was hit, see 12.4, incorrect account number.

How to respond to a 12.5 chargeback

First, pull the real records. Get the receipt, the signed order form or the terminal record, and any quote or invoice the customer saw. Compare the charged amount to what the customer approved.

If the charge was right, say so plainly. Show the price the customer agreed to and the amount that was taken. Point to the spot on the receipt where they match. Visa dispute evidence must be easy to read and in English, or come with an English translation.

If you did charge the wrong amount, do not fight the whole dispute. Accept it, or refund the difference if your processor allows that. Pushing back on a real error wastes time and can cost you more.

Each step of a Visa dispute has a set time limit, so a late answer can lose the case. Send your reply early.

Your reply is not always the end. An acquirer may respond only once to the original dispute. After your Dispute Response, the issuer must deal with the evidence you gave. It can still push the case into pre-Arbitration, and it may switch dispute conditions only if the first condition was valid. Your acquirer cannot send a Dispute Response if you already accepted the dispute through Rapid Dispute Resolution.

Best practices to prevent 12.5 disputes

  • Check typed-in totals against the screen before charging the card.
  • Print the amount on the receipt and have the customer see it before they leave.
  • Test your terminal after any setup change, and again after a price file update.
  • Refund the difference fast when a customer spots an overcharge. A quick refund stops a dispute before it starts.

Amount slips are part of a wider family of processing errors. If the wrong transaction code was sent, that is 12.2, incorrect transaction code. If the same charge went through twice, see 12.6, duplicate processing. Bad or unreadable data in the payment fields falls under 12.7, invalid data. Visa once had 22 legacy reason codes. As part of the VCR Initiative, it consolidated them into four dispute categories, and 12.5 now sits in the Processing Errors group.

Sources