Mastercard Reason Code 4860: Credit Not Processed

What Mastercard Reason Code 4860 Means

Mastercard reason code 4860 is titled Credit Not Processed and falls under the Consumer Disputes category. It is filed when a cardholder expected a credit or refund to appear on their Mastercard account — whether from a returned product, a cancelled service, or a merchant's explicit promise to refund — but the credit never materialized.

This code is distinct from quality disputes. The cardholder is not claiming the product was defective or the service was inadequate. They are claiming specifically that a refund that was owed to them was never posted to their account. The merchant's defense is either to show the credit was in fact processed (with documentation), or to explain why a credit is not owed under the terms of the sale.

Cross-Network Equivalent Codes

Common Trigger Scenarios

• Return accepted but credit never issued. A customer returned a product in-store or by mail, received an acknowledgment that the return was accepted, but the credit was never submitted to the card network. The cardholder waited the expected processing time and filed a dispute when nothing appeared.
• Customer service promised a refund that was never processed. A support agent told the customer "your refund will be processed within 5-7 business days" but the refund was never actually submitted. Either a processing error occurred, the agent exceeded their authority, or the promise fell through the cracks.
• Cancelled order refund delayed past reasonable timeframe. An order was cancelled — either by the customer or by the merchant — and the merchant acknowledged the cancellation, but the refund took longer than the cardholder expected (or never came). The cardholder filed a chargeback rather than waiting further.
• Credit issued to wrong card or account. The merchant processed the refund but to a different card number — a previous card, a different family member's card, or a card that has since been replaced. The credit was issued but the cardholder never saw it.
• Partial refund for a full-refund-expected situation. The merchant issued a partial credit when the cardholder expected a full refund. The cardholder disputes the remaining balance as a missing credit, treating the partial amount as inadequate.

Key Deadlines & Timeframes

Evidence You Will Need

The primary question is whether a credit was issued. Pull your transaction records before anything else.

• Credit transaction record from your processor showing the refund was submitted — credit reference number, date processed, amount, and the card number it was issued to
• Return or cancellation confirmation showing the customer's return was accepted or order was cancelled, and the refund amount authorized
• Your return policy if the dispute involves a situation where a credit is not owed — showing the no-refund policy was conspicuously disclosed at time of purchase
• Customer service communication records documenting any interactions about the refund request, particularly any promises made or denied
• Batch settlement records showing the credit transaction was included in a submitted batch if the credit was issued but may not have reached the cardholder's account due to routing
• For store credit situations: documentation showing the cardholder was informed of the store-credit-only policy and accepted it, including their use of the store credit if applicable

How Merchants Lose This Dispute

• Credit was genuinely never processed. The most common cause of 4860 losses is that the refund simply was not submitted. A staff member accepted a return and told the customer the credit was coming, but never actually processed it in the system. Implement return workflows that require a credit transaction number before the return is considered complete.
• Cannot produce a credit reference number. Even if you believe a credit was issued, without a credit transaction reference number from your processor, you cannot prove it. "We always process refunds" is not sufficient evidence — the specific transaction record is required.
• Store credit offered when card refund was owed. If you issued a store credit without the cardholder's agreement, or your no-refund policy was not clearly disclosed at purchase, the cardholder is entitled to a card refund and your store credit does not defeat the chargeback.
• Credit issued outside the allowable window. If you wait too long to process a credit — past 30 days in many cases — the credit may not post correctly or may not be accepted by the network. Process refunds promptly after the return or cancellation is accepted.

Response Framework Overview

1. If credit was processed: lead with the credit reference number, processing date, and amount. This is usually sufficient to resolve the dispute in your favor within days.
2. If credit was not owed: present your return or cancellation policy showing the cardholder is not entitled to a refund under the terms they agreed to at purchase.
3. Attach the return or cancellation documentation. Show what the cardholder returned or cancelled, when, and what the agreed resolution was.
4. Include customer service records. If a refund was promised, show what was communicated. If a refund was declined with explanation, show that communication as well.
5. For store credit situations: provide evidence the cardholder agreed to store credit and, if available, evidence they used it — confirming they received the benefit of the credit.

Prevention Tips

• Require a credit transaction number before closing any return. Build your return workflow so that a refund cannot be marked "complete" until a credit reference number has been generated by your processor. This eliminates the "return accepted but credit never processed" scenario entirely.
• Send automated refund confirmation emails. When a credit is processed, immediately send the cardholder an email confirming the refund amount, date, and expected posting time. This prevents premature chargeback filings from customers who don't know the credit is coming.
• Process credits within 5 business days of return acceptance. Delayed credits are one of the leading triggers of 4860 disputes. A fast refund policy eliminates cardholder frustration before it becomes a chargeback.
• Make no-refund and store-credit-only policies visible at checkout. If your refund policy does not include cash-back to the original card, that must be disclosed prominently at purchase — on the product page, at checkout, and on the receipt. Hidden no-refund policies generate 4860 chargebacks at high rates.

Frequently Asked Questions

What triggers a Mastercard 4860 chargeback?

A 4860 chargeback is triggered when a cardholder expected a credit on their account but it never appeared. Common triggers include a return accepted but never credited, a customer service promise unfulfilled, a cancelled order not refunded, or a credit issued to the wrong card.

How long does a Mastercard refund take to appear?

Mastercard credits typically take 3-5 business days to appear after the merchant processes the refund. The merchant must actually submit the credit to their processor — promising a refund doesn't start the clock. If a chargeback arrives while a recent credit is still processing, provide your credit transaction record as evidence.

Can I win a 4860 if I already issued a refund?

Yes — this is the most winnable version of a 4860. Provide the credit transaction reference number, the date it was submitted, and the amount. The issuer will verify the credit posted and resolve the dispute in your favor.

What if I issued a store credit instead of a card refund?

A store credit is not equivalent to a Mastercard credit unless the cardholder explicitly agreed to accept it in lieu of a refund. If your return policy offers store credit only, that policy must be clearly disclosed at time of purchase. Even with disclosure, Mastercard may still side with the cardholder if the policy was not sufficiently prominent.

Related Codes & Resources