Taking Payments for Events and Bookings

A wedding venue paid in March for October. A class pack bought in January for sessions through June. A workshop sold out three months ahead. Every one of these is a payment for something that hasn't happened yet — which is exactly what processor risk monitoring is built to watch, since a business that takes money and then can't deliver leaves customers disputing charges the processor may have to fund. Getting the structure right up front — deposits, policies, and what you tell your processor — is what separates a smooth season from a frozen account in the middle of one.

The gap the processor sees

Per our processor review guide, monitoring asks one question: how much has this merchant been paid for things not yet delivered? For event businesses that number is large by design.

Business	Typical gap between payment and delivery	Exposure
Retail	Minutes to days	Low
Classes sold as packs	Weeks to months	Moderate
Workshops and ticketed events	Weeks to months	High
Venues, weddings, travel	Months to over a year	Very high

A venue with a strong spring booking season can hold a year's revenue in advance payments — and from a processor's position that's a year of revenue customers could dispute if something went wrong. Per our reserves guide, this is why these businesses frequently see rolling reserves or delayed settlement.

Tell your processor first

The single most effective step, and it happens before the first sale.

• Describe the business accurately at application — how far ahead you sell, typical ticket sizes, seasonality.
• Say when your booking season is, so a spring surge isn't read as anomalous volume.
• Ask directly about reserves — whether one applies, how it's calculated, and when it's released.
• Flag anything unusual — a large event, a new venue, a longer booking window.

Per our processor review guide, a change flagged in advance is a conversation; the same change discovered by monitoring is an exception. An event business that surprises its processor with a season's worth of advance sales risks a hold at the moment it most needs the cash to prepare.

And plan for a reserve if one is likely. Budget for the cash you won't receive until later, per our forecasting guide, rather than discovering it in settlement.

Deposit and balance

The structural choice that reduces exposure on every side.

	Full payment up front	Deposit now, balance near the date
Cash you hold	All of it, for months	A fraction until close to the date
Processor exposure	Maximum	Much lower
Refund exposure if you cancel	Everything	Deposits only, for most bookings
Customer commitment	Harder to make	Easier to make
Risk the balance fails	None	Real — needs a process

For anything booked well ahead, deposit-plus-balance is usually better for both sides. Size the deposit to cover the cost of holding the date — the other bookings you turn away — and set the balance date close enough to the event that most cancellations happen before it.

The bottom row is the cost. Collect the balance by stored card or bank debit with clear consent, per our stored card guide, and remind the customer a week ahead — a card that has expired since the deposit is the most common reason a balance fails.

The cancellation policy

Your main evidence in any dispute, so it has to be seen before payment.

A good policy states, in plain words:

1. What's refundable and when — typically a schedule, with less refunded as the date approaches.
2. Whether the deposit is refundable, and in what circumstances.
3. What happens if the customer can't attend — transfer, reschedule, credit.
4. What happens if you cancel or change the event.
5. How to cancel, and by when.

Show it at checkout and require an acknowledgement — a tick box next to the policy text, recorded with the booking. Per our refund policy guide, a policy customers never saw isn't evidence of anything.

Check local consumer protection rules too. Some jurisdictions limit what can be kept on a cancellation, particularly for consumers, and a policy that exceeds those limits won't hold whatever the customer ticked.

And offer alternatives to a refund where you can. A transfer to another person or a rescheduled date keeps the revenue and resolves most cancellations without the customer feeling they've lost out.

No-shows and stored cards

Charging a no-show fee to a card on file works — when it's been set up properly.

• State the fee and when it applies at booking, clearly.
• Get explicit consent to store the card and charge it under those conditions, recorded.
• Send a reminder before the appointment that restates the fee.
• Use a descriptor the customer will recognize, per our descriptor guide.
• Notify the customer when you charge it, with the reason.

Card network rules govern charges made on stored credentials, and a no-show fee the customer doesn't remember agreeing to will likely be disputed — and lost. The reminder is what does the most work: it both reduces no-shows and proves the customer knew.

Money held, not earned

The accounting point that becomes a cash point.

Per our deposits guide, payment for an event that hasn't happened is held on the customer's behalf until it does. Recording it as revenue when received overstates the business's performance and, more practically, invites spending money that may need to be returned.

• Track advance payments separately — what's been paid for events not yet delivered.
• Hold at least the refundable portion in the obligations tier, per our cash management guide.
• Recognize revenue as events are delivered, with your accountant confirming the treatment.
• Watch the balance through the season — it's the number that tells you how much you'd owe if everything stopped.

Using next season's deposits to fund this season's costs is common and dangerous. It works while bookings keep growing and fails the first time they don't — per our cash cycle analysis, the same structure as any business funded by its customers' money.

If you have to cancel

The scenario to plan for while it's hypothetical.

An event cancelled by you refunds everyone at once. Customers will generally be entitled to a refund or a reasonable alternative, and if they don't get one, they dispute.

1. Know what you'd owe for each upcoming event, from the held-payments figure above.
2. Check your insurance — per our insurance guide, event cancellation cover exists for some situations.
3. Communicate early and plainly, per our disruption guide.
4. Offer the choice of a refund, a new date, or credit — many customers take the alternative if it's offered first and fairly.
5. Refund promptly rather than waiting to be asked; per our refunds guide, a refund costs less than a dispute in every respect.
6. Tell your processor before refund volume spikes.

Item six is the one that protects the account. A wave of refunds or disputes with no explanation looks like a failing business; the same wave with a notice attached looks like a business handling a cancellation responsibly.

Disputes

Event disputes are usually about one of four things:

• "I cancelled and wasn't refunded" — your acknowledged policy and cancellation dates are the evidence.
• "The event didn't happen" — attendance records, or proof it went ahead.
• "It wasn't as described" — the event description at the time of purchase.
• "I don't recognize this charge" — usually a descriptor problem, or a balance or no-show charge taken long after booking.

Per our dispute guide, the evidence has to be captured at the time — the policy acknowledgement, the booking confirmation, the reminder, the check-in record. None of it can be reconstructed later.

Frequently asked questions

---

This guide is educational and does not constitute legal advice. Consumer protection rules on cancellations, refunds, deposits, and no-show fees vary by jurisdiction; card network rules govern stored-credential charges and dispute handling; and reserve and settlement terms are set by your processor agreement. Consult a qualified attorney about your cancellation policy and obligations.