Mastercard 4863 — Cardholder Does Not Recognize — Potential Fraud
Mastercard 4863: the cardholder doesn't recognize your charge
By Byron Kiriibwa · Updated
Checked by three automated reviewers (facts against the playbook, search, and our rules), then approved by the author on .
Mastercard 4863 means the cardholder doesn't recognize the charge on their statement. It can be a real purchase under a name they don't know. It's decided on two things together: that the statement name clearly leads to your business, and that the cardholder made the purchase. If you can't connect the charge to a known customer or order, accept it.
The bank's test
The bank checks:
- Does the name on the cardholder's statement clearly lead to this seller?
- Can the seller identify the purchase and show the cardholder made it?
Evidence that answers it
“Where it goes” uses the names Stripe's and Square's APIs give each piece of evidence, which are the names Upheld uses in your packet. Nothing is sent without your approval; where Upheld can't send it for you, you submit it yourself. In Stripe's Dashboard, choose the matching type for each file or text field. In Square's, add it when Square asks you to “upload any additional evidence specific to your service type”.
| Evidence | When it counts | How to show it | Where it goes | For |
|---|---|---|---|---|
| How the statement name links to the seller | The name on the customer's statement belongs to the business they bought from: the statement name, the brand the customer bought from, and the website. | The descriptor as it appears on statements, the business and brand name, and the website. | Stripe: Uncategorized textSquare: Generic evidence | Every seller |
| Receipt or invoice | Showing it was sent to the cardholder's email. | The receipt or invoice sent to the customer. | Stripe: ReceiptSquare: Receipt | Every seller |
| Messages with the customer | Showing messages with the cardholder about this order. | The relevant messages only, dated, with the key lines highlighted or quoted in the response. | Stripe: Customer communicationSquare: Cardholder communication | Every seller |
| Earlier payments from the same customer | Showing the same customer paid before without disputing. | List each earlier payment with date and amount, and which identifiers match the disputed one (email, IP, device, shipping address, account). | Stripe: Uncategorized textSquare: Related transaction documentation | Every seller |
| Customer account history | The buyer has an account with the seller — created on a known date, used repeatedly, tied to the cardholder's email. | Account creation date, email, login count and dates, earlier orders. A screenshot or export from the seller's platform. | Stripe: Uncategorized file or Uncategorized textSquare: Cardholder information | Every seller |
| Proof of delivery | Showing delivery to the cardholder's address. | The carrier's delivery record showing date, address, and any signature or photo. | Stripe: Shipping documentationSquare: Proof of delivery documentation | Online stores |
| Access and usage log | Showing activity on the cardholder's own account. | Dated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export. | Stripe: Access activity logSquare: Online or app access log | Courses, memberships, digital products |
| Service delivered | The service took place — a session was attended, work was delivered, an event happened. | Dates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off. | Stripe: Service date or Service documentationSquare: Service received documentation | Services |
What doesn't help
- A receipt sent to an email that doesn't match the cardholder.
- Explaining the descriptor without showing who made the purchase.
Mastercard's rules for 4863
- The current guide has no 4863: Mastercard's Chargeback Guide – Merchant Edition (13 May 2025) doesn't list it, and names no code that replaces it. Stripe still lists it, under unrecognized (Stripe's dispute categories (docs.stripe.com/disputes/categories), checked 2026-10-29).
- Stripe puts this code, and Mastercard retrieval request 6321 ("cardholder does not recognize transaction"), in its unrecognized category. Source: Stripe docs, checked 2026-10-06.
- Visa and Amex cardholders who don't recognize a charge usually arrive under fraud codes. Use the fraud evidence plus the descriptor explanation.
Common mistakes with Mastercard 4863
- Treating it as a pure descriptor problem; still prove who bought.
- Using a statement descriptor that doesn't match the brand name on the website or receipt.
Should you fight it?
Fight it when you can show both halves: that the name on the statement leads to the business the customer bought from, and that the cardholder made the purchase, with a receipt sent to their email, delivery to their address, their use of the account, or earlier payments they didn't dispute. Explaining the statement name without showing who bought leaves the second half open. Accept it when this is true:
- The seller can't connect the charge to a known customer or order.
If you accept, don't refund as well: once it's a chargeback the money has already gone back to the customer, so a refund would pay them twice.
A dispute counts against your account whether you win or lose. To see the chance of winning at which fighting pays on your amount, try the fight-or-accept calculator; to compare what you keep with each tool, the fee calculator.
How to prevent the next one
- Set a statement descriptor that matches the brand customers know, plus a support URL or phone number.
- Send a receipt for every charge, naming the descriptor that will appear on the statement.
- For subscriptions, name the product in each renewal receipt.
Deadlines and fees
| Platform | Deadline | Fees |
|---|---|---|
| Stripe (US)Checked 2026-10-21 | Respond by the due date on the dispute in your Stripe Dashboard. It's usually 7 to 21 days, depending on the card network. | $15 when the dispute arrives, which isn't returned. $15 more when you respond, returned only if you win in full.Stripe's Smart Disputes waives the $15 response fee and takes 30% of the disputed amount when you win. |
| SquareChecked 2026-10-21 | Seven days from Square's first email about the dispute. | No fees for dispute management on chargebacks: Square covers the fee for disputes you challenge together. |
| Shopify Payments (US)Checked 2026-10-21 | Respond by the evidence due date in your Shopify admin. It's usually 7 to 21 days. | $15 per chargeback, returned if you win. |
A worked example (made up)
Your online shop sells hand-bound notebooks under its brand name, but card statements show your company's legal name. A returning customer orders two notebooks for $48 on April 6. The receipt goes to the email on their account, and the carrier delivers to their address on April 10. They have two earlier orders on the same account, neither disputed. In May the cardholder files a 4863 dispute saying they don't recognize the charge.
The response would attach:
- Exhibit A: how the statement name links to the shop: the name on the statement, the shop's brand, and the website, which names the company behind the shop.
- Exhibit B: the April 6 receipt, sent to the email on the cardholder's account.
- Exhibit C: the customer's account record, with two earlier orders on it, neither disputed.
- Exhibit D: the carrier's delivery confirmation to the cardholder's address on April 10.
A sample response letter (made up)
For the example above. It's laid out the way Upheld drafts a response: one part for each thing the bank checks, strongest evidence first, each pointing to its exhibit. Yours should state only what your own records show.
We contest this dispute, Mastercard reason code 4863, for $48.00 charged on April 6 for two notebooks. The name on the statement is our company's legal name, and the cardholder made this purchase.
The statement name leads to us. It is the legal name of the company that runs our shop, and our website names that company alongside the shop's brand (Exhibit A).
We can identify the purchase and the cardholder who made it. The receipt for the order went to the email on the cardholder's account (Exhibit B). That account has two earlier orders, neither disputed (Exhibit C), and the notebooks were delivered to the cardholder's address on April 10 (Exhibit D).
The charge is ours under our legal name, and the receipt, the account and the delivery all tie it to the cardholder. We ask that the dispute be decided in our favor.
Questions people ask
What is a Mastercard 4863 chargeback?
Mastercard's code for Cardholder Does Not Recognize, Potential Fraud: the cardholder doesn't recognize a transaction on their statement. It can be a real purchase that appears under a name the cardholder doesn't connect with the business.
Is 4863 still a Mastercard reason code?
Mastercard's current Chargeback Guide (Merchant Edition, 13 May 2025) doesn't list it and names no code that replaces it. Stripe still lists 4863, in its unrecognized category.
Is explaining our statement descriptor enough to answer a 4863?
No. The bank also checks that you can identify the purchase and show the cardholder made it, so send the descriptor explanation with a receipt to their email, delivery to their address or their account's use, and earlier undisputed payments.
What is Mastercard retrieval request 6321?
Mastercard's retrieval request for "cardholder does not recognize transaction". Stripe puts it, with 4863, in its unrecognized category.
Our receipt went to a different email from the cardholder's. Does it still count?
It doesn't help: a receipt sent to an email that doesn't match the cardholder doesn't show they made the purchase. Lean on delivery, account use or earlier payments instead.
Draft yours free
Answer a few questions and get a draft, an evidence checklist and an honest read on whether to fight. Free account, no card.
Not sure what your notice says? Decode it first.