Why would someone who never bought from me dispute a charge under 12.4?

Because your transaction settled against their account number, usually through a keying error, a corrupted batch, or a token mapping defect. From their perspective an unknown merchant billed them. Verify quickly whether the account matches a real order; if not, refund or accept the dispute and find the systemic cause before it repeats.

How is 12.4 different from a fraud chargeback?

A 10.4 fraud dispute claims the cardholder's own card was used without authorization to make a purchase. A 12.4 says the wrong account was billed entirely, with no valid authorization tied to that account. The distinction matters because 12.4 does not automatically generate fraud reporting, though affected cardholders sometimes file fraud claims instead, which is worse for your ratios.

What evidence wins a 12.4 representment?

Show that the authorization and settlement carry the same account number, the authorization was approved, and the account belongs to a customer with a real order. Gateway authorization logs plus the order record usually settle it. If your own records reveal a mismatch, the case is unwinnable and speed of correction is what protects you.

Visa · Processing Errors

Reason code 12.4: Incorrect Account Number

The transaction was processed against an account number that does not match a valid authorization, meaning the cleared account differs from the one that was authorized or the cardholder whose account was billed never transacted with the merchant. It is fundamentally a keying or data-integrity failure. The person disputing often has no relationship with your business at all.

Issuer filing window

120 days from the transaction processing date

Merchant response window

typically 20-30 days to respond, depending on the acquirer

Why 12.4 chargebacks happen

A manually keyed card number contained a transposition error that happened to hit a different valid account.
A stored credential update went wrong and billing ran against the wrong customer's tokenized card.
A batch file edit or repair introduced the wrong account number before settlement.
The transaction settled with an account number different from the one in the authorization message due to an integration defect.
Two customer profiles were merged incorrectly in your CRM, attaching one customer's card to another's orders.

How to fight a 12.4 chargeback

Match the settled account number against the authorization record; if they agree and the authorization was approved for that account, submit both records.
Provide the order and customer documentation tying the billed account to an actual purchase by that cardholder.
If your investigation confirms a keying error, issue the correcting credit immediately and document it in the response rather than contesting a losing case.
Trace tokenized billing paths to demonstrate the token used maps to the customer who placed the order.
Accept the dispute where the billed party truly never transacted with you; there is no evidence that overcomes billing a stranger.

How to prevent 12.4 chargebacks

Eliminate manual card number entry wherever possible, and validate keyed entries with AVS and CVV2 before capture.
Use gateway tokenization end to end so raw account numbers are never re-keyed or hand-edited in your systems.
Lock down batch file editing; settlement repairs should go through processor tooling with audit trails, not text editors.
Add integration tests asserting the settled PAN or token always equals the authorized one.
Guard CRM profile merges with confirmation steps whenever payment credentials are attached.

Frequently asked questions

Why would someone who never bought from me dispute a charge under 12.4?: Because your transaction settled against their account number, usually through a keying error, a corrupted batch, or a token mapping defect. From their perspective an unknown merchant billed them. Verify quickly whether the account matches a real order; if not, refund or accept the dispute and find the systemic cause before it repeats.
How is 12.4 different from a fraud chargeback?: A 10.4 fraud dispute claims the cardholder's own card was used without authorization to make a purchase. A 12.4 says the wrong account was billed entirely, with no valid authorization tied to that account. The distinction matters because 12.4 does not automatically generate fraud reporting, though affected cardholders sometimes file fraud claims instead, which is worse for your ratios.
What evidence wins a 12.4 representment?: Show that the authorization and settlement carry the same account number, the authorization was approved, and the account belongs to a customer with a real order. Gateway authorization logs plus the order record usually settle it. If your own records reveal a mismatch, the case is unwinnable and speed of correction is what protects you.

Related Visa codes