Analyze my chargebacks

Mastercard reason code 4870: what it means and how to respond

Mastercard 4870 covers counterfeit-card fraud when chip data is missing. Learn the requirements, defense evidence, and filing deadlines.

What Mastercard code 4870 means and when it applies

Mastercard code 4870, “Chip Liability Shift—Counterfeit Fraud,” is filed when the cardholder denies authorizing a card-present transactionA transaction made with the physical card at a payment terminal or ATM, rather than online or by phone. and the fraud involved a counterfeit card. The code applies the EMVEMV stands for Europay, Mastercard, and Visa. It is the technical standard for chip cards and, for this code, helps determine who bears the loss. chip liability shift when the transaction does not record a valid chip read.

For the issuer to file 4870, all of these requirements must be present:

  1. The cardholder denies authorization. The cardholder states that they did not authorize the transaction.
  2. The fraud involved a failed chip read. At least one of these two situations must have occurred:
    • the counterfeit card was used at a payment terminal or ATM that could not read the chip; or
    • the transaction went through a hybrid terminalA payment terminal or ATM that can read both the card’s chip and magnetic stripe. For code 4870, that capability does not prove the chip was actually read., but DE 55Data Element 55 contains the data generated by the chip. It lets Mastercard verify how the card was read and how the cardholder was verified. was absent from the authorization or financial transaction message.
  3. The genuine card had an EMV chip. The issuer had provided the cardholder with a valid chip card.
  4. The fraud was reported before the chargeback. The issuer reported the transaction as counterfeit to the Fraud and Loss DatabaseMastercard’s database where issuers report fraudulent transactions. For code 4870, the counterfeit report must precede the chargeback.. Mastercard allows up to three days for that report to be processed.

Source for the requirements: Mastercard Chargeback Guide, Merchant Edition, May 19, 2026, “Issuer Chargeback,” pp. 584–586.

A valid chip read would have exposed the counterfeit card. When all the requirements above are met, the missing chip read shifts the loss to the acquirer, the institution that connects the merchant to the Mastercard network, and the loss may reach the merchant.

Code 4870 does not apply to online, telephone-order, mail-order, or recurring transactions. Those cases route to 4837 or 4863. Fraud involving a lost, stolen, or never-received card under the chip rule generally routes to 4871. For eligible US transactions, the chip liability shift covers ATMs and all POS transaction types.

The dispute is also invalid if the required records show a valid chip transaction, a properly identified technical fallbackThis occurs when the terminal tries to read the chip, cannot, and completes the transaction using another technology. To support a defense, the fallback must be identified in the transaction records., or a service codeA code stored in the magnetic-stripe data and sent in DE 35 or DE 45. A first digit of 2 or 6 tells Mastercard that the genuine card had a chip. showing the card was not a chip card. Properly identified contactless transactions, DSRPDigital Secure Remote Payment is an authenticated online transaction with its own Mastercard liability treatment. It is outside code 4870., and consumer-presented QR payments are also outside this code. Each of these situations is independently enough to bar code 4870.

Source for the exclusions: Mastercard Chargeback Guide, Merchant Edition, May 19, 2026, “Transactions ineligible for chargeback,” pp. 580–581.

Deadlines for each party under Mastercard 4870

1 block represents 10 calendar days.

  1. IssuerFile the 4870 chargebackThe clock starts when Mastercard processes the transaction.
    Up to 120 calendar days
  2. AcquirerFile the second presentmentThe clock starts when the chargeback is settled.
    Up to 45 calendar days
  3. AcquirerUpload supporting documents to Mastercom (10 days for Maestro)The clock starts when the second presentment is generated.
    Up to 8 calendar days
  4. AcquirerRespond to the issuer’s pre-arbitration caseThe clock starts when the issuer submits the pre-arbitration case.
    Up to 30 calendar days
  5. IssuerAsk Mastercard to decide the caseThe clock starts when the acquirer’s second presentment is settled.
    Up to 45 calendar days
These are the time limits set by Mastercard.Your deadline to submit documents may be shorter; confirm it with your acquirer.Source:Mastercard Chargeback Guide, Merchant Edition (19/05/2026), “Chip Liability Shift (Message Reason Code 4870)”: Supporting Documentation, Issuer Chargeback, Acquirer Second Presentment, Acquirer Response to a Pre-arbitration Case e Issuer Submission of an Arbitration Case (pp. 583–606)

Who files the dispute and what happens next

The issuer files code 4870 in MastercomMastercard’s system where the issuer files the chargeback and the acquirer submits its response and case documents.. The merchant does not respond directly to Mastercard.

Before filing the dispute, the issuer must gather one of these document sets:

  1. A complete cardholder statement. A letter, email, message, or Form 0412Mastercard’s Dispute Resolution Form—Fraud. It records the conversation in which the cardholder or a representative disputes the transaction. stating both that the cardholder did not authorize the transaction and that the cardholder retained possession and control of every valid card on the account.
  2. A statement plus certification. The cardholder’s statement that they did not authorize the transaction and an issuer letter certifying that counterfeit fraud occurred.
  3. A company or government statement. This route applies only to a corporate card when the organization no longer employs the authorized cardholder.

If the issuer uses Form 0412, it must also close and block the account before the chargeback. Listing the account in the Mastercard Stand-in Account File with a “capture card” response has regional exceptions, including for certain cards issued in Latin America and the Caribbean.

Source for the issuer’s documents and controls: Mastercard Chargeback Guide, Merchant Edition, May 19, 2026, “Supporting documents,” pp. 585–586.

After filing, the dispute follows this order:

  1. The issuer files the first chargeback. The value is returned to the issuer, and the acquirer reviews the case.
  2. The acquirer files a second presentmentThe acquirer’s formal response in Mastercom showing why the chargeback should be reversed. It uses a ground Mastercard permits and the records required for that ground.. The standard deadline is 45 calendar days from chargeback settlement. The merchant gives its records to the acquirer, which files the response.
  3. The issuer may file pre-arbitrationAn optional step where the issuer asks for review of the second presentment before Mastercard decides the case.. This step is optional under the standard rule, and Mastercard recommends proceeding directly to arbitration. If pre-arbitration occurs, the acquirer has 30 calendar days to accept, reject, or take no action; no action shifts liability to the acquirer.
  4. The issuer may take the case to arbitration. The standard deadline is 45 calendar days from settlement of the second presentment, whether or not pre-arbitration occurred. Mastercard decides from the documented record, and the losing party pays the fees.

Source for the flow and deadlines: Mastercard Chargeback Guide, Merchant Edition, May 19, 2026, “Acquirer Second Presentment,” pp. 587–599; “Issuer Submission of a Pre-arbitration Case,” pp. 600–604; and “Issuer Submission of an Arbitration Case,” pp. 605–606.

Before building a defense, check whether this dispute is invalidProving any one condition is enough to challenge the dispute's validity.
  • The chip transaction was valid: DE 55 (chip data) was transmitted in the authorization when online authorization occurred and in the First Presentment/1240 message.
  • The transaction was a properly identified technical fallback (DE 22 subfield 1 equals 01, 79, or 80)—except at an intra- or inter-European ATM, where the issuer retains a counterfeit-fraud compliance right.
  • The first digit of the service code in DE 35 or DE 45 is neither 2 nor 6: the card was not an EMV chip card, or the counterfeit card had an altered service code—the issuer’s own risk.
  • The transaction was properly identified and authorized as contactless, DSRP, or Mastercard Consumer-Presented QR.
  • The transaction was mail-order, telephone-order, e-commerce, or recurring—those cases route to 4837 or 4863.
  • The transaction involved a Commercial Payments Account (MAP) or a Biometric Card with successful biometric authentication.
  • The fraud involved a lost, stolen, or never-received PIN-preferring chip card used at a terminal that could not accept PIN—that case belongs under 4871.
  • The account’s FNS fraud counter exceeds 35, or the issuer approved the transaction after two or more earlier fraud chargebacks under 4837, 4870, or 4871 on the same account.
  • The transaction was not reported as counterfeit to the Fraud and Loss Database before the chargeback.

Source:Mastercard Chargeback Guide, Merchant Edition, 19/05/2026 — "Transactions ineligible for chargeback", pp. 580–581

How to reduce the risk of this reason code

The merchant should treat reading the chip and transmitting the chip data as parts of the same process:

  1. Read the chip whenever the card has one. A compatible terminal is not enough if the sale is completed using the magnetic stripe or manual entry without a valid chip-read attempt.
  2. Confirm that DE 55 is transmitted. For an online authorization, the chip data must appear in the authorization request and the First Presentment/1240 messageThe processing record the acquirer sends after the transaction to present it to Mastercard and calculate settlement.. If the transaction did not require online authorization, the acquirer must be able to retrieve the complete DE 55 for the defense.
  3. Record fallback correctly. When the terminal tries the chip and switches technology, the authorization and first presentment must preserve the indicators for that event. Manually entering the card data without first trying the chip does not create this exception.
  4. Keep transaction-level records. Ask the acquirer or processor for access to terminal, authorization, chip, and settlement data. Without those records, the merchant cannot prove which defense ground applies.

Source for chip reading, data transmission, and the fallback exception: Mastercard Chargeback Guide, Merchant Edition, May 19, 2026, “Transactions ineligible for chargeback,” p. 580, and “Acquirer Second Presentment,” pp. 587–594.

Evidence the merchant and acquirer need to gather

Prove chip use

The merchant gives the records to the acquirer, which files the second presentment in Mastercom. The response must use exactly one primary ground. It is not a checklist for combining arguments. After selecting the ground, gather all required items within it:

  1. DE 55 was already in the first presentment. The record must include DE 55 in the 1240 message and a CVMCardholder Verification Method is the method used to verify the cardholder, such as a PIN. The result appears in the chip data and shows how the transaction was authenticated. result proving one of three alternatives: chip-and-PIN, chip on a card that is not PIN-preferring, or CVM fallback. The response uses the message text “DE 55 PREVIOUSLY PROVIDED.”
  2. The chip transaction did not require online authorization, and DE 55 was not in the first presentment. Both items are mandatory: complete DE 55 with all subelements, supplied now, and a record showing that no online authorization request occurred. The response uses “CHIP TRANSACTION.”
  3. The chip was authorized offline. All elements must coexist: the chip was read, the transaction did not require online authorization, and DE 55 was in the first presentment. The response uses code 2700.
  4. The merchant already issued the refund. The record must include the date and ARDAcquirer Reference Data is the reference created during processing to locate a specific transaction. in DE 72. A partial refund resolves only the credited amount; the issuer may continue the dispute for the remaining balance if no other remedy applies. This route does not apply to an ATM transaction.
  5. The liability shift does not apply. One proven condition is enough: the service code does not start with 2 or 6, a technical fallback was properly identified, a hybrid terminal actually processed or attempted the chip, the region has no applicable liability shift, the Fraud and Loss Database report is missing, the fraud counter exceeds 35, or the issuer approved the transaction after two earlier fraud chargebacks. The terminal’s hybrid capability alone does not resolve the case: if DE 55 was required and not sent, the issuer’s qualifying condition remains present.
  6. The chargeback has a procedural defect. One defect is enough, such as filing after the deadline, duplication, a mismatch between the dispute identifiers and the first presentment, or documentation that is missing, illegible, incomplete, or tied to another case.

Source for the grounds and the logic within each one: Mastercard Chargeback Guide, Merchant Edition, May 19, 2026, “Acquirer Second Presentment,” pp. 587–599.

The full PANPrimary Account Number is the card account number. In Mastercom documents, it must be masked so that only the last four digits remain visible. must be hidden in the documentation. Documents must be uploaded to Mastercom within eight calendar days after the second presentment is generated, or ten days for Maestro. Evidence required in the second presentment cannot be held back for pre-arbitration or arbitration.

If no route is fully supported, the acquirer and merchant should accept liability or issue a refund instead of filing an unsupported defense.

Source for the documentation rules: Mastercard Chargeback Guide, Merchant Edition, May 19, 2026, “Supporting Documentation,” pp. 583–584, and “Acquirer Response to a Pre-arbitration Case” and “Issuer Submission of an Arbitration Case,” pp. 604–606.

Frequently asked questions

When does Mastercard use chargeback reason code 4870?

4870 covers counterfeit fraud under the EMV chip liability shift. Every requirement must be met: the cardholder denies authorizing the transaction, the genuine card had an EMV chip, the issuer reported the fraud as counterfeit before the chargeback, and one of two failures occurred. A counterfeit card was used at a non-hybrid POS terminal or ATM, or the transaction went through a hybrid terminal without DE 55 in the authorization or financial transaction message.

What is the difference between Mastercard codes 4870 and 4871?

Both codes concern the chip liability shift, but they cover different fraud. 4870 applies to counterfeit-card fraud with an unaltered service code. 4871 applies to a lost, stolen, or never-received PIN-preferring chip card used at a terminal that cannot accept PIN. Mastercard’s 4871 chapter directs counterfeit fraud with an unaltered service code to 4870.

Does Mastercard code 4870 apply to an online purchase?

No. Mail-order, telephone-order, e-commerce, and recurring transactions are outside 4870. Card-not-present fraud routes to 4837 or 4863. Code 4870 covers only card-present transactions at POS terminals or ATMs.

How can a merchant respond to a 4870 chargeback?

The merchant works through its acquirer, which files a second presentment in Mastercom within 45 calendar days of chargeback settlement. The acquirer cites exactly one applicable ground: a valid chip transaction with DE 55 in the first presentment, an offline-authorized chip transaction, a refund already issued, or an invalid chargeback. Invalidity may involve technical fallback, a non-EMV card, no applicable liability shift, no Fraud and Loss Database report, a fraud threshold, a late filing, or duplication.

When does technical fallback invalidate a 4870 chargeback?

Technical fallback invalidates the chargeback when it is properly identified: DE 22 subfield 1 equals 01, 79, or 80. The issuer then authorized at its own risk, and the liability shift does not apply under code 2008. For an intra- or inter-European ATM transaction, however, the issuer retains a counterfeit-fraud compliance right.

Must the issuer report the fraud before filing a 4870 chargeback?

Yes. The issuer must report the transaction as counterfeit to the Fraud and Loss Database before the chargeback, with a three-day processing tolerance. Without that report, the acquirer can defeat the dispute in second presentment using loss-data-file evidence.

View all Mastercard chargeback reason codes or return to Knowledge.

First step

Start with your chargeback history.

Sparsu uses the data you already have to size the opportunity, recognize patterns and identify which data can improve the next decisions.