Visa reason code 12.2:
Incorrect Transaction Code

What Visa 12.2 means

The issuer claims the transaction code was incorrect, so the cardholder was debited when they should have been credited, or vice versa, or a credit refund was used to fix an error that needed a reversal or adjustment.

Common causes

• Staff choosing 'sale' instead of 'refund' on the terminal
• Correcting a mistaken charge with a refund instead of voiding or reversing it
• Integration bugs that send refunds as captures

Evidence that answers it

• Processor records showing the transaction was correctly processed as a debit or credit
• An explanation that a credit was a genuine refund, not a correction of a processing error
• Proof that a correcting credit or reversal was already processed (not valid where a credit was used instead of a reversal)

How to prevent it

• Void same-day errors instead of refunding them
• Restrict refund permissions and require a second check for manual refunds
• Test refund and capture flows after every checkout or POS update

Time limits and caveats

Collaboration workflow. Issuer time limit: 120 calendar days from the transaction processing date or the processing date of the credit refund.

How Verdikx helps with 12.2

Verdikx's processing-error playbook for 12.2 asks for the processor's transaction record and the order, and the packet includes any refunds on the order, so you can show whether a credit was a deliberate return or a fix for a mistake. The AI draft explains the sequence for you to review.