Mastercard Reason Code 4860: Credit Not Processed

What Mastercard reason code 4860 means

4860 is a legacy cardholder-dispute code for missing refunds. The cardholder says one of these happened:

• They returned the goods and never got their money back.
• They cancelled an order, booking or service and weren’t credited.
• The merchant promised a refund, partial refund or price adjustment and it never arrived.
• A refund was issued for less than they expected.

Mastercard now handles this as the “credit not processed” sub-scenario of 4853 Cardholder Dispute. A related problem, a refund processed as a purchase, falls under 4834 instead.

Common causes

• Refunds promised by support but never processed
• Returns received but not matched to the order, so the refund never triggered
• Refunds that take several days to post, prompting the customer to dispute in the meantime
• Restocking fees or partial refunds the customer didn’t expect
• Non-refundable terms that weren’t visible at checkout
• Cancellations made just before a cut-off the customer didn’t know about

Evidence that wins a 4860 dispute

1. The refund record: date, amount and reference, ideally the ARN (acquirer reference number) the issuer can trace.
2. Your refund and return policy as disclosed at checkout, with the box the customer ticked or a checkout screenshot.
3. Return status: proof no return was received, or it arrived outside the return window, or in a condition your policy excludes.
4. Cancellation terms for bookings and services, with the timing of the customer’s request.
5. Calculation of any partial refund, such as a disclosed restocking fee or used portion of a service.
6. Customer communication, especially if they accepted store credit or an exchange instead.

If you refunded before the chargeback, lead with that. It’s usually decisive.

How to prevent 4860 chargebacks

• Refund the same day support promises it, and email confirmation with the amount and expected posting time.
• Tell customers refunds can take several business days to appear on their statement.
• Link returns to orders automatically so a received return triggers the refund.
• Display refund, restocking and cancellation terms near the payment button.
• Avoid refunding a transaction that’s already under dispute. Read chargebacks after a refund for how to handle overlaps.

Should you fight or accept?

Fight when you’ve already refunded (show the ARN), when no return was received, or when your disclosed policy meant no refund or a partial refund was due.

Accept when the customer returned the item or cancelled within your policy and you didn’t credit them. The chargeback gives them the refund they were owed, so don’t issue a second one. Then find out why the refund didn’t happen, because a 4860 almost always points to a gap in your returns or support process.