ChargebackKit
MastercardFraudUpdated June 2026

Mastercard Reason Code 4840: Fraudulent Processing of Transactions

The issuer believes the merchant processed transactions in a fraudulent manner — for example by splitting a single purchase into multiple smaller charges to stay below authorization thresholds, or by processing a transaction after a decline.

Respond within ~45 days
Winnable with strong evidence

Your strongest argument

Each charge has a valid authorization and corresponds to a distinct, separately ordered purchase — no split-ticket or post-decline processing occurred.

Evidence that wins a Mastercard 4840 dispute

  • Authorization approval code for each transaction, showing no charge was force-posted after a decline
  • Distinct order IDs, line items, and delivery or service records proving each charge was a separate legitimate purchase
  • Proof transactions were not split to avoid authorization limits
  • Settlement records showing each transaction matched its corresponding authorization

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

Source: Mastercard Chargeback Guide. The Mastercard 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 Mastercard 4840. 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 — freeLook up another code

How processors label this dispute

ProcessorWhat you'll see
Stripereason: fraudulent

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 4840 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 — $19

Or run the free readiness check first.

Frequently asked questions

What is Mastercard reason code 4840?↓
Mastercard 4840 ("Fraudulent Processing of Transactions") is filed when the issuer believes the merchant processed transactions in a fraudulent manner — for example by splitting a single sale into multiple charges or by processing after a decline.
How do I respond to a 4840?↓
Show that each charge has a valid authorization and represents a separate, legitimate purchase. Provide order records, line items, and delivery proof that tie every charge to actual goods or services delivered.
What is split-ticket processing and why does it trigger 4840?↓
Split-ticket (or split-sale) processing means dividing one purchase into multiple smaller transactions — often to stay below a floor limit or avoid authorization. Mastercard prohibits it, and issuers use 4840 when they detect it.

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

Updated June 2026. This code’s meaning and evidence requirements are sourced from the Mastercard Chargeback Guide and may change as Mastercard 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.