In customer service, one of the most expensive sentences is also one of the kindest: “Don't worry, we'll take care of it.” You type it to calm an upset customer and move on. Three weeks later it comes back. The bank has pulled the money out of your account, and the customer has sworn to their card issuer that you promised a refund and never paid it. You remember the conversation differently. Each of you believes your own version, and the bank has no way to know which one is true.

That is how a credit not processed chargeback usually starts. Visa files it under reason code 13.6, and other networks have their own equivalents. It has little in common with a fraud dispute. Nobody is claiming the card was stolen or that the product never showed up. The customer is saying that a deal was made and you broke it.

So the dispute is really about a promise and what that promise said, more than about the money. The single idea that wins most of these cases is simple: a refund promise has to exist in writing, with its conditions, before anyone needs it.

Why both of you remember it differently

The customer who files this dispute is usually not lying. More often they are remembering, and memory is less reliable than it feels.

Psychologists have known for about a hundred years that memory gets rebuilt each time we recall it. Frederic Bartlett showed in the 1930s that people retelling a story slowly reshape it to fit what they expected. Elizabeth Loftus later showed that small details after the fact, even the wording of a question, can change what people sincerely believe they saw. Neither of these is lying. Recall works that way.

Now apply that to a refund conversation. You wrote: “If the return arrives unused, we'll process a refund within a few days of receiving it.” The customer was frustrated and reading on their phone, and what stuck was “we'll process a refund.” The condition fell away. A month later, with their statement in front of them, they remember being promised a refund and not getting it, and they are sure of it.

Your memory is no better. You remember the condition because you wrote it and it matters to you. You may not remember that it lived in a phone call and not an email, or that a coworker told them something softer on live chat.

In this kind of dispute, two honest memories end up competing. The issuer will not decide between them. It looks at documents, and whoever has the clearer written record usually wins.

What the issuer is actually asking

A reviewer looking at a credit not processed dispute is trying to answer a few narrow questions:

  1. Did the merchant agree to give a refund or credit?
  2. If so, did the customer meet the conditions attached to it, for example returning the item?
  3. Has the refund already been issued?
  4. If no refund was owed, was the policy that says so shown to the customer before they paid?

Nearly every winning response answers one of these clearly. Either the refund already happened, here's proof, or the refund was conditional and the condition wasn't met, or no refund was owed under a policy the customer agreed to.

Notice what isn't on that list: how reasonable you were, how much time support spent, how unfair the customer is being. Those feel important when you're angry, and they don't change the outcome.

The refund that already happened

This is the most common case, and the easiest to win if you know where to look.

Many of these disputes come from timing. You refunded on Monday. Depending on the card issuer, the refund can take several business days or more to appear on the customer's statement, and it may show as a separate line item that's easy to miss. The customer looks, doesn't see it, and files.

Your evidence here is the refund record itself, and the strongest piece is the Acquirer Reference Number (ARN), a tracking number that card networks assign to the refund. The customer's bank can use it to find the money in its own systems. Stripe often shows the ARN on the refund in the Dashboard. If it's there, put it in your response. A refund date and amount are good. A refund date, amount, and ARN let the issuer confirm it themselves.

One trap matters here. Once a dispute is open on Stripe, you generally can't refund that charge, because the money is already held in the dispute. If you refund the customer some other way to “make it right” after the dispute opens, you can lose the money twice. Fight the dispute with your evidence, or accept it. Don't do both.

The return that never came back

The second case is harder and more personal. The customer says they sent the item back. You never got it, or what you got was used, damaged, or missing parts.

You need two documents:

  • The return conditions as you stated them. The actual policy text, plus any message where you told this customer how to return the item: address, timeframe, condition requirements, and whether a tracking number was needed.
  • What actually happened to the return. No tracking number given, a tracking number showing delivery to the wrong address, an intake note with photos of the condition the item arrived in, or the return arriving after your stated window.

This is where vague kindness hurts you most. If your last message said “just send it back and we'll sort it out,” you made an unconditional promise in writing, and the customer kept their side by mailing something. A message that said “please ship to this address with tracking within 30 days; refunds are issued once we inspect the item” makes a promise you can defend.

The refund that was never owed

Sometimes the customer asked for a refund, you said no, and they disputed anyway, describing your refusal as a broken promise. You win this by showing the policy was disclosed before purchase and that you applied it as written, for example offering store credit instead of cash if that's what the policy says.

The weak spot is any exception you made for someone else and documented loosely. Issuers look at what happened with this transaction, and a consistent policy is much easier to defend than one that depends on the support agent's mood that day.

The real lesson: write promises like you'll have to show them

This applies beyond chargebacks. People pleasers, conflict-avoiders, and most kind-hearted business owners say the soft version when things get tense. We'll take care of it. Don't worry. We'll make it right. It feels generous, and it is. It's also an open-ended commitment that the other person's memory will fill in however it likes.

The fix isn't being colder. It's being specific, and specific can still be warm: “I'm sorry this didn't work out. Here's exactly what happens next: once the item arrives back with us, I'll refund the full amount within two business days and email you the confirmation.” That message is kind and also hard to misremember. It's also something you can hand to a bank.

Your next moves

  • Rewrite your refund macro today. Open your support tool's saved replies and replace every “we'll take care of it” with a version that states the condition, the timeframe, and what the customer has to do. Five minutes now saves a dispute later.
  • Move every refund promise into writing. If a refund is agreed on a phone call or live chat that isn't saved, send a short follow-up email the same day summarizing exactly what was agreed. It becomes your evidence.
  • Find the ARN on your last three refunds. Open them in the Stripe Dashboard and see where the acquirer reference number appears. When a dispute arrives, you'll know where to look in seconds.
  • Send a refund confirmation email every time. Include the amount, date, last four digits of the card, and a line saying it may take several business days to appear. Many credit not processed disputes come from customers who never got that heads-up.
  • Log the condition of every return on arrival. One photo and a dated note when a package comes back is enough. Without it, “they sent it back damaged” is just your word against theirs.

Where Argeback fits

In a credit not processed dispute, the evidence is usually already in your Stripe account: the refund, its ARN, the policy, and the email where you stated your conditions. It's just scattered, and the response window is short, so it's easy to give up. Argeback ingests the dispute, pulls the relevant records together, and drafts a response built around the questions the issuer is actually asking. You can review and file it from your phone before the deadline. If you've lost one of these because you couldn't put the paperwork together in time, take a look at Argeback. Next time, your written record does the arguing for you.