Somewhere in the first year of selling a course, almost every creator gets a refund request that feels unfair, a student who watched every lesson, downloaded every worksheet, and then asked for their money back on day twenty nine of a thirty day window, and the instinct in that moment is usually to wonder what you're actually obligated to do versus what you've simply decided to offer. Those are two different things, and the confusion between them is where most refund disputes actually come from. Consumer protection law sets a floor for what a buyer is owed under certain circumstances, your own written policy sets whatever ceiling you're comfortable offering above that floor, and the gap between the two is where you have real decisions to make as a business owner, rather than just following a rulebook someone else wrote for a completely different kind of product.
The floor versus the ceiling, and why the distinction matters
Digital products occupy a slightly different space than physical goods when it comes to consumer protection, because once someone's accessed the content, the "return" concept that works cleanly for a t shirt doesn't map onto a course video that's already been watched in full. General consumer law in India does provide protections around unfair trade practices, misleading claims and deficient service, but the specifics of what applies to a self paced digital course versus a live cohort versus a certification program vary enough that stating exact rules here would do more harm than good. What matters practically is that your own refund policy should sit comfortably above whatever the legal floor is, not right up against it, because a policy that only just clears the legal minimum tends to generate exactly the kind of disputes that end up costing more in time and reputation than the refund itself would ever have cost you.
Where creators usually get it backwards
The most common mistake isn't offering too generous a refund policy, it's writing one that sounds generous but is actually vague, something like "refunds available within a reasonable time if you're not satisfied," which sounds friendly right up until two different students interpret "reasonable" two different ways and you're left mediating rather than just pointing to a clear rule that settles it on its own. A policy that says access must be under a specific percentage watched, requested within a specific number of days, submitted through a specific channel, is far easier to apply consistently, and consistency is what actually builds trust, because students talk to each other, especially inside a community space, and a policy applied unevenly spreads faster through word of mouth than almost anything else you do as a creator.
There's a second, quieter mistake that shows up once a business has been running a while, which is letting the policy drift from what's actually being enforced day to day. A creator might have a written thirty day window but, in practice, has been quietly honoring requests at day forty five because saying no felt awkward, and that gap between the written rule and the actual behavior eventually gets discovered by a student who compares notes with someone else in the community, at which point the written policy stops meaning anything and every future request becomes a negotiation instead of a lookup. The fix isn't necessarily to become stricter, it's to decide, once, what you're actually comfortable honoring, write that down as the real policy, and then apply it evenly rather than letting each request get decided fresh based on how the conversation happens to go that particular day. A common shape for this in practice is a thirty day window paired with a rule that access has to stay under roughly a fifth of the course watched, which is generous enough to feel fair to a genuinely unhappy student while still being specific enough that nobody has to guess where the line actually sits.
How the platform you sell on shapes this too
Where you actually sell the course changes how much of this you have to manage by hand, because a platform that processes the refund back through the original Razorpay or Stripe transaction, updates the student's access automatically, and keeps a clean record of when the request came in relative to the purchase date removes most of the manual bookkeeping that turns a simple policy into a genuinely messy process. Creators piecing together a course business across a generic payment link and a separate content host often end up processing refunds by hand, revoking access by hand, and hoping they remembered to update a spreadsheet somewhere, which is exactly the kind of friction that makes a business owner start bending the written rule just to avoid the hassle of following it properly. None of this changes what you're required to offer under consumer protection principles, but it changes how consistently you're actually able to honor your own stated policy, and consistency, more than generosity, is usually what students remember.
Cohorts, live components and the deposit question
Refund logic gets more complicated the moment a course involves live elements, because a cohort based program has real costs attached to enrolment that a purely self paced course doesn't, coaching calls get scheduled, group sizes get capped, and a seat that goes unused because someone dropped out on day two often can't simply be resold to fill the gap. Many creators handle this by treating a portion of the cohort price as a non refundable deposit once a waitlist converts into a paying seat, which is a legitimate business decision as long as it's disclosed clearly before purchase rather than discovered afterward when a student is already asking for their money back. The same logic extends to payment plans, where a student who's paid one of four installments and then wants a refund raises a slightly different question than someone who paid the full price up front, and it's worth deciding your answer to that before the first request comes in rather than while you're in the middle of it.
Writing a policy that actually reduces disputes
The most useful refund policies read less like a legal disclaimer and more like an FAQ a student could genuinely find helpful, stating the window in days, the access threshold if there is one, exactly how to request it, and how long a checkout refund typically takes to process back through Razorpay or Stripe. Publishing this on its own page, linked from checkout rather than buried in a terms of service document nobody reads before buying, does more to prevent disputes than any clever legal phrasing ever could, because most refund requests that turn ugly do so not because the student is being unreasonable, but because they genuinely didn't know the rule existed until they'd already broken it without meaning to.
The law tells you what you can't get away with, your own policy tells students what to actually expect, and a course business that keeps those two things clearly separated, rather than treating "legally allowed" and "what I'll actually offer" as the same question, ends up spending far less time arguing about refunds and far more time just running the business it set out to build. That separation, once you've actually made it, tends to be the thing that lets you offer a policy generous enough to build trust without ever wondering, mid dispute, whether you're giving away more than you're required to.