Mastercard's "I don't recognise this charge" code, decided on whether the merchant can connect the order to the legitimate cardholder before the issuer rules it fraud.
Mastercard 4863 looks like a fraud dispute and is filed like one, but the cardholder is usually not claiming the card was stolen. They are saying they do not recognise the charge, which often means they do not connect the merchant name on the statement to a purchase they actually made. The merchant's job in the rebuttal is to close the recognition gap, not to fight a fraud claim that was never really there.
How the dispute actually arrives
The notification arrives with the cardholder claim phrased some variant of "I do not recognise this transaction." The merchant has 45 days to respond. 4863 is most common against subscription businesses, parent-company billing arrangements, and merchants whose statement descriptor differs from the customer-facing brand.
It sits alongside Mastercard 4837 (No Cardholder Authorization) in the fraud family but is the softer of the two. 4837 is the cardholder asserting fraud; 4863 is the cardholder asserting confusion. The evidence that resolves confusion is different from the evidence that defeats fraud.
What the issuer is looking for
The issuer wants the merchant to show that the legitimate cardholder placed the order or has previously transacted with the merchant. Customer account history is the strongest single piece of evidence: a buyer with five prior successful orders contesting their sixth as unrecognised is rarely upheld by the issuer if the merchant produces the order history.
Descriptor evidence matters more than merchants assume. A statement line reading "ACME HOLDINGS LLC" against a customer who bought from "BetterPillow.com" is a recognition failure even where the transaction was genuine. The cardholder's agreement to the descriptor at checkout, where it exists, closes that gap.
Common scenarios merchants see
A monthly subscription billed under the parent-company name. The cardholder sees a charge they do not associate with their gym, software, or content service. The fix is a clearer descriptor; the case in front of the issuer turns on whether the merchant can produce the sign-up record and the cardholder's consent to the billing arrangement.
A shared household card used by a spouse, child, or business co-owner. The merchant has no way to know who at the household placed the order, but a delivery to the billing address and a buyer's email matching prior orders make a strong case.
A long-standing customer disputing one of many transactions. The order history alone often wins these. A pattern of legitimate orders is what the issuer reads first; the disputed transaction sits inside that pattern.
What this code is not
4863 is not a no-receipt code, a not-as-described code, or a billing-error code. If the cardholder is complaining about what they got, the issuer will route the dispute under 4853 with the appropriate condition attached. Submitting delivery proof to a 4863 case is not wrong, but it is not what the issuer asked for, and a letter that leads with the recognition argument wins more often.
Where this fits in our service
Mastercard 4863 disputes turn on the merchant's customer-history records, not the evidence of any single transaction. The rebuttal letter is built from the account history, the descriptor agreement at checkout, and the device-and-address footprint of the buyer. If you have just received one, you can start with a free first letter.
Official source: Mastercard rules. Last reviewed 2026-05-14.