DiscoverFraudUpdated June 2026

Discover Reason Code UA05: Fraud — Chip Card Counterfeit Transaction

A counterfeit chip card was used in a card-present transaction that was not processed via the EMV chip — for example a magstripe fallback on a chip-capable card — shifting counterfeit-fraud liability to the merchant.

Respond within ~30 days
Highly winnable

Your strongest argument

The EMV chip was read at a certified terminal — the chip counterfeit-liability shift condition is not met.

Evidence that wins a Discover UA05 dispute

  • Proof the terminal was EMV chip-enabled and the chip was read (not a magstripe fallback)
  • Transaction record confirming chip-on-chip acceptance at a certified terminal
  • Authorization log showing EMV data was transmitted in the authorization request

Ordered strongest first — lead your rebuttal with the items at the top.

Source: Discover Network Dispute Rules and Reason Code documentation. The Discover rulebook defines this code and its dispute framework; the issuer decides every dispute and sets the exact deadline shown in your processor dashboard.

Not sure you have enough to win?

Run a free 60-second readiness check for Discover UA05. Answer a few yes/no questions and get a 0–100 score, a green/amber/red evidence checklist, and your exact response deadline — no signup.

How processors label this dispute

ProcessorWhat you'll see
Stripereason: fraudulent
SquareChip liability shift

Where to pull this evidence

Prove the genuine cardholder made and benefited from the purchase. Authentication data wins these. Here's exactly where the relevant records live in each processor dashboard — gather them free before you build your pack.

Stripe

Dashboard → Payments → Disputes (or the email alert from Stripe).

  • AVS & CVC check results: Open the original payment → Payment details → "Checks" (CVC, ZIP, address).
  • Customer email, IP, and device: Payment → Customer section and the "Risk insights" / Radar panel.
  • Receipt / order confirmation: Payment → "Send receipt" or your order-management system; export the PDF.
  • Refund history & reference IDs: Payment → Timeline shows any refunds with their re_… reference IDs.

Shopify Payments

Shopify admin → Orders → the flagged order → "Chargeback" banner, or Settings → Payments → Manage disputes.

  • Order & fulfillment details: Orders → the order → Fulfillment + Timeline (shows when items shipped).
  • Tracking number & carrier: Orders → Fulfillment → tracking; confirm "Delivered" status with the carrier.
  • Customer info & IP: Order → Customer section; Order → Additional details / fraud analysis for IP and AVS/CVV.
  • Fraud analysis (AVS/CVV/risk): Order → "Fraud analysis" panel shows AVS, CVV, and Shopify’s risk indicators.

Square

Square Dashboard → Disputes (or Balance → Disputes), or the email from Square.

  • Transaction & receipt: Transactions → the payment → receipt; "Resend receipt" for a copy.
  • Card-present / chip details: Transaction detail shows entry method (chip, tap, keyed) — chip reads support card-present disputes.
  • Customer details: Customer Directory → the customer; or the transaction’s customer section.
  • Itemization & amount: Transaction → itemized breakdown to rebut "incorrect amount" claims.

PayPal

PayPal → Resolution Center → the open case (Dispute, Claim, or Chargeback).

  • Transaction details & ID: Activity → the transaction → details; note the Transaction ID.
  • Proof of delivery / tracking: Resolution Center → "Respond" → add tracking number + carrier (PayPal validates delivery).
  • Proof of shipment / service: Resolution Center evidence upload: invoice, shipment receipt, or service-completion proof.
  • Buyer communication: Resolution Center message thread + your own email records with the buyer.

Build a submission-ready Discover UA05 response

ChargebackKit assembles your evidence into a formatted, labeled rebuttal pack with the exhibits and response letter card networks expect — pre-mapped to Fraudulent / Unauthorized disputes.

Verified against the official Discover Network Dispute Rules and Reason Code documentation3-day money-back guarantee if your pack isn’t structured correctly for your dispute

Or run the free readiness check first →

Frequently asked questions

What is Discover reason code UA05?
Discover UA05 ("Fraud — Chip Card Counterfeit Transaction") is filed when a counterfeit chip card is used in a card-present transaction that was not processed via the EMV chip — for example when the terminal fell back to magstripe on a chip-capable card. Because EMV chip processing prevents counterfeit cards, bypassing it shifts liability to the merchant. It is the Discover equivalent of Visa 10.1 and Mastercard 4870.
How do I win a Discover UA05 chargeback?
Provide records showing the terminal was EMV-certified and the chip was actually read during the transaction. A magstripe swipe on a chip-capable card without a valid fallback procedure is difficult to contest.
How is UA05 different from UA06?
UA05 covers counterfeit chip-card fraud; UA06 covers lost, stolen, or never-received chip-card fraud. Both require proof that the EMV chip was properly read at a certified terminal, but UA06 additionally requires PIN verification records.

Where to go next

Build the pack for Fraudulent / Unauthorized disputes, or dig into the matching guide, template, and processor evidence requirements.

Updated June 2026. This code’s meaning and evidence requirements are sourced from the Discover Network Dispute Rules and Reason Code documentation and may change as Discover revises its rules; always check your processor dashboard for the exact deadline and label on your dispute. The issuer decides every dispute — there is no guaranteed outcome.