What Visa reason code 12.4 means
The account number in the clearing record has to match an account at the issuer and the card that was authorized. When a digit is wrong, the charge can land on the wrong cardholder or on no valid account at all. This happens far more often with manually keyed transactions and older terminals than with tokenized online checkouts, where the card number comes straight from the payment form or the card network token.
Typical triggers for a 12.4 chargeback
-
A card number was keyed by hand at a phone order desk or virtual terminal and a digit was wrong.
-
An offline or stand in transaction was processed without real time authorization.
-
A clearing record was edited or rebuilt after an outage and the account number changed.
-
A stored card on file was reused after the issuer replaced the card number.
Time limits for Visa 12.4
For processing error codes the issuer typically has 90 days from the processing date to raise the dispute. Your response window is set by your processor and is often between 7 and 21 days. In Stripe the deadline appears as the evidence due date on the dispute. A missed deadline means the dispute is lost.
Evidence that wins a 12.4 dispute
-
The authorization record showing approval for the same account number that was cleared.
-
The clearing record with the matching masked card number, last four digits and card fingerprint.
-
Proof the card was entered by the cardholder at checkout, such as a tokenized payment method.
-
AVS and CVV results that confirm the details matched the issuer's records.
-
Order and customer records that tie the cardholder to the purchase.
What to avoid when you respond
-
Do not send full card numbers. Masked numbers and last four digits are enough.
-
Do not argue about the product or delivery. The dispute is about which account was charged.
-
Do not refund after the dispute is opened, because the funds are already withdrawn.
-
Do not miss the deadline while you request records from a terminal provider.
How to prevent Visa 12.4 chargebacks
-
Let customers enter their own card details in a hosted payment form instead of keying numbers by hand.
-
Require real time authorization and avoid offline transactions where possible.
-
Use network tokens and account updater services so stored cards stay current.
-
Ask for CVV and run AVS on every card not present order.
How 12.4 appears in Stripe
Card numbers on Stripe come from the payment form or a network token, so 12.4 disputes are uncommon there. When one appears, Stripe usually shows it under the reason general rather than incorrect account details, which is mostly used for bank account payments. The raw code is always in the network reason code field of the dispute (payment_method_details.card.network_reason_code). NoChargeback reads that field and attaches the card fingerprint, last four digits and authorization data from the charge. See Stripe chargeback protection.
Rebuttal letter opening for Visa 12.4
We are responding to the dispute filed under Visa reason code 12.4. The transaction was authorized and cleared on the same account number, entered by the cardholder at checkout. The authorization approval, AVS and CVV results, and the matching masked card number in the clearing record are attached below.
Can a merchant win a Visa 12.4 chargeback?
Yes. When the authorization and clearing records show the same valid account number and the card details matched, the issuer has no basis for the dispute.
Why would a 12.4 dispute reach an online store?
It is uncommon, but it happens with manually keyed phone orders, virtual terminals and stored cards that were replaced. A tokenized checkout makes it rare.
Should I include the full card number as proof?
No. Send the masked number, last four digits and the authorization record. Full card numbers must never appear in dispute evidence.