Reason codes / Credit / Refund Not Processed

Credit / Refund Not Processed disputes, handled plainly

The whole case is dates and transaction records. That makes these disputes unusually clean: either the receipts exist, or there is something you should do right now instead of fighting.

Worth fighting30 to 50%of these are won with the right evidence, industry average

What the bank was told

The cardholder told their bank a refund was promised, or owed under your stated policy, and never arrived. Nobody disputes that the purchase happened. The fight is over whether money should have come back, and whether it did.

If you issued the refund before the dispute was filed, submit the refund transaction record: these are about as strong as dispute responses get. If the refund went out after the dispute was filed, it does not clear automatically; you still need to respond with the evidence. If you owe a refund and have not sent it, process it now: the dispute fee plus a lost chargeback costs more than the refund. If the refund is legitimately not owed (e.g. outside your stated policy window), document why clearly.

How the bank actually decides it

One timeline decides it: was a refund owed under the policy shown at checkout, and when did it move relative to the dispute? A refund issued before the dispute was filed, documented with the processor record, is about as strong as dispute responses get.

If no refund was owed, the policy as the customer saw it at purchase is your case: the window, the conditions, and exactly where this request fell outside them. Stated policies defend you. Unstated ones do not.

The evidence that decides it

  • Refund transaction record from your payment processor
  • Date the refund was issued vs. dispute filing date
  • Refund confirmation email sent to customer
  • Your refund policy and stated processing timeline
  • Customer communication where refund was promised or acknowledged
  • Bank processing time disclosure (refunds take 5 to 10 business days)

Your first hour after it lands

Pull the refund record, or confirm none exists

The processor transaction and its date, set against the dispute's filing date, is the entire skeleton of this response.

If a refund is owed and unsent, send it now

The dispute fee plus a lost chargeback costs more than the refund you already owed. Sending it today is the cheapest available outcome.

If no refund is owed, document why

Collect your policy exactly as it appeared at checkout, the customer's request date, and the specific term the request fell outside.

One response only

A dispute response locks the moment it is submitted, yours orShopify’s automatic one, with no edits after. Whatever goes in first is your whole case, which is why the first hour matters more than the last day.

Preventing the next one

Questions merchants actually ask

I refunded after the dispute was filed. Is it over?

No. A refund sent after filing does not clear the dispute automatically. You still need to respond with the refund transaction record, so the case closes with the money and the paperwork matching.

The request was outside my policy window

Then document the policy exactly as the customer saw it at checkout and where the request fell outside it. Stated-policy cases are winnable. Policies that only existed in your head are not.

What does Backstop do with these?

It syncs the dispute with this code's guidance, assembles the order record and your refund policy into the evidence pack, and runs the deadline countdown with emails at 7, 3, and 1 day so the response actually goes in.

Where Backstop fits

Backstop lines up the dispute date against the order's history, assembles your refund policy and order records into the evidence pack, and keeps the deadline loud, because a receipts case that misses its deadline loses exactly like a weak one.

Live on the Shopify App Store

Install in under a minute. Free to watch; evidence packs are $19/month after a 14-day trial, cancel in one click.

Install on Shopify