Discover · Fraud
Reason code AA: Does Not Recognize
The cardholder looked at their Discover statement and could not identify the transaction. Unlike a hard fraud claim, the cardholder is not necessarily alleging theft; they simply do not recognize the merchant name, amount, or date. Discover files this as a dispute so the merchant can supply details that either jog the cardholder's memory or confirm the charge is legitimate.
Issuer filing window
typically 120 days from the processing date
Merchant response window
typically 30 days to respond
Why AA chargebacks happen
- Your billing descriptor shows a legal entity name or acronym that does not match the brand name the customer bought from.
- The charge settled days after the purchase, so the posting date on the statement does not line up with when the customer remembers buying.
- A family member or employee used the card and never told the primary cardholder.
- A trial converted to a paid charge under a descriptor the customer never associated with the free signup.
- The transaction was genuine fraud and the cardholder truthfully has no knowledge of it.
How to fight a AA chargeback
- Respond to any Discover ticket retrieval request immediately with a legible sales record; a complete retrieval response often resolves an AA before it hardens into a chargeback.
- Send the order confirmation, invoice, and itemized receipt showing the product, amount, and date so Discover can share recognizable details with the cardholder.
- Include the AVS and CVV match results plus the IP address and device data tying the order to the cardholder.
- Provide delivery confirmation to the cardholder's verified billing address, or access logs for digital goods.
- Attach any email or support correspondence with the customer that references the purchase.
How to prevent AA chargebacks
- Set your Discover billing descriptor to the customer-facing brand name and include a phone number or URL in the descriptor field.
- Send a branded receipt email at the moment of purchase that repeats the exact descriptor the customer will see on their statement.
- Batch and settle daily so the posting date stays close to the purchase date.
- State clearly on the checkout page how the charge will appear on the statement.
- Enroll in Verifi Order Insight or Ethoca so transaction details surface inside the issuer's app before a dispute is filed.
Frequently asked questions
- Is Discover reason code AA the same as a fraud chargeback?
- Not exactly. AA sits in Discover's fraud family but it means the cardholder does not recognize the charge, not that they are formally alleging fraud. Supplying clear transaction details often resolves it without a full representment fight, which is why the ticket retrieval stage matters so much.
- Can I win an AA dispute if the customer really made the purchase?
- Yes, and the win rate is better than for hard fraud codes. Evidence that connects the cardholder to the order, such as AVS match, delivery to the billing address, prior undisputed purchases, and login history, frequently gets AA disputes reversed or withdrawn.
- Why did I get an AA instead of UA02?
- Discover uses AA when the cardholder says they do not recognize the transaction and UA02 when they affirmatively claim a card-not-present charge was unauthorized. The evidence you submit is similar, but AA cases are more likely to be honest confusion that a good receipt trail can clear up.
Related Discover codes