Discover Chargeback Code UA22: Fraud — No Cardmember Authorization

What Discover Reason Code UA22 Means

Discover reason code UA22, Fraud — No Cardmember Authorization, is filed when a cardholder claims a transaction was processed without their knowledge or consent. This is Discover’s general unauthorized transaction fraud code, applying when the cardholder denies authorizing the charge regardless of the transaction method.

Unlike more specific fraud codes tied to transaction type (chip, CNP, digital goods), UA22 is a broader claim. The defense requires direct evidence that the cardholder authorized the specific transaction — a signed receipt, EMV chip record, authorization phone recording, or account-based evidence showing the cardholder initiated the purchase.

Cross-Network Equivalent Codes

Common Trigger Scenarios

• Stolen card used in-person or online. A fraudster uses a stolen card for any type of transaction, and the cardholder files UA22 as a general unauthorized charge claim.
• Friendly fraud on legitimate purchases. A cardholder claims no authorization on a purchase they actually made, particularly for high-value items or recurring charges.
• Family member or household fraud. Someone in the cardholder household uses the card without explicit permission, and the cardholder disputes the charge as unauthorized.
• Subscription not recognized. A cardholder disputes a recurring charge they originally authorized but no longer recognize, claiming no authorization.
• Account takeover. A fraudster accesses the cardholder account and makes purchases; the cardholder files UA22 for all unauthorized transactions regardless of channel.

Key Deadlines & Timeframes

Evidence You Will Need

• Signed sales receipt or order form — cardholder signature directly authorizing the specific transaction
• EMV chip transaction data — for card-present transactions, ARQC/TC proving chip authentication occurred
• Authorization match confirmation — proof the transaction was authorized with a valid auth code from the issuer
• Cardholder account activity — login records, account history, or email confirmations showing the cardholder initiated the transaction
• Prior transaction history — evidence the cardholder has made similar transactions with the same merchant before without dispute

How Merchants Lose This Dispute

• No signed authorization or receipt. Without a signed document from the cardholder, the representment has no direct authorization evidence to present.
• No authorization code in transaction record. A transaction processed without a valid Discover authorization code cannot be defended against a no-authorization claim.
• Delivery to a non-billing address. Shipping to an address other than the cardholder billing address significantly weakens the merchant position on any fraud claim.
• No account history linking cardholder to purchase. For digital or account-based purchases, no evidence that the cardholder personally initiated the transaction is a critical gap.

Response Framework Overview

1. Locate direct authorization evidence — a signed receipt or order form is the strongest single piece of evidence for UA22.
2. Pull the authorization record — confirm a valid Discover auth code was obtained and include it in the representment.
3. Document delivery or service fulfillment — carrier tracking to the billing address or service delivery confirmation.
4. Include account history — for account-based purchases, login records and prior transaction history showing the cardholder used this account.

Prevention Tips

• Always obtain a valid authorization code before settling. A transaction without a valid auth code cannot be defended against a UA22 claim.
• Capture cardholder signatures for card-present transactions. A signed receipt is direct authorization evidence and the strongest defense for UA22.
• Implement account authentication for online purchases. Login records and 2FA confirmation provide authorization evidence when no physical signature exists.
• Maintain transaction records for at least 18 months. Older transactions are harder to win without documentation, and records may be needed for pre-arbitration.

Frequently Asked Questions

How is UA22 different from more specific Discover fraud codes?

UA22 is a general no-authorization claim without specifying the transaction type. More specific codes like UA18 (chip-and-PIN) or UA06 (CNP) are filed when the transaction channel is known. The defense evidence for UA22 depends on how the original transaction was processed.

Can prior transaction history help win a UA22 dispute?

Yes — evidence that the cardholder has previously transacted with the merchant using the same card, without dispute, is useful corroborating evidence. It does not replace direct authorization evidence but supports a friendly fraud argument.

How long does a cardholder have to file a UA22 dispute?

120 days from the transaction date. The merchant response window is 30 days from Discover’s notification.

Related Codes & Resources