What Visa Reason Code 12.4 Means
Visa reason code 12.4 falls under the Processing Errors category and is titled Incorrect Account Number. It is filed when the account number in the settlement record does not match a valid authorized account number for the transaction. The issuer receives a settlement debit for an account number that either does not exist in their system, belongs to a different cardholder, or was not the account number used in the authorization.
This chargeback can arise from simple data entry errors, tokenization system failures, card-on-file account number mismatches, or problems during card reissuance where a new account number was not properly updated in the merchant's system.
Code 12.4 is about the account number field in the transaction record, not the transaction amount or currency. If the correct account number is charged but the wrong amount is billed, that is 12.5 (Incorrect Amount). If the cardholder asserts they never authorized the charge at all, that is a fraud dispute under the 10-series codes, not a processing error under 12.4.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Visa | 12.4 | Incorrect Account Number | This page |
| Mastercard | 4834 | Point of Interaction Error | MC's processing error catch-all; covers account number errors |
Common Trigger Scenarios
- Manual key-entry digit errors. When a card number is typed manually (due to a damaged card or terminal failure), a single transposed digit results in a transaction against a non-matching account number.
- Tokenization system errors. Payment systems that store and retrieve tokens (representing card numbers) can retrieve the wrong token for a cardholder's account — particularly after system migrations or when a cardholder has multiple cards on file.
- Card reissuance without account update. When a cardholder receives a new card with a new account number and the merchant's system still charges the old number, the settlement hits a closed or reassigned account.
- Batch file mapping errors. During bulk transaction processing, if account number fields are shifted or misaligned in a batch file, transactions can be applied to entirely different accounts than intended.
- Multi-card household confusion. In environments where multiple cards are stored for a single customer, the wrong card may be charged if the system does not correctly identify the intended card.
Key Deadlines & Timeframes
| Milestone | Timeframe | Notes |
|---|---|---|
| Cardholder Filing Window | 120 days | From the transaction date |
| Merchant Response Window | 30 days | From acquirer receipt of chargeback; processor deadline may be shorter |
| Pre-Arbitration | 30 days | After representment rejection, if escalation is warranted |
Evidence You Will Need
- Authorization approval record showing the account number that was authorized — this is the critical comparison point against the settled account number
- Settlement record showing the account number submitted in the settlement batch
- Signed transaction receipt showing the card number (last four digits) and cardholder signature
- Tokenization or card-on-file system log showing which token/account number was retrieved for the transaction and confirming it was the correct one on file for the cardholder
- Account Updater service records confirming the account number on file was updated prior to the disputed transaction (if card reissuance is the claimed cause)
- Cardholder consent documentation showing authorization to charge the specific account on file
How Merchants Lose This Dispute
- Settlement account number genuinely differs from authorization. If your records confirm the settled account number does not match the authorized account number, the chargeback is correct. Accept it and fix the data pipeline.
- Unable to produce the authorization record. Without the authorization showing the account number that was approved, you cannot demonstrate the settlement matched the authorization.
- Card-on-file number was outdated. If the cardholder's card was reissued and you did not update the account number, this is a merchant-side failure with no representment path.
- Assuming the cardholder "knows" they have this card on file. If a cardholder has multiple cards and did not intend to use the one you charged, awareness is not consent. The wrong account number is still the wrong account number.
Response Framework Overview
- Compare authorization and settlement account numbers. Pull both records and confirm whether they match exactly. This single check determines whether you have a defense.
- If they match: Provide the authorization and settlement records showing identical account numbers and challenge the chargeback as filed in error by the issuer.
- If they do not match: Determine the root cause (key-entry error, tokenization failure, reissuance gap) and document whether the cardholder authorized the correct account.
- Provide cardholder authorization documentation. If the cardholder specifically authorized the account that was charged, include the authorization agreement or signed receipt.
Prevention Tips
- Enroll in Visa Account Updater. This service automatically pushes new account numbers to merchants when issuers reissue cards. It eliminates the most common cause of 12.4 chargebacks for subscription and card-on-file merchants.
- Validate PAN format before processing. Implement Luhn algorithm validation on any manually entered card numbers. This catches transposition errors before they become chargebacks.
- Audit tokenization mapping quarterly. Confirm that your token-to-PAN mapping is accurate and that no stale tokens are associated with active cardholder records.
- Test batch file account number fields after any data migration. A single field shift in a batch import file can misdirect thousands of transactions. Validate a sample of records before full processing.
Frequently Asked Questions
How does a transaction end up on the wrong account number?
The most common causes are manual key-entry errors where the card number is typed incorrectly, tokenization or card-on-file system errors where the wrong stored account number is retrieved for a recurring charge, account number updates during card reissuance where the system uses an old number, and batch file import errors where account numbers are mapped to the wrong transaction records.
Can I win a 12.4 dispute if I charged the right customer but the wrong card?
Yes — if you can prove the cardholder (or someone authorized by them) presented the card that was charged, and the correct authorization was obtained. The dispute is about the account number in the settlement record not matching the authorized account. If you have an authorization approval for the account that was settled against, the dispute may be overturned despite the number discrepancy.
What is the time limit for a Visa 12.4 chargeback?
The cardholder has 120 days from the transaction date to file a Visa 12.4 dispute. Your acquirer will notify you and you typically have 30 days to respond, though your processor may impose a shorter internal deadline. Check your processor agreement for their specific requirements.
Does card reissuance cause 12.4 chargebacks?
It can. When a cardholder receives a new card with a new account number, merchants storing the old number for recurring billing need to update it. Visa's Account Updater service is designed to automatically update stored card numbers when accounts are reissued, but merchants who do not participate in Account Updater or whose systems do not process the updates correctly will charge an account number that no longer exists or belongs to a different person.