Refunds, Cancellations, Chargebacks and Reserves: An Organizer Guide
A practical organizer workflow for event changes, ticket refunds, card disputes, payout holds and settlement reconciliation.
When an event changes, decide whether it is cancelled or postponed; update sales, notify buyers, preserve refund cash and check who controls each payment. A refund returns money through the payment channel; a card dispute starts with the cardholder's issuer. Neither changing event status nor invalidating a ticket necessarily returns money. Record the decision, communication, payment and ticket validity per order.
Scope: desk research, not a universal policy
This guide uses Eventbrite organizer help, Stripe documentation, and Ticket Tailor help. It is desk research, not hands-on testing or a contract review. Procedures differ by country, payment method and account. Consumer law, card rules and vendor agreements can impose different obligations; seek jurisdiction-specific advice when needed.
Four different events in your records
- Cancellation: The original event will not go ahead. Stop sales, set the correct event status, tell buyers what happens next and identify refunds owed. On Eventbrite, its cancellation instructions call for changing status, emailing attendees and refunding orders; its own policies apply to events on that platform, not every ticketing system.
- Postponement or rescheduling: The original date will not happen, but an event is expected later. A postponement without a date is different from a confirmed new date. Communicate what is known, when the next update is due and how attendees request a refund. Eventbrite's postponement policy defines its own timelines and describes holding event payouts; do not generalize those timelines to other contracts.
- Refund: Some or all of an original payment is returned. A full refund might invalidate an admission; a partial price adjustment might leave it valid. The amount returned, fees included, and ticket state are separate fields to verify. Eventbrite's order instructions say a fully refunded ticket becomes invalid but a partially refunded ticket remains valid on its system.
- Card dispute or chargeback: A buyer challenges a charge with their card issuer, which may debit funds while reviewing the claim. The bank, not the organizer, decides the outcome. A posted “no refunds” policy does not prevent a dispute; see Eventbrite's chargeback explanation. Investigate before separately issuing a refund on the same payment.
Do not assume a new date means the attendee has agreed to attend. Request and record confirmation where required, explain the refund route, and check old barcodes, transferred seats and unanswered messages. A changed listing alone is not effective notice.
Who has the money, and which fee is which?
Map the payment path before announcing refund dates. The vendor may hold funds as merchant of record, or your organization may receive sales into its connected processor account. Ask who receives the charge, authorizes returns, answers disputes and absorbs a negative balance.
For example, Eventbrite says it manages chargebacks as merchant of record when Eventbrite Payment Processing is used. Ticket Tailor describes sales paid directly into an organizer's connected Stripe account; it also supports other processors. These are illustrative configurations, not universal claims. Compare the payment paths of Eventbrite and Ticket Tailor on the same questions.
Separate platform or ticketing fees from payment-processing fees, taxes on fees, and any dispute charges. Ask for the net-buyer and net-organizer effect of an ordinary voluntary refund, a cancelled event, a postponed event and a duplicate charge. Eventbrite's published Ticketing Fee article distinguishes ordinary refunded tickets from cancelled or postponed events, when it says the entire purchase including Ticketing Fees is refunded. Stripe says original processing fees are not returned on refunds. Neither document is a substitute for your account's current terms; never assume every buyer gets every fee back or every organizer retains it.
Run refunds without losing ticket control
For every request, identify the original order and payment, quantity, payer, ticket holders, event status, prior adjustments and any active dispute. Confirm whether a group booking needs one ticket refunded, a percentage of the order refunded, or the whole order cancelled. Calculate the buyer amount and fee treatment before clicking confirm; obtain approval for exceptions. Keep a durable record of who approved the decision and the processor refund ID.
A partial monetary refund and a partial cancellation are not interchangeable. Eventbrite documents full and partial order refunds, while Ticket Tailor's single-ticket instructions call out a “Void items” choice. Check whether the refunded barcode becomes unusable, inventory returns to sale and companion tickets remain valid. For bundles, seats and add-ons, confirm how discounts are recalculated.
Use the ticketing workflow so admission and finance reporting stay aligned. Ticket Tailor warns that cancelling an order does not automatically return money, and refunds made directly in a processor do not update its tickets or revenue dashboard. Offline payments require a separate return of funds. Reconcile external refunds and void tickets where appropriate.
Before promising a refund, check the available balance, not merely gross tickets sold. Stripe's refund docs say card refunds can remain pending when the available Stripe balance is insufficient, while refunds for other payment method types can fail; pending funds are not available balance. Eventbrite's refund guide directs organizers whose event sales cannot cover a refund after payout to add funds or use its applicable alternative. Follow the actual account workflow and confirm completion status; a submitted or pending refund is not money received by the buyer. Keep enough working capital for returns even after deposits have reached your bank.
Communicate early, precisely and in writing
Use one owner and a public update schedule. Send notices through the platform's attendee channel where available, and retain copies. These are adaptable examples, not legal notices:
- Cancellation: “The [event] scheduled for [date] is cancelled. We have stopped sales. We will process eligible refunds through [original payment channel or named process], including the applicable fee treatment for your order. You do not need to buy another ticket. We will update you by [date]; contact [address] with your order reference.”
- Postponement: “The [event] will not take place on [date]. We expect to confirm a new date by [date]. Your ticket status is [specific status]. To request a refund or discuss the new date, use [link/contact] by [relevant date, if one applies]. We will not treat silence as acceptance where consent is required.”
- Refund progress: “Your order [reference] has a [full/partial] refund of [amount and currency] [submitted/completed] through [payment provider] on [date]. [Named tickets] are [valid/void]. The time to see the credit depends on the payment provider and issuing bank. Contact [address] if the credit has not appeared after the provider's stated window.”
Avoid an unqualified “refunds are automatic” message. If the processor rejects a refund, the original card is unavailable, or a voucher is offered, explain the options without representing a voucher as cash. Give customer support enough information to answer a group's different outcomes consistently.
Respond to disputes, then plan for reserves
Monitor the payment inbox and dispute dashboard during a cancellation. Record the issuer reason, amount, response deadline and owner. Stripe's response documentation calls for evidence suited to the dispute type; a submitted response cannot simply be amended, and the issuing bank decides. Gather checkout receipt, purchase policy, payment IDs, attendee messages, event-change notice and acceptance, refund status and relevant scan records. Remove irrelevant personal information; follow the provider's format, not just an external link. Evidence cannot guarantee a win. If a refund is due, discuss accepting the dispute or resolving it through the provider.
A reserve or holdback is money not yet available to spend, separate from a fee and separate from a refund. Stripe's balances documentation explains that an account can have a reserve balance to cover expected incoming refunds or disputes. Eventbrite's postponement policy describes a payout hold in that specific circumstance. The percentage, release conditions, payout timing and recourse depend on the account, risk assessment and contract; do not budget on an advertised “instant” payout without confirming eligibility and holds. Ask finance to model a hypothetical cancellation of your largest event: gross paid orders, taxes/fees, money already deposited, refunds still pending, chargeback debits, available balance, and liquidity needed for venue or supplier obligations. This is a stress-test scenario, not a claim about likely losses.
Operational checklist and settlement close
1. Freeze or amend listings and scan rules; assign an incident owner and a second approver for material refunds.
2. Export orders, payment IDs, ticket IDs, buyer contacts, original event terms, payout ledger and communications before changes.
3. Classify each order: keep for new date with recorded response, refund in full, refund in part, voucher if permitted and chosen, or unresolved dispute.
4. Check processor balance, method restrictions, tax and fee treatment, and the funding source for all promised refunds; escalate insufficient funds before promising a completion date.
5. Issue and track returns in the right system; verify the buyer-facing status and invalidate only the tickets that should no longer admit.
6. Log disputes by issuer deadline and evidence owner; preserve relevant checkout and communication records without over-sharing.
7. Reconcile per order: gross charge minus platform/processing fees, refunds, dispute debits or reversals, adjustments, tax and net payout. Match processor transaction IDs to platform exports and bank deposits; isolate timing differences, pending returns and external payments instead of forcing totals to agree.
8. Review held funds and reserve release terms with the payment provider; record who funds a shortfall and report unresolved differences to finance.
For operations with multiple venues, the box-office guide discusses permission and consolidated reporting checks. If admissions span dates or capacity slots, see the timed-entry guide. Neither replaces an account-level payment review.
Frequently asked questions
Does cancelling the listing refund every buyer?
No. Follow the platform's cancellation and payment-return steps, then confirm each refund status and ticket state. Eventbrite's cancel-event instructions list email and refunds separately; Ticket Tailor says cancelling an order is not automatically a payment refund.
Can we refund one person in a group and keep the others' tickets?
Potentially, but check order-level discounts, fees and seat assignments. Use a per-ticket cancellation when the admission must be void, not just an order-level price reduction. Verify the remaining barcodes before the doors open.
Can a buyer dispute a nonrefundable ticket?
Yes. The issuer may accept a cardholder's claim for review regardless of your policy. Respond according to the dispute reason and deadline; clear purchase terms and written buyer consent may help explain the transaction, but cannot ensure the bank decides in your favor.
Are payout holds the same as lost revenue?
No. A hold or reserve changes access to funds and can create immediate cash-flow pressure; a fee or finally lost dispute changes the amount retained. Ask for the account's actual release conditions and reconcile later payouts rather than counting a withheld amount as both income and cash.
Which policy governs a postponement?
Check local consumer law, the terms buyers accepted, card rules and your payment/ticketing contracts together. Eventbrite's published postponement rules are specific to its service. This guide is operational information, not legal advice.