A refund and a chargeback both end with money moving back to the customer, and that similarity is exactly why the two get used interchangeably in casual conversation. They are not the same event. A refund is something a merchant chooses to give, on terms the merchant set, through a process the merchant controls from start to finish. A chargeback is something a customer's bank grants, on terms the card network set, through a process the merchant only gets to participate in after the fact, as the party being investigated. Confusing the two, or writing a refund policy that quietly assumes the difference doesn't matter, is one of the more common ways a business ends up with more chargebacks than it needs to have.
What a refund actually is
A refund is a direct transaction between a merchant and a customer. The customer asks, the merchant evaluates the request against its own stated policy, and if it qualifies, the merchant initiates the return of funds through its payment processor. The merchant decides whether the request meets the conditions (a return window, an unworn item, a valid reason for a subscription cancellation), decides how the money comes back (original payment method, store credit, partial versus full), and decides how long the process takes. Nothing about a refund requires an outside party's approval. It is, in the fullest sense, a customer-service and business-policy decision that lives entirely inside the merchant's own systems.
That control cuts both ways. Because the merchant owns the decision, the merchant also owns the customer's experience of asking for one. A refund policy that is easy to find, states a clear timeframe, and processes quickly reads as evidence of a business standing behind what it sells. A policy that is vague, hidden three clicks deep, or contradicted by what a support agent tells a customer on the phone reads as evidence of the opposite, and it pushes exactly the customers a merchant most wants to keep toward the second, much less merchant-friendly option below.
What a chargeback actually is
A chargeback is a dispute the customer files with their card-issuing bank, not with the merchant. The customer calls or opens a dispute through their bank's app, cites a reason (the item never arrived, it wasn't as described, it was an unauthorized charge, or simply that they didn't recognize the transaction), and the bank provisionally reverses the charge, often before the merchant is even notified that anything happened. The merchant then has a fixed, usually short window, set by the card network's own rules, not by the merchant's policy, to submit evidence and contest it. A card network arbitrates the outcome, not the merchant and not, in most cases, the customer's continued cooperation.
Three things separate a chargeback from a refund in practice, and they are worth naming explicitly because each one changes what a merchant can actually do about it:
The bank, not the merchant, makes the final call on whether the money goes back, based on evidence the merchant submits after the fact rather than a policy the merchant set in advance. The dispute almost always carries a chargeback fee, typically in the fifteen-to-twenty-five-dollar range charged by the payment processor regardless of who ultimately wins, on top of the disputed amount itself, so a merchant that successfully fights and wins a chargeback still often ends up out the fee. And a pattern of chargebacks, tracked as a ratio against total transaction volume, is itself a risk signal that payment processors monitor: cross a threshold (commonly cited around 0.9 to 1 percent of transactions, varying by network and processor) and a merchant can face increased reserve requirements, higher processing fees, or in serious cases the loss of card processing privileges entirely. A single refund never does any of that. A chargeback problem, left unaddressed, can.
Refund vs Chargeback
| Refund | Chargeback | |
|---|---|---|
| Who decides | The merchant, against its own policy | The bank, against card network rules |
| Who initiates it | Customer requests it from the merchant | Customer disputes it with their bank |
| Merchant's role | Approves or denies the request | Submits evidence after the fact |
| Typical cost to merchant | The refunded amount only | Disputed amount plus a chargeback fee |
| Effect on merchant standing | None | Counts toward the chargeback ratio |
| Where it happens | Merchant's own systems | The customer's bank and the card network |
Why a weak refund policy produces more chargebacks
A chargeback almost never starts as a chargeback. It starts as a customer who wants their money back and has to decide how to go about getting it. When a merchant's own refund path is clear, fast, and easy to find, most customers use it, because it's less friction than disputing a charge with their bank and waiting out an investigation. When it isn't, a meaningful share of those same customers skip the merchant entirely and go straight to their bank instead, not necessarily out of hostility, but because the bank's dispute process looks more predictable than a merchant's refund policy that gives them no confidence about what happens next.
Every branch on the left side of that flow that ends in a chargeback is a branch a specific, accessible, promptly-honored refund policy can close off. That's also the actual mechanism behind a claim that surprises people the first time they hear it: refund policies that look more generous on paper, a longer window or a no-questions-asked return, often produce fewer disputes than stricter ones, because the customer never has a reason to route around the merchant in the first place. A related pattern shows up across the refund policy pages that measurably reduce chargebacks: the common thread isn't generosity for its own sake, it's that the customer never has to guess what happens next.
What to change in your policy
The fix isn't a longer policy. It's a more specific one, in the places customers actually check before deciding whether to trust the merchant with a return request or take it straight to their bank instead.
- Refunds are handled on a case-by-case basis.
- Please contact us if you are unsatisfied with your purchase.
- Processing times vary.
- Refund requests within 30 days of purchase are approved automatically if the item is unused.
- Approved refunds are issued to the original payment method within 5 business days.
- Start a return from your account under Orders, no email required.
The specific version on the right does two things the vague version doesn't. It removes the ambiguity that makes a customer nervous enough to call their bank instead of the merchant, and it gives a merchant something concrete to point to if a chargeback is filed anyway, since card networks weigh a merchant's stated, consistently-applied policy as part of the dispute evidence. A policy that says "case-by-case" gives a merchant nothing to submit when contesting a dispute; a policy with a stated window, a stated condition, and a stated processing time does.
Beyond the wording itself, three specific inclusions do the most work against chargebacks: a named timeframe rather than an open-ended one, so a customer never has to guess whether they've missed their window; a named refund method (original payment method versus store credit) stated before the customer commits to a return, since a customer who is surprised by store credit when they expected cash back is a customer who is more likely to dispute the original charge instead; and a self-service way to start a return, since a policy that technically allows refunds but routes every request through an email ticket with no stated response time creates exactly the kind of uncertainty that sends people to their bank. Subscription businesses carry an extra wrinkle here, since a mid-cycle cancellation raises the proration question our subscription refund policy guide walks through in more detail, and getting that question answered clearly in the policy text closes off one more common route to a dispute.
None of this eliminates chargebacks entirely. Some will always be outright fraud, unrelated to how good the refund policy reads, and no policy language changes that. But the share of chargebacks that start as an ordinary, honest refund request, the customer who couldn't find a clear answer and defaulted to calling their bank, is the share a specific, accessible, promptly-honored policy can actually move. Our Refund Policy Generator builds that specificity in by default: a stated timeframe, a stated refund method, and a stated process, rather than the case-by-case language that gives a merchant nothing to stand on when a dispute does show up.
The information in this article is for informational purposes only and should not be construed as legal advice on any matter, and does not create a lawyer-client relationship.
