Mastercard 4853: Cardholder Dispute: How to Respond and Win

Network: Mastercard · Reason code 4853 · Covers Stripe, Shopify Payments, PayPal, Braintree and Adyen

What reason code 4853 means

Cardholder Dispute is a Mastercard reason code. Under Mastercard rules, you have one shot to submit evidence that directly addresses what the code alleges.

The evidence that wins this code

• Delivery confirmation
• Product description match
• Customer communications
• Refund policy compliance

Defense strategy

Mastercard consolidated dispute code. Determine the underlying issue (not received, defective, etc.) and address specifically. Focus on delivery proof and product matching description.

How to respond, by gateway

Stripe

Stripe specifics for this dispute

• Deadline: 7-21 days depending on card network (check the Stripe dashboard deadline for your dispute)
• Where to submit: Stripe Dashboard → Payments → the disputed charge → Submit evidence. Stripe also supports automated dispute evidence with webhooks.
• Fee impact: Stripe charges a $15 fee when the dispute is received, kept win or lose. If you submit evidence (counter the dispute), a second $15 applies and that one is refunded when you win.
• Stripe quirk: Stripe requires evidence fields submitted via their structured form or API fields (uncategorized_text for anything else).

PayPal

PayPal specifics for this dispute

• Deadline: 10 days to respond to an 'Item Not Received' or 'Significantly Not As Described' claim
• Where to submit: PayPal Resolution Center → the case → Add Response. PayPal Seller Protection can shift liability entirely if shipping proof meets their terms.
• Fee impact: PayPal keeps the original transaction fee even on a refund; no separate chargeback fee for most seller cases.
• PayPal quirk: PayPal disputes are claims under their own flow, not card-network chargebacks, until the buyer escalates. Seller Protection criteria: proof of delivery to the address on the transaction, online tracking, signature for high-value orders.

Braintree

Braintree specifics for this dispute

• Deadline: network deadline shown per dispute (typically 7-14 days); Braintree emails a new-dispute notification
• Where to submit: Braintree Control Panel → Transactions → Disputed → Submit Evidence. Evidence text fields map to network evidence types.
• Fee impact: $15 per dispute (US), waived if the dispute is won.
• Braintree quirk: Braintree (a PayPal service) passes network chargebacks through under raw network rules. The evidence categories follow the card network, not Braintree's own taxonomy.

Adyen

Adyen specifics for this dispute

• Deadline: defense period shown in the Customer Area per dispute (usually 14-21 days)
• Where to submit: Adyen Customer Area → Transactions → Disputes → Defend. Adyen supports API-driven defense document upload (disputes/defend endpoints).
• Fee impact: Adyen passes the network chargeback fee through; amounts vary by scheme and region.
• Adyen quirk: Adyen's Defense Reasons map each network code to structured defense types. Choose the one matching your evidence, or Adyen defaults to a generic defense that loses specificity.

Response deadlines and fees at a glance

The gateway dashboard shows your exact deadline. At network level: Mastercard gives merchants 45 days to respond for most codes. The dispute clock started when the issuer filed the case.

Frequently asked questions

What can 4853 actually be?

Almost anything: defective goods, wrong item, credit not processed, cancelled order. Read the cardholder's claim text first; 4853 is Mastercard's catch-all and the evidence list changes with the claim.

How do I respond to a vague 4853?

Answer the stated claim directly, then add descriptor clarity (business name the buyer saw) and the full order record. Vague claims are won with organized, complete files.

Frequently asked questions

What can 4853 actually be?

Almost anything: defective goods, wrong item, credit not processed, cancelled order. Read the cardholder's claim text first; 4853 is Mastercard's catch-all and the evidence list changes with the claim.

How do I respond to a vague 4853?

Answer the stated claim directly, then add descriptor clarity (business name the buyer saw) and the full order record. Vague claims are won with organized, complete files.

What ChargeGuard does with reason code 4853

ChargeGuard maps this code to the exact evidence list above, checks your evidence vault for completeness, and drafts a network-compliant response you review before submission. The flow is identical whether the dispute landed in Stripe, Shopify Payments, PayPal, Braintree or Adyen.

Try ChargeGuard free for 14 days. No credit card required.