How is 4840 different from a normal fraud chargeback like 4837?

Under 4837 the cardholder denies the entire transaction relationship. Under 4840 the cardholder admits doing business with you but claims extra transactions were processed fraudulently on top of the legitimate one. The implication is misconduct at the merchant level, which is why acquirers scrutinize 4840s far more heavily.

Can a duplicate billing error trigger a 4840 instead of a processing error code?

Yes. If an issuer believes the duplicate was intentional rather than clerical, they can file under 4840. In representment, showing the duplicate came from a documented batch error and was already refunded usually resolves it, but you want to correct the root cause immediately so the pattern does not repeat.

Mastercard · Fraud

Reason code 4840: Fraudulent Processing of Transactions

Code 4840 applies when a cardholder made a legitimate card-present transaction at a merchant, but additional transactions were processed on that card at the same location without authorization. The claim is that the merchant, or someone with access to the merchant's terminal, ran extra charges after capturing the card data. It targets merchant-side skimming and duplicate fraudulent processing rather than third-party card theft.

Issuer filing window

typically 120 days from the central site business date

Merchant response window

typically 45 days to respond via second presentment

Why 4840 chargebacks happen

An employee ran additional unauthorized charges on a customer's card after a legitimate sale.
Card data captured at your point of sale was reused to process later transactions the cardholder never approved.
A compromised terminal or POS system at your location allowed skimmed card details to be replayed as new transactions.
A batch error re-submitted settled transactions in a way the issuer interpreted as fraudulent duplicate processing rather than a clerical mistake.

How to fight a 4840 chargeback

Provide signed receipts, EMV chip data, or PIN verification records for every disputed transaction, not just the one the cardholder acknowledges.
Show that each transaction represents a distinct purchase with separate items, timestamps, and invoice numbers rather than a replay of the original sale.
Submit terminal logs demonstrating the card was physically present and read for each charge in question.
If the extra charge was a legitimate follow-on transaction such as a balance payment or gratuity adjustment, document the cardholder's agreement to it.
Respond through Mastercom within 45 days; unanswered 4840 disputes are treated as conceded and add weight to any fraud audit review of your MID.

How to prevent 4840 chargebacks

Restrict manual key-entry and re-authorization functions on terminals to managers, and log every use with an employee ID.
Maintain PCI DSS compliance and patch POS software promptly so card data cannot be harvested and replayed from your environment.
Reconcile batches daily to catch duplicate submissions before they settle and are disputed as fraudulent processing.
Use point-to-point encryption so card data is never available in the clear anywhere in your stack.

Frequently asked questions

How is 4840 different from a normal fraud chargeback like 4837?: Under 4837 the cardholder denies the entire transaction relationship. Under 4840 the cardholder admits doing business with you but claims extra transactions were processed fraudulently on top of the legitimate one. The implication is misconduct at the merchant level, which is why acquirers scrutinize 4840s far more heavily.
Can a duplicate billing error trigger a 4840 instead of a processing error code?: Yes. If an issuer believes the duplicate was intentional rather than clerical, they can file under 4840. In representment, showing the duplicate came from a documented batch error and was already refunded usually resolves it, but you want to correct the root cause immediately so the pattern does not repeat.

Related Mastercard codes