Refund Policy for Event and Ticket Sales

A “tickets are non-refundable” line does most of the work most refund policies for event sales ever attempt, and that is the problem. It answers the question a customer who changed their mind is asking, and it says nothing about the question that actually generates support tickets and chargebacks: what happens when the event itself does not happen the way it was sold. A concert gets canceled outright. A conference gets pushed back six months. A ticket holder simply does not show up. Those are three different situations, and a policy that treats all three as “no refunds” is not just unhelpful, in some of them it is unenforceable.

Why “non-refundable” has to be disclosed, not just written

The first thing a ticket refund policy has to get right has nothing to do with cancellations at all: whether the no-refund terms were shown to the buyer before they paid, not just published somewhere on the site afterward. Ticket sales draw more regulatory attention to this point than most other purchases, because live-event tickets are a category where states have specifically legislated disclosure, on top of the general consumer-protection rules that already apply to every online sale.

The clearest federal example is the Federal Trade Commission’s rule on unfair or deceptive fees for live-event tickets, which took effect in 2025. It requires sellers to show the total price, including mandatory service and processing fees, up front, rather than adding them at checkout after a customer has already committed to a lower advertised price. It is a pricing-transparency rule rather than a refund rule, but it belongs in the same conversation, because both rules share the same underlying principle: a buyer has to see the real terms of the sale before they pay, not discover them afterward. A refund policy is part of that same up-front disclosure. If your no-refund terms only appear on a policy page a customer would have to go looking for, and not on the page where they actually enter payment details, you are relying on the same kind of after-the-fact disclosure the fee rule was written to stop.

Several states go further and regulate ticket sales specifically. New York’s ticket-sales law is one of the more detailed examples, requiring sellers to conspicuously disclose their refund terms before the sale and, separately, to guarantee a refund if a performance is canceled outright and not rescheduled. Other states impose similar disclosure obligations without necessarily using the word “ticket” in the statute, folding it into general consumer-protection or unfair-trade-practices law instead. None of this adds up to one uniform national rule, and if you sell tickets into more than one state, checking your specific states’ requirements is worth doing rather than assuming your general terms of service already cover it. What is consistent across all of them is the underlying expectation: state the refund terms clearly, and state them before the purchase, not after.

The three situations your policy actually needs

Once disclosure is handled, the substance of the policy comes down to distinguishing three outcomes, because the money owed genuinely differs between them.

An event that is canceled outright, with no new date announced, is the organizer failing to deliver what was sold. That is not the same legal situation as a customer who simply changes their mind, and most state consumer-protection frameworks, along with the card network rules behind every credit card payment, treat it that way: a seller who takes payment for a service and then never provides it is generally expected to return the money, regardless of what the ticket’s fine print says about final sales. Visa and Mastercard’s own chargeback rules reflect this in practice. A cardholder disputing a charge for an event that was canceled and never refunded is disputing “services not provided,” a category card networks resolve in the cardholder’s favor often enough that a “no refunds, no exceptions” policy applied to outright cancellations tends to lose money in chargebacks and fees even when it holds up on paper.

Postponement is the middle case, and it is where a policy needs the most specific language, because reasonable businesses handle it differently. The ticket itself usually stays valid for the new date, which is not a refund at all, just a rescheduled service. Some organizers stop there. Others also offer a refund window for ticket holders who genuinely cannot attend the new date, since a date change several months out can turn a valid ticket into one nobody can use. Neither approach is required by default the way an outright cancellation refund often is, so your policy should say explicitly which one you offer, and by what deadline a refund request has to come in if you do offer one.

A no-show is the one case where “non-refundable” is exactly the right answer, and the easiest one to defend. The event happened as sold, the ticket was valid, and the holder chose not to use it. This is functionally the same as any other service a customer paid for and declined to use, a gym membership visit, a reserved restaurant table, and the general rule that applies to unused-but-available services applies here too: no failure to perform occurred, so no refund is owed by default.

Writing it so the difference actually shows up

The gap between a policy that works and one that generates disputes is usually just specificity. A single blanket sentence forces every one of these three situations through the same rule, which is either too generous for a no-show or too strict for a cancellation.

A few details are worth locking down alongside those three core rules. State the refund method, back to the original card, store credit, or a choice between the two, since “you’ll get a refund” without a method invites a support conversation on its own. State a concrete timeline for processing a cancellation refund, since a canceled event with an open-ended “refunds will be issued” line is exactly the situation most likely to end up as a chargeback if it drags on. And if you sell through a resale marketplace or a secondary ticketing partner rather than only direct, note that the refund terms for tickets bought through that channel may be set by the marketplace, not by you, so your own policy should be clear about which sales it actually governs.

Building the policy

A refund policy for ticketed events needs to do more than a generic ecommerce return policy, because “the product” here is an experience with a fixed date, not a physical item that can simply be shipped back. Get the disclosure right by putting your refund terms where a buyer sees them before paying, and get the substance right by writing a separate, specific rule for cancellation, postponement, and no-show rather than one line meant to cover all three. Our Refund Policy generator builds each of those sections from a short set of questions about how your events are sold, so the cancellation, postponement, and no-show language stays distinct instead of collapsing into one “final sale” sentence that answers the wrong question for two out of three cases.

For the general vocabulary difference between a refund policy and a return policy, see Refund Policy vs Return Policy. For a statutory cancellation right that applies to some in-person contract sales regardless of what your policy says, see State Cooling-Off Period Laws and Your Refund Policy.