Visa Reason Code 12.4: Incorrect Account Number

What Visa reason code 12.4 means

Reason code 12.4 is a Processing Errors dispute about which card was charged. The issuer says the transaction was processed to an account number that is wrong, or that isn’t on its file at all.

The typical story is a typo. A digit was keyed incorrectly, the transaction was processed without a successful authorization on the right card, and someone else’s account (or a non-existent one) ended up in clearing. A cardholder then sees a charge they have no connection to.

12.4 is a collaboration code. You can respond in the dispute-response stage, and the issuer may escalate to pre-arbitration if it rejects your response.

Ecommerce note: when customers enter their own card details and you authorize in real time, the issuer validates the number, so a genuine 12.4 is rare. Where it does happen, the cause is usually upstream: phone orders keyed by staff, offline processing, or stored cards corrupted in a migration.

Common causes

• Manual entry errors in a virtual terminal or POS for phone and mail orders
• Offline or paper-based processing where the number was transcribed incorrectly
• Stored-card or token migrations between gateways that mismatch customer and card records
• Charging the wrong customer’s stored card in a subscription or account system
• Transactions settled without an authorization that would have caught an invalid number

Evidence that wins a 12.4 dispute

1. The authorization record showing the issuer approved the transaction for the account number that was charged.
2. Clearing data matching the authorization: the same account number, amount and date.
3. Order records linking the cardholder to the purchase: name, billing address, email and the order ID.
4. For stored cards, the customer’s consent to store the card and the history of earlier undisputed charges to that same card.

If the cardholder named on the dispute recognizes the merchant and has bought before, that is useful context, but the core question is whether the account number was correct.

How to prevent 12.4 chargebacks

• Authorize every transaction in real time. An approval validates the account number before you ship.
• Minimize manual card entry. Where you must key cards, read the number back to the customer.
• Validate stored-card migrations by test-charging or verifying a sample before switching over.
• Make sure your subscription platform can’t charge one customer’s stored card for another customer’s order.

Should you fight or accept?

Fight when you have an issuer approval for the account number that was charged and the order ties to the cardholder. That is usually conclusive.

Accept when the number was mis-keyed or a migration put the wrong card on the order. The cardholder has no connection to the purchase, and the correct step is to charge the right customer, with their authorization, separately.