MastercardFraudUpdated June 2026

Mastercard Reason Code 4863: Cardholder Does Not Recognize

The cardholder does not recognize the transaction on their statement (often a billing-descriptor confusion rather than true fraud).

Respond within ~45 days
Highly winnable

Your strongest argument

The order ties to the cardholder’s own account and your billing descriptor, resolving the "I don’t recognize this" confusion.

Evidence that wins a Mastercard 4863 dispute

  • Clear billing-descriptor records matching your business name
  • Order details, receipt, and customer information
  • Proof the customer placed and received the order

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 4863. 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 — free

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 4863 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 4863?
Mastercard 4863 ("Cardholder Does Not Recognize") is filed when the cardholder does not recognize a charge — frequently a billing-descriptor issue rather than real fraud.
How do I win a 4863?
Connect the charge to the customer’s own order and account, and show a clear billing descriptor. These are highly winnable when records are complete.
How do I prevent 4863?
Use a recognizable billing descriptor that includes your customer-facing brand name and a support contact.

Where to go next

Build the pack for Fraudulent / Unauthorized disputes, or dig into the matching guide, template, and processor evidence requirements.

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.