What Mastercard reason code 4860 means
The issuer files this claim when the cardholder returned goods, canceled a service or was told a credit was on the way, and nothing appeared on the statement. Mastercard folded it into 4853 with a credit not processed sub case, so many issuers now use 4853 for the same complaint. Your answer depends on the facts: either the credit was processed, or your return and cancellation policy did not entitle the cardholder to it.
Typical triggers for a 4860 chargeback
-
A refund issued but not yet visible on the card statement.
-
A returned item received at the warehouse but not logged for refund.
-
A support agent who promised a refund that was never processed.
-
A return sent outside the return window or without the required authorization.
-
A canceled service where the customer expected a prorated credit your policy does not offer.
Time limits for Mastercard 4860
The cardholder typically has 120 days to dispute, often counted from the date they expected the credit. Your response window is set by your processor and is much shorter, often 7 to 21 days at Stripe. A missed due date loses the dispute automatically.
Evidence that wins a 4860 dispute
-
The refund record with ID, amount and date, and the card it went to.
-
The acquirer reference number for the refund, which the cardholder's bank can trace.
-
Your return or cancellation policy and proof the customer accepted it at checkout.
-
Proof the item was never returned, or arrived after the return window, or arrived used or damaged.
-
Usage logs showing the service was used after the claimed cancellation.
-
Support messages that show what was promised and when.
What to avoid when you respond
-
Do not issue a second refund after the chargeback is filed. You can lose the amount twice.
-
Do not claim no refund is owed if an agent promised one in writing.
-
Do not send a policy screenshot without the date and the place the customer saw it.
-
Do not miss the deadline while the warehouse checks the return.
How to prevent Mastercard 4860 chargebacks
-
Process refunds the same day a return is received and email the refund confirmation.
-
Tell customers how many business days a refund takes to appear on their statement.
-
Log every promised refund in your support tool and close it only after processing.
-
State the return window and condition rules on the product page and the receipt.
-
Use chargeback alerts to catch an inquiry and settle it before it becomes a chargeback.
How 4860 appears in Stripe
Stripe usually shows 4860, and 4853 disputes in the credit not processed sub case, with the reason credit_not_processed. The raw code is always in the network reason code field on the dispute. NoChargeback reads it, finds any refund already made on the charge, attaches your refund policy and fills the Stripe refund evidence fields. See Stripe chargeback protection.
Rebuttal letter opening for Mastercard 4860
We are responding to the dispute filed under Mastercard reason code 4860. The credit the cardholder requested was already processed to the same card on the date shown, with the refund reference attached so the issuing bank can trace it. No further amount is owed under the return policy the cardholder accepted at checkout. The refund record and policy are attached below.
Is Mastercard 4860 still used?
Mastercard generally handles credit not processed claims under 4853 today. Some processors and older reports still display 4860, and the evidence is the same under both.
What if I already refunded before the chargeback?
Submit the refund record with its date, amount and reference number. A refund made before the dispute is strong evidence that the claim should be reversed.
Do I have to refund a return sent after the deadline?
Not if your return window was disclosed and accepted at checkout. Show the policy, the acceptance and the date the return arrived.