Visa 12.4 - Incorrect Account Number
- The wrong Payment Credential was used. Not the wrong amount, the wrong account. An Original Credit can carry this code too
- Look for a keyed digit, a saved card linked to the wrong number, or a card they didn't pick
- Can you prove the correct credential with a receipt or other record? A mismatch doesn't end it: check invalidity and any overlooked credit first. See Representment Options
- For an ordinary purchase or Original Credit, the customer's bank must file within 120 calendar days from the date the payment was processed. Visa's standard limit for the response from your acquirer (the bank behind your processor) is 30 calendar days; work to the date on your notice, which your processor can set earlier
Got this code?
Your deadline: The date on your notice wins. Your processor can set it earlier than Visa's standard limit for your acquirer's response (30 calendar days), and some domestic markets are shorter.
The claim: An incorrect Payment Credential was used, on a purchase or an Original Credit. The bank certifies that, or that the credential doesn't match its master file and no authorization was obtained.
Records that answer it:
- The authorization record with the account charged
- A receipt or other record proving the correct credential. Matching last four alone isn't proof; for an updated or tokenized credential, get the processor or network linkage
- The order showing the customer picked this payment method
If you can't support it: Check the invalid-dispute conditions (a valid chip cryptogram is one) and any overlooked credit or reversal before you pay it.
Next: Decide whether it's worth fighting, then build the response with the Representment Workflow.
When This Code Applies
- Transaction posted to the wrong card
- Wrong number keyed by hand
- System error posting to the wrong account
- Digits transposed
- Tokenization mapped to the wrong card
Conditions for Valid Dispute
The issuer certifies one of two things: an incorrect Payment Credential was used, or the credential doesn't match its master file and no authorization was obtained. This code is an exception to Visa's general rule that the cardholder must have taken a financial loss. Some sales are excluded, such as a chip sale with a valid cryptogram, and a credential with no card issued or outstanding when an imprint or authorization was obtained.
Common Scenarios
| Scenario | Cause |
|---|---|
| Multi-card customer | Charged wrong saved card |
| Manual keyed entry | Digit transposition |
| Token confusion | Wrong token used |
| Copy/paste error | Wrong credentials copied |
Time Frames
| Scenario | Dispute Window |
|---|---|
| Bank files, ordinary purchase or Original Credit | 120 calendar days from the date the payment was processed |
NETWORK For ordinary purchases and Original Credits, the issuer has 120 calendar days from the Transaction Processing Date to file 12.4. An ATM Deposit Adjustment runs from its own processing date. For US domestic ATM cash and PIN-authenticated debit adjustments, the alternative runs from the date of the adjustment itself (Visa rules, 24 October 2026, section 11.10.3.3, Table 11-69, printed page 738); source links accessed 28 October 2026.
Representment Options
The answers are an overlooked credit or reversal, an invalid dispute, a withdrawn dispute, or proof of the correct credential.
1. The Right Account Was Charged
Evidence required:
- Transaction records matching the card
- Processor or network linkage for an updated or tokenized credential. Matching last four alone isn't the match
- Authorization record with the correct account
- Customer confirmation
2. The Customer Picked This Card
Evidence required:
- Order showing this payment method
- Record of the customer selecting it
- Account profile records
- IP and device at time of selection
3. Logs That Prove a Ground
Evidence required:
- Processor records that prove the correct credential, an overlooked credit or reversal, or an invalid dispute
- System logs showing a correct submission
- Blaming a downstream system explains the cause. Chasing your processor for the money is a separate matter, not a 12.4 answer
Which defenses hold up
| Defense Type | Where that leaves you |
|---|---|
| Correct account proven | That's the answer, with a receipt or other record proving the correct credential |
| Customer selected this card | Supporting records behind the credential proof |
| Wrong account charged | Still check invalidity and any overlooked credit |
Track your own win rate by reason code.
Where This Breaks
Start with checkout. A customer with four saved cards sees four near-identical rows, and can't tell which one they're picking. Print the last four digits and the brand.
Silent defaults are worse. You auto-select a card, nobody notices, and the charge hits an account they'd stopped using. Make the customer pick.
Then check anything keyed by hand. Read the number back before you submit it; a read-back catches a transposed digit before the sale goes through.
One rule covers the rest. Authorize and capture against the same account. If those two disagree, work through the answers above, then fix whatever caused the mismatch.
Related Codes
See Also
- Reference - The whole reference section
- Time Frames - Dispute and response deadlines
- Is it worth fighting? - Weigh what responding costs against accepting this chargeback
- Checkout Conversion
- Tokenization
- Card on File