Mastercard 4870 — Chip Liability Shift
Mastercard 4870: the cardholder says a counterfeit card was used in person
By Byron Kiriibwa · Updated
Checked by three automated reviewers (facts against the playbook, search, and our rules), then approved by the author on .
Mastercard 4870 means the cardholder says they didn't make an in-person purchase and a counterfeit copy of their card was used. It's decided by how the card was read: liability moves to you when the terminal didn't read the chip. If it was swiped or keyed, or no one can supply a record of the read, accept it.
What decides a Mastercard 4870
- The entry mode on the card reader's record
- The bank's first check is whether the card was read by its chip at a chip-reading terminal, not swiped or keyed. That shows as the entry mode in your card-reader provider's transaction record for the payment. A receipt with only the amount and the card ending doesn't show it, and neither does saying the customer was standing in front of you.
- The chip's data in the approval request
- The second check is whether the approval request carried the chip's data. Send the authorization from the card reader's record together with the entry mode, so the bank sees the chip read and the approval it went with as one sale, for the same amount and date as the disputed charge.
- Online fraud evidence doesn't apply
- 3D Secure, address checks and delivery proof answer online fraud. A 4870 is about a card-present sale made with a copied card, so a response built on them leaves both of the bank's chip questions unanswered, however strong it looks. So does a note that the card checks passed, without the card reader's record behind it.
- A chip read that failed
- When the chip read fails and the sale is finished by swiping or keying the card, the chip wasn't read, and the advice is to accept. The same goes for a terminal that can't read chips at all. Asking for another card at the time, rather than falling back, is what keeps the sale on the chip.
- Where the code applies
- A 4870 is for a sale made in person. For shipped goods it doesn't apply, and for digital products and subscriptions only when the card was taken in person. For a service, the record that answers it comes from the card reader used at the job or session.
The bank's test
The bank checks:
- Was the card read by its chip at a chip-reading terminal, not swiped or keyed?
- Did the approval request carry the chip's data?
- Has the payment already been refunded, or does the cardholder no longer dispute it?
Evidence that answers it
“Where it goes” uses the names Stripe's and Square's APIs give each piece of evidence, which are the names Upheld uses in your packet. Nothing is sent without your approval; where Upheld can't send it for you, you submit it yourself. In Stripe's Dashboard, choose the matching type for each file or text field. In Square's, add it when Square asks you to “upload any additional evidence specific to your service type”.
| Evidence | When it counts | How to show it | Where it goes | For |
|---|---|---|---|---|
| Card reader or processor record (chip, PIN, imprint) | Showing the chip read (entry mode) and the authorization. | The terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified. | Stripe: Uncategorized fileSquare: Authorization documentation | Every seller |
| Receipt or invoice | Showing the sale: what was bought and the amount. | The receipt or invoice sent to the customer. | Stripe: ReceiptSquare: Receipt | Every seller |
| Refund or credit already issued | If the payment was already refunded. | Refund date, amount, and reference. | Stripe: Uncategorized fileSquare: Generic evidence | Every seller |
| Messages with the customer | If the cardholder has withdrawn the dispute. | The relevant messages only, dated, with the key lines highlighted or quoted in the response. | Stripe: Customer communicationSquare: Cardholder communication | Every seller |
What doesn't help
- 3D Secure, address checks, or delivery proof. They answer online fraud, not a card-present sale.
- A receipt that shows only the amount and card ending, with no entry mode or verification result.
Mastercard's rules for 4870
- 4870 covers an in-person sale made with a counterfeit copy of a chip card when the sale wasn't completed by reading the chip: liability moves to the seller when the terminal didn't read the chip. Source: Mastercard, Chargeback Guide – Merchant Edition (13 May 2025), Chip Liability Shift; read 2026-10-27.
- The same EMV liability shift as Visa 10.1 (counterfeit cards): the seller carries the loss when the sale wasn't done the secure way, and not when it was. Visa 10.2 and Mastercard 4871 cover lost or stolen cards.
Common mistakes with Mastercard 4870
- Sending a receipt that doesn't show the entry mode.
- Arguing the sale was in person or that the card checks passed, without the card reader's record.
Should you fight it?
Fight it when your card-reader provider's record shows the chip was read at a chip-reading terminal and the approval request carried the chip's data. A receipt with only the amount and the card ending doesn't show either, and neither does saying the sale was in person. Accept it when any of these is true:
- The card was swiped or keyed, or the terminal can't read chips.
- There is no record of how the card was read, and the card-reader provider can't supply one.
If you accept, don't refund as well: once it's a chargeback the money has already gone back to the customer, so a refund would pay them twice.
A dispute counts against your account whether you win or lose. To see the chance of winning at which fighting pays on your amount, try the fight-or-accept calculator; to compare what you keep with each tool, the fee calculator.
How to prevent the next one
- Use a card reader that reads chips and takes PINs, and let it prompt for the PIN.
- Don't fall back to swiping or keying when a chip read fails; ask for another card.
- Keep the card-reader provider's transaction records.
Deadlines and fees
| Platform | Deadline | Fees |
|---|---|---|
| Stripe (US)Checked 2026-10-21 | Respond by the due date on the dispute in your Stripe Dashboard. It's usually 7 to 21 days, depending on the card network. | $15 when the dispute arrives, which isn't returned. $15 more when you respond, returned only if you win in full.Stripe's Smart Disputes waives the $15 response fee and takes 30% of the disputed amount when you win. |
| SquareChecked 2026-10-21 | Seven days from Square's first email about the dispute. | No fees for dispute management on chargebacks: Square covers the fee for disputes you challenge together. |
| Shopify Payments (US)Checked 2026-10-21 | Respond by the evidence due date in your Shopify admin. It's usually 7 to 21 days. | $15 per chargeback, returned if you win. |
A worked example (made up)
You run a mobile appliance repair service. Customers book online, and you take payment on a card reader at the end of each job. On May 9 you replace a dishwasher pump at a customer's home for $265; the customer inserts their Mastercard and the reader reads the chip. In June the cardholder files a 4870 dispute saying a counterfeit copy of their card was used for the payment.
The response would attach:
- Exhibit A: the card-reader provider's transaction record for May 9: entry mode chip, on a reader that reads chips.
- Exhibit B: the same record's authorization: the $265.00 approval request sent with the chip's data.
- Exhibit C: the receipt the reader produced for the $265.00 repair.
A sample response letter (made up)
For the example above. It's laid out the way Upheld drafts a response: one part for each thing the bank checks, strongest evidence first, each pointing to its exhibit. Yours should state only what your own records show.
We contest this dispute, Mastercard reason code 4870, for $265.00 charged on May 9 for a dishwasher repair at the customer's home. The card's chip was read at a chip-reading terminal, and its data went with the approval request.
The card was read by its chip, not swiped or keyed. Our card-reader provider's record for this payment shows the entry mode as chip, on a reader that reads chips (Exhibit A).
The approval request carried the chip's data. The same record shows the $265.00 authorization sent with the chip's data (Exhibit B).
The receipt from the reader matches the sale: $265.00 on May 9 (Exhibit C). The chip was read and its data went with the approval. We ask that the dispute be decided in our favor.
Questions people ask
What is a Mastercard 4870 chargeback?
Mastercard's chip liability shift code for counterfeit cards: the cardholder says they didn't make an in-person purchase and that a counterfeit copy of their chip card was used. Liability moves to the seller when the terminal didn't read the chip.
Our receipt shows the card's last four digits. Is that enough for a 4870?
No. A receipt that shows only the amount and the card ending, with no entry mode or verification result, doesn't show the chip was read. Send the card reader's record with the entry mode.
The chip wouldn't read, so we swiped the card. Can we fight a 4870?
No: when the card was swiped or keyed, accept the dispute. Next time, don't fall back to swiping or keying when a chip read fails; ask for another card.
Where do we get the entry mode for a 4870 response?
From your card-reader provider's transaction record for the payment. Keep those records; if the provider can't supply one and you have no other record of how the card was read, accept the dispute.
Is Mastercard 4870 the same as Visa 10.1?
Yes, in effect: both are the EMV liability shift for a counterfeit copy of a chip card. The seller carries the loss when the sale wasn't done the secure way, and not when it was. Visa 10.2 is the one for lost or stolen cards, like Mastercard 4871.
Draft yours free
Answer a few questions and get a draft, an evidence checklist and an honest read on whether to fight. Free account, no card.
Not sure what your notice says? Decode it first.