Discover reason code AA
Discover AA: Does Not Recognize
What the cardholder is claiming
The cardholder sees your charge on their statement and cannot connect it to anything they bought. They are not necessarily alleging fraud yet; they just do not recognize the transaction.
The evidence that actually wins
Bank analysts skim responses in minutes against a checklist for this exact code. Lead with the strongest fact; never make them dig.
- ✓Order details matching the cardholder: name, email, billing address, and phone on the order versus the card account
- ✓What was bought, when, and proof of delivery (tracking with confirmation, or access and usage logs for digital goods)
- ✓Prior undisputed purchases from the same customer or account, showing an established relationship
- ✓The billing descriptor as it appeared on the statement, with anything that maps it to your storefront name
- ✓AVS and CVV match results plus IP or device data tying the order to the cardholder
The honest read
One of the more genuinely workable codes, because the cardholder is usually confused rather than adversarial. A clear response showing who bought what, when, and where it went often resolves the recognition problem itself. The common trap is a billing descriptor that does not match the name the customer bought from; if that is the root cause, fix the descriptor or this code keeps arriving. Answer thoroughly the first time, because an unresolved AA can come back as a straight fraud claim under UA02.
Nobody can promise you a win; the cardholder's bank decides. What you control is submitting the strongest complete case your records support, on time. Our plain-language guarantees say exactly what that means.
Fighting a AA right now?
Send us the dispute and a person builds the complete, submission-ready response: the narrative mapped to AA, your evidence compiled and ordered, and the field-by-field walkthrough. 24-hour rush available. If our review says yours isn't worth fighting, we tell you for free.