The short answer
This question has two very different answers depending on who's asking for the refund and why — and conflating them is where most disputes start. If you cancel or substantially fail to deliver the event, Indian consumer law treats withholding a refund as a real problem, not a policy choice. If an attendee simply changes their mind about an event that's going ahead as planned, there's no blanket legal right to a refund — that part genuinely is yours to define.
If you cancel or postpone the event
Under the Consumer Protection Act, 2019, a cancelled event that a consumer already paid for is treated as a "deficiency" in service — a fault or shortcoming in what was promised. The Act's definition of unfair trade practice explicitly includes refusing to refund money for a service that was never delivered. In plain terms: if the event doesn't happen, "no refunds" as a blanket policy doesn't hold up. A 2022 Central Consumer Protection Authority notification on e-commerce unfair practices reinforces this specifically for platforms and ticket aggregators — refunds are expected within a reasonable, stated period when the underlying service isn't delivered.
Force majeure — genuinely unforeseeable circumstances outside your control — can excuse you from actually holding the event, but it doesn't erase the attendee's right to get their money back for something that never happened. Those are two separate questions.
If an attendee just changes their mind
This is the actual gray area that's genuinely within your control. If your event is going ahead as planned and someone simply no longer wants to attend, there's no law requiring you to refund them by default — that's exactly why every ticketing platform lets organizers set their own cancellation terms, and why "refunds are at the organizer's discretion" is standard, legitimate language, not a loophole.
That said, a policy that's technically legal but obviously unreasonable (e.g., zero refunds under any circumstance, with no cutoff communicated anywhere) tends to generate disputes, chargebacks, and reputational damage even when you're not strictly obligated — worth writing a policy you'd actually be comfortable enforcing publicly, not just one that's defensible on paper.
The postponement gray area
Postponing isn't the same as cancelling, and it doesn't automatically trigger a refund obligation — but it isn't a free pass either. The real test is whether attendees are still being offered substantially the same thing they paid for. A one-week postponement to the same venue with the same lineup is a different situation than a "postponement" that quietly becomes a different event, at a different time, that most of your original audience can no longer attend. The latter starts looking a lot more like a cancellation in substance, even if it's labeled a postponement.
Writing a policy that actually holds up
A few things make a refund policy both fairer and easier to defend if it's ever questioned:
- State it before checkout, not after someone asks — an undisclosed policy is much harder to enforce than one the buyer saw and accepted at purchase.
- Set a clear cutoff (e.g., no refunds within 24–48 hours of the event) rather than leaving it ambiguous case by case.
- Always refund for your own cancellations — this isn't optional, and trying to avoid it is the fastest way to end up in a dispute you'll lose.
- Process approved refunds promptly — a slow refund on a legitimate claim converts a minor inconvenience into a real complaint.
How SPION handles this mechanically
Your refund policy is yours to write and communicate on your event page — SPION doesn't impose one on you. What SPION does enforce is a hard floor: once your event has started, refund requests are blocked outright, and you can configure a cutoff window before that (24 hours by default) during which refund requests aren't accepted either. That gives you a consistent, automatically-enforced boundary, so you're not manually adjudicating refund requests as your event approaches — while the actual policy terms (what qualifies, how much is refunded) stay entirely under your control.
Set your refund policy once, enforced automatically
SPION blocks refund requests once your event has started, and applies whatever cutoff window you set before that — no manual policing required.
Create Your Event


