Mastercard Reason Code 4870: Chip Liability Shift — Counterfeit Fraud
A counterfeit 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. Mastercard's lost-or-stolen chip-liability variant is the separate code 4871.
Your strongest argument
The EMV chip was read at a certified terminal — the chip liability shift condition is not met.
Evidence that wins a Mastercard 4870 dispute
- Proof the terminal was EMV-certified and the chip was read (not a magstripe fallback)
- Transaction record confirming chip-on-chip acceptance
- Authorization log showing EMV data was transmitted in the authorization request
Ordered strongest first — lead your rebuttal with the items at the top.
Not sure you have enough to win?
Run a free 60-second readiness check for Mastercard 4870. 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.
Check my evidence readiness — freeHow processors label this dispute
| Processor | What you'll see |
|---|---|
| Stripe | reason: fraudulent |
| Square | Chip 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 Mastercard 4870 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.
Build your evidence pack — $19Or run the free readiness check first.
Frequently asked questions
What is Mastercard reason code 4870?↓
How do I win a Mastercard 4870?↓
What triggers a chip liability shift on a Mastercard dispute?↓
Where to go next
Build the pack for Fraudulent / Unauthorized disputes, or dig into the matching guide, template, and processor evidence requirements.
Build the pack for this dispute
Guides for this dispute
Templates for this dispute
Updated June 2026. Reason-code meanings and evidence requirements are sourced from card network documentation and may change; always check your processor dashboard for the exact deadline and label on your dispute.