Mastercard Reason Code 4863: Cardholder Does Not Recognize

What Mastercard reason code 4863 means

4863 is a fraud-category code for card-not-present transactions. The cardholder has looked at their statement, can’t identify a charge, and tells the issuer it may be fraudulent. The issuer doesn’t need the cardholder to assert outright that someone else used the card. “I don’t recognize this” is enough to file.

Under Mastercard’s current Chargeback Guide, fraud claims of this kind are handled within the No Cardholder Authorization framework of 4837, and many processors now map 4863 cases to 4837. You will still see 4863 on notices, in older processor portals and in reports, and the pattern behind it is distinct enough to treat on its own. Before a fraud chargeback, issuers are generally required to report the transaction to Mastercard’s fraud reporting system.

Why 4863 is mostly friendly fraud

The claim is about recognition, not authorization, and recognition fails for ordinary reasons:

• Your billing descriptor doesn’t match your brand name or store URL.
• The customer bought from one of several storefronts run by the same company.
• A free trial converted to paid and the customer forgot signing up.
• A spouse, child or colleague used the card with permission.
• The charge posted days after checkout because you capture at shipment.

These are friendly fraud cases: real customers, real orders, and a statement line they can’t place. Our guide to unrecognized charge disputes covers the pattern across networks. True third-party fraud also arrives under this code, so check whether the order looked risky before you decide to fight.

Evidence that wins a 4863 dispute

1. A clear description of the purchase: product names, order number, order date, your brand and the descriptor that appeared on the statement. Mastercard has long allowed merchants to respond to 4863 with details that help the cardholder recognize the charge.
2. 3-D Secure / Mastercard Identity Check result, if the transaction was authenticated.
3. AVS and CVC match from the authorization.
4. IP address, device and geolocation consistent with the cardholder’s billing or shipping address.
5. Delivery confirmation to the cardholder’s address, or download and login records for digital goods.
6. Customer account history: account age, logins and prior orders on the same card that were not disputed.
7. Communication from the customer: support tickets, order confirmation emails opened, reviews left.
8. Signup and trial terms for subscription charges, with the renewal reminder you sent.

Lead the rebuttal with the facts that link the transaction to the cardholder personally, not with your policies.

How to prevent 4863 chargebacks

• Set a descriptor that matches your storefront name, and add a support phone number or URL where your processor allows it.
• Send order and shipping confirmation emails that name the brand exactly as it appears on the statement.
• Send renewal reminders before trial conversions and subscription renewals.
• Use 3-D Secure on higher-risk orders to move fraud liability to the issuer.
• Make it easy to reach support so customers ask you before they ask their bank. See how to prevent chargebacks.

Should you fight or accept?

Fight when the order shows clear signs of the genuine cardholder: matching AVS, a known device or IP, delivery to their address, or an account with undisputed history. Those cases are winnable, and fighting them discourages repeat behavior.

Accept when the order has fraud markers: mismatched billing and shipping, a new account with a rushed checkout, a high-risk IP, or several cards tried in a row. In that case the cardholder is probably right, and your effort is better spent tightening fraud screening. For help telling the two apart, see first-party vs friendly vs true fraud.