Someone buys a ticket on Monday, sends you a message on Thursday asking for their money back, and now you need to decide. You could return the full amount and hope they understand you have already paid the venue deposit. You could say no and risk a public complaint. Or you could have written three sentences a week ago that would have made this conversation unnecessary.
Most event organisers never write down their refund rules until the first dispute arrives. By then it is too late to be fair to everyone. The person asking for a refund will feel singled out if you invent a rule on the spot, and you will spend an hour drafting replies when you should be preparing the event itself.
Decide what you can afford before you sell the first ticket
A refund policy is not about being generous or strict. It is about knowing your costs and your calendar. If you book a room two months in advance and pay a deposit, you cannot afford full refunds the day before the event. If you run a monthly meetup in a bar with no fixed costs, you can be more flexible.
Write down the deadline. "Full refund until seven days before the event" is clear. "Refunds at our discretion" is not. Pick a number of days that gives you time to adjust catering, print fewer name badges or release the ticket to someone on a waiting list. For most small events, seven to fourteen days works. For large conferences with printed materials, thirty days makes more sense.
Decide whether you will offer partial refunds after that cutoff. Some organisers return half the ticket price up to two days before the event, keeping enough to cover their fixed costs. Others draw a hard line and keep the full amount once the deadline passes. Both approaches are fair if you explain them in advance.
Write it in plain language and put it where people look
Your refund policy should take up three or four short sentences, not three paragraphs of legal boilerplate. Ticket buyers will not read a wall of text, and you do not need one. State the deadline, the method and any exceptions.
"Full refund until 14 days before the event. After that, no refunds. Contact us by email with your payment transaction ID." That covers what most people need to know.
Put the policy on the ticket page, just below the ticket types or next to the payment instructions. If you only mention it in a confirmation email, half your buyers will miss it. If you bury it in a terms-of-service document, everyone will miss it.
When you sell tickets on Anyza Events, you can add your refund policy to the event description so it appears before anyone pays. Because buyers send payment directly to your wallet, you handle refunds yourself—which means you also control the timeline and the exceptions.
Crypto payments and refunds work differently from card processors
With a credit card, the buyer can dispute the charge and the card company may reverse it without asking you. With bitcoin or stablecoin payments, the transaction is final. Once the buyer sends you the money, only you can send it back. That puts you in full control, but it also means your refund policy is the only protection the buyer has.
This is why clarity matters more than it would with a traditional ticketing platform. You cannot point to a third party and say they will handle disputes. You are the policy. If someone asks for a refund and you have not written down your rules, the conversation will be longer and less pleasant than it needs to be.
When you do issue a refund, ask for the wallet address and double-check it before you send anything. The same care you take with incoming payments applies in reverse. Send a message confirming the refund once it is done, and keep a record of the transaction.
What to do about no-shows and last-minute cancellations
Some ticket buyers will vanish without asking for a refund. They simply will not turn up, and you will never hear from them. Your policy does not need to address this—those tickets are sold, and the money stays with you.
The harder case is the person who messages you two hours before the event, apologising and asking for their money back. If your cutoff was a week ago, the answer is no. You have already spent the money or committed to costs based on the headcount. A well-written policy means you can reply in one sentence and move on.
If you want to be flexible, consider offering a credit toward a future event instead of a cash refund. This works well for recurring meetups or organisers who run several events a year. The buyer does not lose everything, and you do not lose revenue. Just make sure the credit has an expiry date, or you will be tracking promises a year from now.
Test your policy with the first few events
The best refund policy is the one you can actually follow. If you write "full refund until two days before" and then panic when three people cancel and you have already ordered food for twenty, your policy was too loose. If you write "no refunds ever" and then feel uncomfortable saying no to someone whose flight was cancelled, your policy was too strict.
Run a few events, see what people ask for, notice where your costs lock in. Adjust the deadline or the refund percentage based on what you learn. You are allowed to change the policy between events—just not after someone has already bought a ticket under the old rules.
Once you have a version that feels fair and sustainable, stick to it. Consistency is more valuable than perfection. Ticket buyers will trust you more if they see the same clear terms every time, and you will spend less time negotiating.
Write your refund policy this week, even if your next event is two months away. Put it on the page, test it with the first round of ticket sales, and adjust it once you know your real costs. The hour you spend now will save you a dozen awkward conversations later.
Comments