Try free →

Network

Visa

Code

12.2

Response window

30 calendar days

Win difficulty

Medium

Dispute type

Processing Error

Visa 12.2 — Incorrect Transaction Code: What It Is and How to Respond

Note: This is almost always a merchant-side processing error. If your records confirm the wrong transaction type was submitted, accept the chargeback and re-process the transaction correctly. Only contest if you have evidence the error originated with your processor or the network.

Visa 12.2 is raised when the transaction submitted to the network used the wrong transaction code — typically a credit submitted as a debit, or vice versa. The cardholder may have been debited when a credit was owed, or the transaction type on the authorisation did not match what was processed. This is almost always a merchant-side processing error.

The distinction that matters for your response is simple: if your system sent the wrong code, accept the chargeback; if your system sent the correct code and the error happened downstream at the processor or network, you can contest it. Honest records are the foundation of any response you submit.

Common reasons you received this dispute

  1. 1A refund or credit was processed as a new charge instead
  2. 2A debit was submitted as a credit (or vice versa) during settlement
  3. 3Third-party payment software sent incorrect transaction type codes
  4. 4Manual keying error during batch settlement
  5. 5A currency reversal or chargeback was coded incorrectly in your system

Can you win this dispute?

Fight this dispute if...

  • ✓Your processing records confirm the correct transaction code was submitted and the error originated with your processor or the network
  • ✓You have corrected the error and re-processed the transaction correctly with documentation to prove it
  • ✓The dispute is based on a misunderstanding of the transaction type rather than an actual submission error

Accept this chargeback if...

  • ✗Your records confirm the wrong transaction type was submitted — particularly if a key entry or configuration error caused a credit to be processed as a charge
  • ✗The cardholder was incorrectly debited when a credit was due
  • ✗A software update or third-party tool introduced a transaction code misconfiguration that you cannot directly attribute to the processor

Evidence checklist

  1. ✅ Required

    Transaction receipt or invoice showing intended transaction type: Documentation from the point of sale or your system showing what transaction type was intended — charge, refund, credit, or reversal.

  2. ✅ Required

    Processor settlement records showing submitted transaction codes: The settlement file or report from your payment processor showing the transaction type code that was submitted for this transaction.

  3. ✅ Required

    Original authorisation record: The authorisation response showing the transaction type at the time of approval, used to compare against what was settled.

  4. ⭐ Strongly recommended

    Payment gateway confirmation of transaction codes transmitted: A log or report from your payment gateway showing the exact transaction type codes it sent to the processor — useful for distinguishing a gateway error from a merchant system error.

  5. ⭐ Strongly recommended

    Any correspondence with the cardholder about the error: Emails or support messages acknowledging the incorrect transaction and confirming what steps were taken to correct it.

How to write your response

Your response must directly address which transaction code was submitted and whether it matched the intended transaction type. If contesting, compare your authorisation record and settlement record side by side and show they match. If the error has been corrected and re-processed, document that clearly with dates.

Reference each piece of evidence as an exhibit. Keep the narrative brief — the records speak for themselves. If the dispute is a processor error, name the processor and describe what corrective action has been taken.

“We are responding to chargeback [reference] under Visa code 12.2. [If contesting:] Our processing records confirm the correct transaction code was submitted. Exhibit A shows the original authorisation and Exhibit B shows the settlement record — both reflect [transaction type]. The error did not originate with our system. We request reversal of this chargeback. [If you have corrected it:] We have identified and corrected the processing error. A corrected transaction for [amount] was processed on [date]. Please find the corrected settlement confirmation attached.”

Key deadlines

Response window: 30 calendar days from the chargeback notification date.

Retain settlement files and authorisation records for a minimum of 18 months — processing error disputes can be raised well after the transaction date.

If you have already corrected the error and re-processed, document the re-processing date — this is critical for demonstrating you have remediated the issue.

How to prevent this chargeback

  1. 1

    Audit your POS or gateway configuration quarterly: Transaction type mappings are a common source of errors after software updates. Include a transaction type verification step in your post-update testing checklist.

  2. 2

    Reconcile settlement files against authorisations daily: A daily reconciliation process will catch transaction type mismatches before they escalate to disputes — often within the same business day.

  3. 3

    Test refund flows in staging before deploying changes: Refund and credit transactions are the most common source of transaction code errors. Always test these flows in a non-production environment after any payment integration changes.

  4. 4

    Use processor reports to verify credit/debit ratios: Anomalous credit-to-debit ratios in your settlement reports are an early warning sign of transaction code misconfiguration. Set up an alert if your ratio deviates materially from historical norms.

Frequently asked questions

What is a Visa 12.2 chargeback?

Visa 12.2 is a processing error dispute raised when the wrong transaction type was submitted to the network — for example, a credit processed as a debit, or a refund coded as a new charge. It is almost always a merchant-side data entry or configuration error.

Can I win a Visa 12.2 dispute?

Only if the error did not originate with your system — for example, if a processor or network error caused the wrong transaction code to be submitted despite your system sending the correct one. If your system submitted the wrong code, accept the chargeback and re-process the transaction correctly.

How do I fix the error for future transactions?

Audit your payment gateway's transaction type mapping configuration. Test refund flows in a staging environment before deploying changes to your production payment processing. Reconcile settlement files against authorisations daily to catch type mismatches early.

How long do I have to respond to a Visa 12.2 chargeback?

30 calendar days from the chargeback notification date. Locate your processor settlement records and transaction receipts immediately and respond as soon as you have gathered the relevant documentation.

Related reason codes

Visa 12.3

Incorrect Currency

Visa 12.5

Incorrect Amount

Visa 12.6.1

Duplicate Processing

Dealing with a Visa 12.2 chargeback?

Generate a winning dispute response in minutes, or let ChargeMate handle it for you.

Generate my dispute response →Let ChargeMate handle this for me →

3 free generations included · No credit card required