How to Handle Event Ticket Refunds and Chargebacks Without Losing the Margin (Canada, 2026)

Refunds and chargebacks are the two ways ticket revenue leaves after it arrives, and they cost different amounts. A refund you issue costs the processing fee on the original charge, which Stripe does not return (2.9% + CA$0.30 on a domestic card in Canada as of September 2026), plus the staff time. A chargeback you lose costs the ticket, the processing fee, a CA$15 dispute fee on Stripe and, if you contested it manually, a second CA$15; Square charges no dispute fee but holds the disputed funds while the bank decides. Because a refund is always cheaper than a dispute, the whole discipline of handling event ticket refunds and chargebacks comes down to one rule: make the refund path so clear and so fast that nobody calls their bank instead. This guide, part of the How to Run Profitable Events series, covers the policy, the workflow, cancellations, the dispute process and the evidence that wins it. It is general guidance for Canadian organizers, not legal advice; consumer protection rules vary by province.

Key takeaways

• A refund costs you the processing fee (not returned by Stripe on standard pricing) and nothing else; a lost chargeback costs the ticket, the fee, CA$15 on Stripe and your time. Refund fast and dispute rarely.
• Card network rules give cardholders months to dispute a charge, and for a ticket the clock can run from the event date, so disputes arrive long after the sale. Keep the evidence for every order until the window closes.
• The evidence that wins a ticket dispute is boring and specific: the confirmation email, the terms and refund policy the buyer accepted with a timestamp, the ticket delivery record and, best of all, the scan at the gate.
• When an event is cancelled, refund everyone before they ask. Disputes on cancelled events are lost almost automatically, and the processor keeps the original fee either way.
• Ticket transfers, credits and a waitlist that resells returned tickets are the refund alternatives that keep revenue in the event.

What a refund and a chargeback each cost

Processors treat the two differently, and the difference is what your policy should be built around. As of September 2026, from the processors' own Canadian pages:

Two consequences follow. First, on a $30 ticket, a lost Stripe dispute costs $30 plus about $1.17 in processing plus $15 or $30 in dispute fees: half again the ticket's value. Refunding the same buyer the day they asked would have cost $1.17. Second, because the processor keeps the original fee on every refund, a cancelled 1,000-ticket event at $40 leaves the organizer about $1,460 out of pocket in Stripe fees alone (1,000 × ($40 × 2.9% + $0.30)) after refunding every dollar of ticket revenue. The budgeting guide puts that in the contingency line for a reason.

On Eventist the charge runs through the organizer's own Stripe or Square account, so refunds and disputes appear in that account, on those terms, with no marketplace in between deciding the outcome; Eventist's own flat fee is separate from the processor's rate, and the pricing page shows how the two combine.

Write the refund policy before sales open

A refund policy is a contract term, and the buyer has to be able to see it before they pay for it to count as one. The event refund policy guide covers the wording; the structure that works for most events is:

• A deadline that is generous early and firm late. Full refund up to 30 days before the event, credit or transfer after that, no refunds inside seven days except for cancellation.
• The alternatives, named. Ticket transfer to another person, credit toward a future date, or a waitlist resale where returned tickets are offered to people who missed out and the original buyer is refunded when it sells.
• The cancellation and postponement promise. Full refund if the event is cancelled; for a postponement, the ticket carries to the new date with a refund window for those who cannot attend; for a material change (headliner replaced, venue moved), state what you will do.
• Where the fees go. Whether your refund is the face value or the all-in price the buyer paid. Refunding the full amount is simpler to defend and what most buyers expect; if you deduct a fee, say so on the ticket page, not only in the terms.

Then put it in three places: the ticket page above the buy button, the checkout terms the buyer accepts, and the confirmation email. The policy the buyer saw is the first document a bank asks for.

The refund request workflow

Requests arrive by email, Instagram DM, text to a volunteer and, worst, a comment on the event post. Give them one door: a short form or a single inbox linked from the ticket page and the confirmation email, asking for the order number, the email used and the reason. Then:

1. Decide within two business days. Inside policy: refund. Outside policy: offer the alternatives (transfer, credit, waitlist) in writing. A request that sits for a week becomes a dispute.

2. Refund the ticket, not the order. One person in a group of four cannot come; refund that ticket and leave the other three valid. On Eventist a single ticket in a multi-ticket order is refunded from the dashboard and the refund shows up against that order in the sales report, so the reconciliation matches the bank.

3. Log it. Order, date, reason, decision, who handled it. The log tells you at the debrief which tier, which date and which message drove the requests, and it is your record if the buyer disputes anyway.

4. Reply in writing with what was done and the processor's timing (refunds typically take several business days to appear on a card statement).

Alternatives deserve a real push, because they keep the revenue in the event. A transfer button on the ticket lets the buyer hand it to a friend without involving you; a credit is a sale for next year; a waitlist that resells returned tickets turns a refund into a delayed sale. Eventist ticket holders can transfer their own tickets from the ticket page, and organizers can run a waitlist on sold-out tiers, which together handle most of the "I can't make it" mail without a refund at all.

When the event is cancelled or postponed

Refund everyone, immediately, without waiting for requests. A buyer who has to ask for a refund on a cancelled event is a buyer who may ask their bank instead, and a dispute on a service that was never delivered is lost almost automatically, with the dispute fee added to the loss. Budget the processing fees you will not get back, send one clear email with the amount and the expected timing, and post the same notice on the ticket page and the socials. For a postponement, move the tickets to the new date and open a refund window (two to four weeks is common) for people who cannot attend; a shorter window creates disputes, a longer one delays your view of the new date's real attendance. The when to cancel guide covers the decision itself, and the event insurance guide covers cancellation cover, which reimburses committed costs but never the processing fees on refunds.

How a chargeback works

A chargeback (the processors say dispute) is the cardholder asking their bank to reverse a charge. The bank provisionally credits the cardholder, the processor debits or holds the amount from you and notifies you with a reason code, and you have a fixed window to submit evidence. The issuing bank then decides, which on Square's timeline can take up to 90 days from the start of the dispute. Card network rules generally allow cardholders around 120 days to dispute, and for something delivered later, like a ticket to an event, the period can run from the date of the event rather than the date of purchase, which is why a dispute can arrive in November for a ticket sold in March.

The reason codes you will see on tickets:

• Fraudulent / card not recognised. The cardholder says they did not make the purchase. Often a family member did, or the descriptor on the statement did not look like your event.
• Service not provided. The event was cancelled, the buyer says they were refused entry, or a postponed date did not suit them.
• Credit not processed. You agreed to a refund and it did not arrive, or the buyer says you did.
• Not as described. The headliner cancelled, the seat was not the one bought, the "VIP" was a wristband.
• Duplicate. Two charges for one order, usually a double-click.

Each code tells you what evidence the bank wants.

Building the evidence file

Banks decide disputes on documents, and the documents that win ticket disputes are the ones you already have if your ticketing keeps them:

• The order confirmation with the buyer's name, email, the tickets, the amount and the timestamp.
• The terms and refund policy the buyer accepted at checkout, with the timestamp of acceptance and a screenshot of where the policy appeared.
• Delivery. The email or link the tickets were delivered to, and any evidence they were opened or downloaded.
• The scan record. A ticket scanned at the gate, with time and location, ends most "service not provided" and many "fraudulent" disputes on its own. Eventist's QR check-in records every scan against the ticket, so the record exists whether or not anyone thought about disputes on the day.
• Correspondence: the refund request, your reply, any transfer or credit offered.
• A name match between the cardholder and the attendee, or, where a friend bought for a group, the group's names on the order.

Write a short, factual cover statement: what was sold, when, what the policy said, what was delivered, what was scanned. Submit inside the window (seven days on Square from notification; check the notice on Stripe). Decide in advance which disputes you will not contest: on Stripe, a manual response costs CA$15 whether you win or lose, so a $12 dispute may be cheaper to accept. On Square, where there is no fee, contest everything you have evidence for.

Preventing chargebacks

Most ticket disputes are not fraud; they are a buyer who could not find the refund path or did not recognise the charge. The prevention list is short:

• A card descriptor that names the event, or at least the organizer, so the statement line is recognisable months later.
• An immediate confirmation email with the tickets, the policy and how to request a refund or transfer.
• A visible refund policy on the ticket page and in the checkout, not only in a terms link.
• Fast answers to refund requests, because the dispute is the buyer's plan B.
• Transfers and credits so a change of plans never needs a bank.
• The processor's fraud tools left on (3-D Secure challenges on risky cards, the risk rules the processor offers), and a second look at orders with mismatched names, many tickets and a new email address.
• One charge per order: a checkout that blocks double submission, and a quick refund when a duplicate slips through.

Budgeting for it

Put two numbers in the budget: a refund reserve sized to last year's refund rate (or 3 percent of ticket revenue if you have no history), and the processing fees you would lose on a full cancellation, which is the number that decides whether cancellation insurance is worth buying. Track refunds and disputes weekly with sales, by tier and by reason, so a spike shows up while you can still change the message that caused it. The top reasons events fail has "fees and refunds ate the margin" at number seven for a reason: it is the leak that shows up in September, long after the decisions that caused it.

Frequently Asked Questions

Do I have to refund tickets if my event is cancelled?

Refund them. A cancelled event is a service not provided, the buyer can and will dispute the charge, and the dispute is lost almost automatically, with the processor's dispute fee added. Provincial consumer protection rules and your own terms also come into play; this is general guidance, not legal advice, and the cheapest path is the same in every province: refund everyone before they ask.

How long does a customer have to file a chargeback on a ticket?

Card network rules generally allow around 120 days, and for a service delivered on a later date, such as an event, the period can run from the event date rather than the purchase date. Keep the order, terms, delivery and scan records for every ticket until well after the event.

What does a chargeback cost an event organizer?

On Stripe in Canada as of September 2026, a CA$15 dispute fee that is returned only if you win, plus CA$15 more if you respond manually, plus the ticket revenue and the original processing fee if you lose. On Square there is no dispute fee, but the disputed amount is held while the bank decides, and the processing fee is not returned if the buyer wins.

How do I win a ticket chargeback?

With documents: the order confirmation, the terms and refund policy accepted at checkout with a timestamp, the delivery record, the scan at the gate and any correspondence, submitted inside the processor's window with a short factual statement. A scanned ticket is the single strongest piece of evidence.

Can I refund one ticket from a group order?

Yes, on most platforms and processors a partial refund of the order is possible; on Eventist a single ticket within an order is refunded from the dashboard while the others stay valid, and the refund is recorded against the order in the sales report.

What is friendly fraud at events?

A cardholder disputing a legitimate purchase, usually because they did not recognise the charge, could not attend, or found the dispute easier than the refund request. Clear descriptors, immediate confirmations, a visible refund policy and fast refund handling prevent most of it; the scan record wins most of the rest.

Refunds are a cost of selling tickets; chargebacks are a cost of making refunds hard. Publish the policy, answer requests inside two days, refund the ticket rather than the order, keep the scan record, and let transfers carry the rest. If you want single-ticket refunds, transfers, waitlists and a scan log in the same dashboard as the sales report, the Eventist events platform runs them through your own Stripe or Square account; the refund policy guide has the wording to start from.