What Discover Reason Code UA30 Means
Discover reason code UA30, titled Fraud — Counterfeit, Magnetic Stripe, is filed when a counterfeit Discover card — a cloned magnetic stripe — was used at a merchant's point-of-sale terminal. This is the classic card skimming and cloning fraud scenario.
Under Discover's EMV liability shift, if a counterfeit stripe card is used at a merchant terminal that could have required an EMV chip read but instead processed via magnetic stripe, the merchant bears full fraud liability. If the terminal properly attempted and captured EMV chip data, liability shifts to the issuer.
UA30 is the direct consequence of not requiring EMV chip reads. Counterfeit magnetic stripe fraud is nearly eliminated for merchants who properly process chip cards via EMV. If your terminal swiped a chip-capable Discover card, you own the liability. If your terminal dipped the chip, liability shifts to the issuer. The distinction is entirely within the merchant's control.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Discover | UA30 | Fraud – Counterfeit, Magnetic Stripe | This page |
| Visa | 10.1 | EMV Liability Shift Counterfeit Fraud | Visa counterfeit stripe code |
| Mastercard | 4870 | Chip Liability Shift | Mastercard counterfeit code |
| Amex | F10 | Missing Imprint | Amex card-present fraud code |
Common Trigger Scenarios
- Stripe-only terminal used with chip-capable card. A counterfeit stripe cloned from a chip-capable Discover card was used at your terminal. Because you didn't require a chip read, Discover's liability shift applies and you bear full liability.
- Chip card swiped instead of dipped. The cardholder's chip card was swiped (possibly because the chip reader was disabled or the cashier bypassed it), allowing a counterfeit card with only a cloned stripe to succeed.
- Fallback stripe transaction on chip-capable card. A chip read 'failed' and the transaction fell back to magnetic stripe. If the chip failure was not genuine, this may represent a counterfeit card attempting to bypass chip verification.
- Skimmer-compromised terminal processing cloned cards. A skimming device on your terminal captured magnetic stripe data from legitimate cards, which was then used to create counterfeit cards used at other locations.
Key Deadlines & Timeframes
| Milestone | Timeframe | Notes |
|---|---|---|
| Cardholder Filing Window | 120 days | From the transaction date |
| Merchant Response Window | 30 days | From Discover dispute notification; confirm with your processor for internal deadlines |
| Pre-Arbitration | 30 days | If Discover rejects representment, 30 days to escalate |
Evidence You Will Need
- EMV chip transaction record — Proof that the chip was read for the disputed transaction, not the magnetic stripe. If you have this, the liability shifts away from you.
- Terminal receipt showing EMV mode — Receipt indicating 'Chip Read' or 'EMV' rather than 'Swipe' or 'Magnetic Stripe'
- Terminal configuration records — Documentation showing the terminal was configured to require chip reads and had chip-reading capability
- Fallback documentation — If fallback to stripe occurred: records of the chip read attempts, the reason for fallback, and the fallback procedure followed
- Terminal audit logs — Terminal transaction logs showing the processing mode for the disputed transaction
Learn Exactly How to Package and Present This Evidence
The Fraud Defense Guide covers the complete evidence format for UA30 representments, how to structure your response letter, and when a dispute is better accepted than contested given your authentication data.
Learn exactly how to package and present this evidence →How Merchants Lose This Dispute
- Operating stripe-only terminals. Any terminal that cannot read EMV chips has no counterfeit stripe defense. Every transaction at a non-EMV terminal on a chip-capable card creates full merchant liability.
- Allowing cashiers to swipe chip cards. Cashiers who swipe chip cards 'because it's faster' create avoidable counterfeit fraud liability on every such transaction.
- No fallback documentation. When genuine chip failures occur and stripe fallback is necessary, the fallback must be documented. Undocumented fallbacks look identical to unauthorized swipes.
- Disabled chip readers. Some merchants disable chip readers due to speed complaints. This creates full counterfeit liability on all chip-capable Discover cards processed at that terminal.
Get the Step-by-Step Winning Strategy
Our Fraud Defense Guide covers the complete UA30 representment structure and the cross-network approach for equivalent fraud codes across Visa, Mastercard, and Amex.
Get the step-by-step winning strategy →Response Framework Overview
- Present EMV chip transaction record. If the chip was read, present the electronic transaction record showing chip mode. This establishes the liability shift immediately.
- Show terminal receipt mode. The receipt should indicate 'Chip Read' not 'Swipe.' Present this as corroborating evidence.
- Document fallback if applicable. If a genuine chip failure required stripe fallback, document the failed chip attempts, the error codes, and the fallback procedure followed.
- Present terminal EMV capability records. Show terminal certification and configuration records proving the terminal was chip-capable.
Prevention Tips
- Ensure all terminals are EMV chip-capable. Replace any stripe-only terminals. EMV compliance is the only effective counterfeit stripe fraud prevention.
- Require chip reads — never allow cashier stripe bypass. Configure terminals to require chip reads and train staff never to swipe chip-capable cards. Stripe bypass creates full counterfeit liability.
- Inspect terminals for skimming devices regularly. Regular physical inspection of terminals for skimming devices prevents both stripe data capture and the counterfeit cards that result from it.
- Document all fallback transactions. When a genuine chip failure requires stripe fallback, document it in real-time. This documentation is the only available defense for a fallback transaction.
Frequently Asked Questions
Why is counterfeit stripe fraud a merchant problem?
Under Discover's EMV liability shift, merchants who do not require chip reads accept full liability for counterfeit stripe transactions. The network policy is: if you could have required a chip read but didn't, you own the fraud. This policy incentivizes universal EMV adoption.
What happens if the chip legitimately failed?
Genuine chip failures allow stripe fallback under specific documented procedures. The fallback must be documented (chip attempt records, error codes, fallback notation). Undocumented fallbacks are treated as unauthorized stripe swipes and carry full merchant liability.
Can UA30 chargebacks be won without EMV data?
Winning UA30 without evidence that the chip was read is extremely difficult. The merchant needs to show either that the chip was processed (liability shift) or that extraordinary circumstances justified stripe processing. Without either, the win rate is very low.