Code4863TypeFraudFiling window120 daysMonitoringChargeback count (ECP)What does Mastercard 4863 mean?
The cardholder looked at a charge on their statement and could not connect it to anything they bought. They told their bank, and the bank filed it as potentially fraudulent, because from the bank's side an unrecognized charge and a fraudulent one look identical.
It is softer than a firm fraud claim. The cardholder isn't swearing someone stole their card; they're saying the statement line meant nothing to them. That distinction is exactly why this code is winnable, and preventable.
What causes a 4863 chargeback?
- A statement line that doesn't match the brand the customer bought from.
- A rebill weeks after signup, long after the purchase faded from memory.
- A legal entity name on the statement instead of the product name.
- A shared card, where the person reading the statement isn't the person who bought.
Why do subscription businesses get 4863?
Subscription businesses collect 4863 for a structural reason: the charge that appears on the statement is a rebill, separated by weeks from any purchase decision, and often labeled with a name the customer never saw at checkout.
That makes 4863 the purest descriptor-failure code on either network. Run your statement line through the checker the way a confused customer would read it, and you are looking at the fix.
Can a chargeback alert stop 4863?
Ethoca catches 4863 before it becomes a chargeback.
The cardholder contacts their bank first, which is when Ethoca, Mastercard's alert network, sees the dispute. Refund through the alert and no chargeback ever files, so nothing counts toward Mastercard's Excessive Chargeback Program. And because 4863 starts as confusion rather than conviction, a clear response often ends it entirely.
Alerts are one of the two levers here. See how RDR, CDRN and Ethoca work together, and check where your ratio stands before the letter checks it for you.
How do you respond to a 4863 dispute?
You win 4863 by helping the cardholder recognize the charge, or proving they made it. Send:
- The order details: what was bought, when, and from which page or app.
- The exact statement line the charge appeared under, connected to your brand.
- Prior undisputed charges from the same customer.
- Usage or delivery records showing the product was accessed after the charge.
- Any signup confirmation or receipt emailed to the cardholder.
Your processor sets your response deadline, usually 20 to 30 days from the chargeback.
How do you prevent 4863?
- Fix the statement line first. 4863 exists because customers read names they don't recognize.
- Put a way to reach you in the descriptor, so confusion becomes an email instead of a bank call.
- Send a renewal reminder before each rebill, so the charge is expected before it appears.
- Match your checkout brand, receipts, and statement line, one name everywhere.
The cardholder gets 120 days to file. You usually get 20 to 30 days to respond. And the dispute counts the day it files, win or lose, which is why prevention beats response.
FAQ
Is Mastercard 4863 a fraud chargeback?
It sits in Mastercard's fraud family, but the claim is softer: the cardholder doesn't recognize the charge, and the bank flags it as potentially fraudulent. Many 4863 disputes are legitimate customers confused by a statement line, which is why recognition evidence wins them.
What is the difference between 4863 and 4837?
4863 says the cardholder doesn't recognize the charge. 4837 says the cardholder firmly denies authorizing it. 4863 is the softer claim and often comes first; if the confusion isn't resolved, the same dispute can return as the harder 4837.
Can chargeback alerts stop 4863?
Yes. The cardholder contacts their bank first, so Ethoca sees the dispute before it becomes a chargeback. Refund through the alert and no chargeback files, which means nothing counts toward Mastercard's Excessive Chargeback Program.
How do I prevent 4863 chargebacks?
Make the statement line unmistakable. Use the brand name your customer saw at checkout, add a URL or phone number, and send a reminder before each rebill. 4863 is caused by confusion, and confusion is the one cause you can remove completely.
Checked against Mastercard's chargeback guide and Mastercard's dispute rules. Last reviewed August 28, 2026.
