Skip to content
NoChargeback

Mastercard reason code 4863 and how to win unrecognized charge disputes

Mastercard reason code 4863 (Cardholder Does Not Recognize, Potential Fraud) means the cardholder sees a charge on their statement they cannot identify and suspects fraud. Many of these disputes come from an unclear descriptor or a forgotten purchase, so you win by showing who bought, what they bought and how to recognize it.

Draft my evidence See pricing

Read and dispute permissions only. We never move your money.

What Mastercard reason code 4863 means

4863 sits in Mastercard's fraud category, but unlike 4837 the cardholder does not state the card was stolen. They only say they do not recognize the transaction. That makes it a common route for friendly fraud and for honest confusion about merchant names, subscription renewals or purchases made by family members. Clear identifying details and proof of a relationship with the cardholder often resolve it.

Typical triggers for a 4863 chargeback

  • A statement descriptor that shows a legal entity or parent company instead of your brand.
  • A subscription renewal or trial conversion the cardholder forgot.
  • A purchase by a spouse, child or employee on a shared card.
  • A charge processed days after the order, so the date does not match the cardholder's memory.
  • A billing name that differs from the website the customer used.

Time limits for Mastercard 4863

The cardholder typically has 120 days from the transaction date to dispute. Your response window is set by your processor and is much shorter, often 7 to 21 days at Stripe. Missing the evidence due date loses the dispute automatically.

Evidence that wins a 4863 dispute

  • A clear description of what was sold, with the brand name, website and how it appears on the statement.
  • The customer's name, email, billing address and phone matching the cardholder.
  • AVS and CVC match results, and 3D Secure authentication if it was used.
  • IP address, device and location, matched to earlier undisputed orders from the same customer.
  • Prior undisputed transactions with the same card or account, which Mastercard programs for first party misuse can take into account.
  • Login, download or usage logs after the purchase.
  • Signup and renewal reminder emails for subscriptions.

What to avoid when you respond

  • Do not treat 4863 as a lost cause because it sits in the fraud category.
  • Do not assume the issuer knows your brand. Explain the descriptor in the first lines.
  • Do not refund after the chargeback is filed, since the funds are already withdrawn.
  • Do not send raw logs without a short explanation of what they prove.

How to prevent Mastercard 4863 chargebacks

  • Use a statement descriptor with your brand name and a support phone or URL.
  • Send a receipt that names the descriptor customers see on their statement.
  • Remind subscribers before each renewal.
  • Share order details with issuers through Ethoca alerts, so the cardholder sees what they bought before filing.
  • Track friendly fraud patterns by customer and product.

How 4863 appears in Stripe

Stripe usually shows 4863 disputes with the reason unrecognized, and some issuers file them so they appear as fraudulent. The raw code is always in the network reason code field on the dispute. NoChargeback reads it, pulls customer history, AVS, CVC, 3D Secure and IP data from the charge and fills the Stripe evidence fields. See Stripe chargeback protection.

Rebuttal letter opening for Mastercard 4863

We are responding to the dispute filed under Mastercard reason code 4863. The charge appears on the statement under our registered descriptor and relates to the order placed on our website by the cardholder, using the name, email and billing address on file. The purchase came from a device and IP address used in earlier undisputed orders, and the account was used after the charge. The order record and customer history are attached below.

Draft my evidence

What is the difference between Mastercard 4863 and 4837?

With 4837 the cardholder states they did not authorize the transaction. With 4863 they only say they do not recognize it, which often points to a descriptor problem or a forgotten purchase.

Can a clearer descriptor stop 4863 chargebacks?

It removes a major cause. When customers see your brand name and a support contact on the statement, many call you instead of their bank.

What is the strongest evidence for 4863?

Proof that ties the purchase to the cardholder, such as matching contact details, prior undisputed orders from the same device or IP, and usage after the charge.