Visa reason code 12.2: incorrect transaction code
Visa code 12.2 covers an incorrect transaction code: a debit instead of a credit or the reverse. Learn who files, how to respond, and the deadlines.
What Visa code 12.2 means
Visa code 12.2, “Incorrect Transaction Code,” applies when the posting type causes money to move into or out of the cardholder’s account in the wrong direction. For the issuer to use this code, at least one of these three situations must apply:
- A credit was processed as a debit. The merchant should have returned money, but the posting charged the cardholder.
- A debit was processed as a credit. The merchant should have charged the cardholder, but the posting credited the cardholder’s account.
- A credit refund replaced the correct type of correction. To fix an earlier transaction submitted in error, the merchant processed a credit refund when it should have used a Reversal or AdjustmentThese are ways to correct an earlier transaction submitted in error. Under this code, they differ from posting a new credit refund.. An exchange-rate difference between the two entries can leave the cardholder under-refunded.
Source for the three situations: Visa Core Rules §11.9.1.1, Table 11-52 (ID# 0030280). Visa also explains the rule for merchants in the Visa Dispute Management Guidelines for Visa Merchants, Condition 12.2, p. 30.
Code 12.2 addresses only the direction and type of the posting. It does not address authorization, amount, currency, account number, goods, or services. If the actual issue is the currency, account number, amount, duplicate processing, or invalid data, see codes 12.3, 12.4, 12.5, 12.6, and 12.7, respectively.
The dispute amount depends on the situation. For a credit/debit swap, Visa sets it at twice the transaction amount. When a credit refund replaced a Reversal or Adjustment, the dispute amount is limited to the difference between the credit refund and the original debit.
Source for the calculation: Visa Core Rules §11.9.1.2, Table 11-53 (ID# 0030281).
Deadlines for each party under Visa 12.2
1 block represents 10 calendar days.
- IssuerFile the 12.2 disputeThe clock starts when the transaction is processed by Visa.Up to 120 calendar days
- AcquirerSubmit a Visa-permitted defense pathThe clock starts when the dispute is processed by Visa.Up to 30 calendar days
- IssuerRespond to the acquirer’s defenseThe clock starts when the acquirer’s defense is processed by Visa.Up to 30 calendar days
- AcquirerRespond to the issuer’s pre-arbitration attemptThe clock starts when the issuer’s pre-arbitration attempt is processed by Visa.Up to 30 calendar days
- IssuerAsk Visa to decide the caseThe clock starts when the acquirer’s pre-arbitration response is processed by Visa.Up to 10 calendar days
Who files the dispute and what happens next
The issuer, the bank that issued the card, opens the 12.2 dispute in VROLVisa Resolve Online is the system where the issuer opens the dispute and the acquirer submits the case response and documents.. For a credit/debit swap, the issuer must certify whether the credit was processed as a debit or the debit as a credit. For a credit refund used instead of a Reversal or Adjustment, it must explain why the refund was processed in error and provide the dates of the original transaction and the Credit Transaction. Both the explanation and the two dates are required.
Source for the issuer’s requirements: Visa Core Rules §11.9.1.5, Table 11-56 (ID# 0030283).
The issuer has 120 calendar days from the Transaction Processing DateThe date Visa processes the transaction. For 12.2, it usually starts the issuer’s deadline to file the dispute.. If the case involves a credit refund used instead of a Reversal or Adjustment, the 120 days start on the Processing Date of that credit refund.
Source for the filing deadline: Visa Core Rules §11.9.1.4, Table 11-55 (ID# 0030282).
When the issuer opens the case, it disputes the amount and charges it back to the acquirer, the institution responsible for the merchant within the Visa network. If there is a valid basis to contest the case, the merchant gives its records to the acquirer. The acquirer sends the Dispute ResponseThe formal response the acquirer sends to Visa to contest the dispute with one of the forms of evidence allowed for this code. within 30 calendar days of the Dispute Processing DateThe date Visa processes the opening of the dispute. It starts the acquirer’s deadline to send the Dispute Response.. The issuer may then make a pre-arbitration attemptThe stage where the issuer challenges the acquirer’s response and asks for another review before the case goes to Visa for a decision.. If the case continues, the issuer is also the party that may ask Visa to decide it in arbitration.
Source for the process: Visa Core Rules §11.2.3, Table 11-2 (ID# 0030213), §11.3.1 (ID# 0030214), and §11.9.1.6, Table 11-57 (ID# 0030284).
Before building a defense, check whether this dispute is invalidProving any one condition is enough to challenge the dispute's validity.
- The disputed transaction is a Mobile Push Payment Transaction — code 12.2 does not apply to this transaction type.
Source:Visa Core Rules §11.9.1.3 — Tabela 11-54 (Invalid Disputes, ID# 0030551)
How to reduce the risk of this code
Visa expressly recommends training staff on the correct procedures for processing credits, debits, and Reversals. The goal is to prevent a refund from becoming a charge, a charge from becoming a credit, or the wrong method from being used to correct a transaction.
Source for the prevention measure: Visa Dispute Management Guidelines for Visa Merchants, Condition 12.2, p. 30.
The rule and accepted evidence point to the controls that should support this training:
- Confirm the direction of the posting before submission. Clearly separate the process that charges a cardholder from the process that returns money.
- Use the correct method to fix an error. If the transaction requires a Reversal or Adjustment, do not replace that correction with a credit refund.
- Keep a record of every posting and correction. Preserve the submitted type, date, amount, and receipt. Without these records, the acquirer cannot prove that the code was correct or that the merchant already corrected it.
Source for these controls: Visa Core Rules §11.9.1.1, Table 11-52 (ID# 0030280), and §11.9.1.6, Table 11-57 (ID# 0030284).
Evidence the merchant and acquirer need to gather
Before addressing the transaction code, check the only formal invalidity for 12.2. If the transaction was a Mobile Push PaymentA Visa transaction initiated by the cardholder on a mobile phone or other mobile device to pay for goods, services, or move money. Visa excludes this transaction type from code 12.2., proof of that classification is enough. The dispute is invalid, and the acquirer does not need to prove whether the posting was a credit or debit.
Source for the invalidity: Visa Core Rules §11.9.1.3, Table 11-54 (ID# 0030551).
If the claim is a credit/debit swap, Visa accepts at least one of these two responses:
- The code was correct. Send the Transaction ReceiptThe transaction record containing the information Visa requires. For 12.2, it or another processing record helps prove the type and direction of the posting. required by §5.9.2.2 or another record showing the code that was submitted. If the posting was a legitimate refund, explain and document that the credit was intentional, not the result of an error in processing the original transaction.
- The merchant already corrected the swap. Send proof of the credit or Reversal the issuer did not address. The documentation must show the amount and processing date.
The second response applies only to a credit/debit swap. It does not apply when the problem is a credit refund processed instead of a Reversal.
Source for responses to a credit/debit swap: Visa Core Rules §11.9.1.6, Table 11-57 (ID# 0030284), and Visa Dispute Management Guidelines for Visa Merchants, Condition 12.2, p. 30.
If the claim is a credit refund processed instead of a Reversal or Adjustment, one of these two forms of evidence is enough:
- The merchant issued a Reversal that was not addressed. Send the record linking that Reversal to the disputed transaction.
- There was a reason to use a Credit Transaction. Document why the credit was processed instead of a Reversal or Adjustment. To rebut the filing, also identify the original transaction and Credit Transaction dates reported by the issuer.
Source for responses to a credit refund: Visa Core Rules §11.9.1.6, Table 11-57 (ID# 0030284). The two dates the issuer must provide for this case appear in Table 11-56 (ID# 0030283).
A cardholder letter, delivery proof, and fraud evidence do not appear among the accepted responses for 12.2. They do not establish the posting type and cannot replace the records above. If the code was wrong, no correction was made, and no applicable response path can be proven, Visa’s guidance is to accept the dispute.
Source for the accepted response paths and the instruction to accept the error: Visa Core Rules §11.9.1.6, Table 11-57 (ID# 0030284), and Visa Dispute Management Guidelines for Visa Merchants, Condition 12.2, p. 30.
Frequently asked questions
Why was the Visa 12.2 chargeback filed?
Code 12.2 covers the dispute condition “Incorrect Transaction Code.” It applies when at least one of these situations occurs: a credit is processed as a debit, a debit is processed as a credit, or a credit refund is processed when a Reversal or Adjustment should have been used to correct an earlier error.
How does Visa calculate the 12.2 dispute amount?
When a credit was processed as a debit, or a debit as a credit, the dispute amount is twice the transaction amount. When a credit refund was processed instead of a Reversal or Adjustment, the amount is limited to the difference between the credit refund and the original debit (Visa Core Rules, Table 11-53).
When is a 12.2 dispute invalid?
The only formal invalidity Visa lists for 12.2 is a Mobile Push Payment Transaction (Table 11-54). A correct code and a legitimate refund are merits defenses; filing more than 120 days after the applicable processing date violates the time limit in Table 11-55.
How long does the issuer have to file a 12.2 dispute?
The issuer has 120 calendar days from the Transaction Processing Date. When a credit refund was processed instead of a Reversal or Adjustment, the 120 days run from the Processing Date of that credit refund.
Can a cardholder letter saying they no longer dispute the transaction defend a 12.2?
It is not an official response path. That option appears for codes 12.3 and 12.4, but it is absent from 12.2 in both the Visa Core Rules (Table 11-57) and the Dispute Management Guidelines for Visa Merchants (p. 30). Treat the letter as weak or supplemental material, never as the primary defense.
Can delivery proof or fraud evidence defend a 12.2?
No. Code 12.2 addresses only the direction and type of the posting. It does not address the goods, services, or who made the purchase. Delivery, product-use, or authentication evidence does not rebut a processing-error dispute. The response must stay focused on the transaction code.
View all Visa chargeback reason codes or return to Knowledge.