No Refund Policy and Chargebacks: What Merchants Need to Know

A no-refund policy is a merchant rule that denies money back on completed purchases, typically offering only store credit, exchange, or nothing at all. It does not exempt a business from card network dispute rules, and in several U.S. states an unposted no-refund policy is not enforceable at all.

Merchants often adopt strict no-refund terms to protect margin and cut down on abuse. In practice, the policy interacts with chargeback rules, consumer protection statutes, and dispute evidence in ways that frequently work against the merchant. This guide covers what a no-refund policy can and cannot do, where it creates legal and compliance exposure, and what to use instead if the real goal is fewer chargebacks rather than more of them.

What a No-Refund Policy Actually Covers

A no-refund policy is a statement, usually posted at checkout, on receipts, or in a website footer, that a business will not return money for completed purchases. It differs from a return policy, which governs whether a physical item can be sent back at all, and it differs from a chargeback, which is a forced reversal initiated by the cardholder's bank rather than by the merchant.

Merchants sometimes use "no refund policy" and "final sale" interchangeably, but they are not identical:

• No refund policy: the merchant will not issue money back, though an exchange or store credit may still be offered.
• Final sale: the item cannot be returned, exchanged, or refunded under any circumstance, usually reserved for clearance, custom, or perishable goods.
• No returns, refunds allowed: the merchant will not accept the physical item back but may still refund under specific conditions, such as a product defect.

None of these change how a cardholder's bank evaluates a dispute. Understanding the difference between a chargeback and a refund matters here: a refund is something the merchant controls, while a chargeback is a decision made by the card issuer, and it can happen regardless of what the merchant's posted policy says.

Why a No-Refund Policy Does Not Stop Chargebacks

The core misconception behind a no-refund policy is that it removes the merchant's obligation to return funds. It does not. Card network rules, not store policy, govern whether a cardholder can dispute a charge, and several common dispute reasons apply no matter what a merchant's refund policy says:

• The cardholder claims the transaction was unauthorized.
• The item never arrived or was materially not as described.
• The merchandise was defective or damaged.
• The cardholder does not recognize the charge on their statement.
• The cardholder contacted the merchant for a refund, was refused, and escalated to their bank instead.

In that last scenario, a strict no-refund policy is often the direct trigger for the dispute. When a customer cannot get money back through the merchant, the card issuer becomes the next and, from the customer's point of view, easier path. Nearly half of merchants surveyed in the Merchant Risk Council's 2024 Chargeback Field Report attributed 50% or more of their chargebacks to friendly fraud, and the same report notes that card networks estimate roughly 70% of fraud-coded disputes are actually this kind of cardholder-initiated dispute rather than true unauthorized use.

A no-refund policy does not just fail to prevent this pattern. By removing the merchant's ability to resolve the complaint directly, it increases the odds that a frustrated customer skips the merchant entirely and goes straight to their bank.

Legal and Compliance Risks of a Strict No-Refund Policy

Beyond the dispute itself, a no-refund policy carries risk that many merchants overlook.

State disclosure laws can override the policy entirely

Several states regulate how a no-refund or limited-refund policy must be communicated. California is the most cited example: under Civil Code Section 1723, a retailer that will not give a full refund, credit, or exchange within seven days of purchase must clearly post that policy at the register, at store entrances, on tags, or on order forms. If the retailer fails to post it, California law entitles the customer to return the item for a full refund within 30 days, regardless of what the merchant intended. Other states, including New York and Florida, have similar disclosure requirements with their own conditions and exceptions.

A rising dispute ratio can trigger network monitoring programs

Because a no-refund policy tends to push more disputes toward the bank instead of the merchant, it can also push a merchant's dispute ratio toward card network monitoring thresholds. As of April 2026, Visa's Acquirer Monitoring Program flags merchants as "excessive" once disputes and reported fraud reach 1.5% of card-not-present transactions, down from 2.2% previously. Mastercard's Excessive Chargeback Program uses similar logic, typically triggered around a 1% chargeback-to-transaction ratio and 150 or more chargebacks in a single month. Enrollment in either program means added per-dispute fees, closer scrutiny from the acquirer, and in repeated cases, a higher risk of losing card processing altogether. Merchants can review the current Visa and Mastercard chargeback thresholds to see exactly where their own ratio stands.

No-Refund Policy vs. Flexible Refund Policy: Chargeback Impact

The table below compares how each approach tends to play out once a customer is dissatisfied.

How a No-Refund Policy Weakens Your Position in a Chargeback Dispute

Even when a merchant fights a chargeback through representment, a strict no-refund policy can work against the case rather than for it.

• Issuers read a blanket refusal as bad faith. A policy that offers zero recourse, even for defective goods or merchant errors, can look punitive rather than reasonable when an issuer reviews the case.
• It undercuts "resolution offered" evidence. Winning representment often depends on showing that the merchant tried to resolve the issue before the dispute was filed. A no-refund policy makes that evidence harder to produce, because there was no offer to point to.
• It does not override reason-code rules. Reason codes for items not received, not as described, or unauthorized use are evaluated on the facts of the transaction, not on the merchant's refund terms.
• It can conflict with required policy disclosure. If a no-refund policy was not clearly presented to the cardholder before purchase, some issuers treat that as grounds to side with the customer regardless of the outcome the merchant wanted.

In short, a no-refund policy does not give a merchant a better argument in a dispute. It removes one of the strongest arguments available: proof that the merchant offered a fair resolution first.

Better Alternatives to a No-Refund Policy

Merchants who want to protect margin without inviting more disputes generally do better with a policy that is strict but not absolute:

• Offer store credit or an exchange instead of a blanket refusal, so there is still a resolution path that does not require a dispute.
• Set a defined return window and condition requirements rather than a flat "no returns" rule.
• Reserve true no-refund, final-sale terms for a narrow set of categories, such as personalized, perishable, or clearance items, rather than the entire catalog.
• Disclose the policy clearly at checkout, on the product page, and on the receipt, not just buried in a terms page.
• Respond to refund requests quickly, since slow responses are one of the most common reasons a customer escalates to their bank instead of waiting.

Chargeflow has a full walkthrough of how to write an ecommerce return policy from scratch, and a separate guide covering five ways to improve your return policy if one is already in place but still generating disputes. Shopify merchants specifically can start from Chargeflow's Shopify refund policy template rather than building one from a blank page. Sellers on creator marketplaces like Whop face the same tradeoff — see how a clear policy helps cut Whop chargebacks.

One risk worth planning for either way: even a well-run refund process does not guarantee immunity from disputes. Chargeflow's guide on getting a chargeback after issuing a refund covers what to do when a customer disputes a transaction that was already refunded.

If You're a Shopper Facing a No-Refund Policy

This guide is written for merchants, but the question comes up from shoppers too: if a business posts a strict no-refund policy, does that mean there is truly no way to get money back?

Not always. Depending on the state, a retailer that does not clearly post its refund policy may be legally required to accept a return anyway, as under California's Civil Code 1723. If a purchase was never delivered, arrived damaged, or was billed incorrectly, a cardholder generally retains the right to dispute the charge with their card issuer regardless of the merchant's stated policy. That said, banks increasingly scrutinize disputes filed simply because a customer changed their mind, since cardholder-initiated disputes of that kind are a major driver of overall dispute costs, so filing a dispute is not a substitute for reading the return terms before buying.

Foire aux questions

Does a no-refund policy stop customers from filing a chargeback?

No. A no-refund policy is the merchant's own store rule, but a chargeback is filed with the card issuer, which evaluates the dispute against card network rules rather than the merchant's posted terms. A cardholder can still dispute an unauthorized charge, an item that never arrived, or merchandise that was defective, regardless of what the refund policy says.

Is a no-refund policy even legal?

In most of the United States, yes, a merchant can generally choose not to offer refunds. However, several states require that policy to be clearly disclosed to the customer before purchase. California's Civil Code 1723, for example, requires the policy to be posted at the point of sale; if it is not, the customer is entitled to a full refund within 30 days by law.

Does refusing refunds increase chargeback rates?

In practice, yes. When customers have no direct path to get money back from the merchant, a portion of them contact their card issuer instead. This shifts what would have been a simple refund into a formal chargeback, which is more costly and carries dispute-ratio risk that a straightforward refund does not.

What should replace a no-refund policy if a merchant wants to limit refunds?

A defined return window, clearly disclosed conditions, and options like store credit or exchange tend to reduce disputes far more effectively than a blanket refusal. Reserving strict no-refund terms for a narrow set of product categories, rather than an entire catalog, keeps most of the cost protection while removing the biggest driver of avoidable chargebacks.

Can a no-refund policy help win a chargeback dispute?

Not directly. Representment cases are decided on reason codes and evidence, not on the merchant's refund terms. In practice, having offered a refund or resolution before the dispute was filed is one of the stronger pieces of evidence a merchant can present, and a no-refund policy removes that option before the case even starts.

What Merchants Should Do With This

A no-refund policy is not the shortcut it appears to be. It does not exempt a business from chargeback rules, it can be legally unenforceable if not disclosed correctly, and it tends to push disputes toward the bank instead of resolving them directly, which raises dispute ratios and monitoring risk rather than lowering them.

The stronger position is a policy that is deliberately narrow rather than absolute, disclosed clearly at every touchpoint, and backed by a fast response process, so customers have a reason to come to the merchant before they go to their bank. Chargeflow helps merchants handle the disputes that happen anyway, automating evidence collection and submission for chargebacks so a strict refund stance does not have to be the only line of defense.