The first time a host runs a dinner series, the math looks clean: twelve seats, everyone pays, everyone shows. Then two guests cancel the morning of, one never replies, and the host is standing in a private kitchen they already put money down on, holding food they already bought, short three seats' worth of revenue. Nothing was overbooked and nothing was mispriced. The event just wasn't protected. The fix is old, boring, and it works: take a deposit at signup, so the people who walk in are the people who already had money on the line.
A deposit is a partial payment a guest makes to reserve a seat, with the balance due before the event. The one-line version of everything below: take a set share of the ticket now, collect the rest before the doors open, and pair it with a clear, written non-refundable-deposit policy so the commitment actually holds.
Why collect a deposit at all?
Collect a deposit because it does three jobs at once — it filters out the people who were never really coming, it funds the costs you have to pay before anyone arrives, and it converts a soft "maybe" into a real commitment. A free RSVP costs the person nothing to break. A paid deposit costs them something, and that small cost changes who actually shows.
Start with the filter. The gap between "I'd love to come" and "I paid to come" is the entire difference between a list of names and a room full of guests. People overcommit to free things and quietly drop them; almost nobody forgets an event they've already paid toward. A deposit doesn't just reduce no-shows, it selects for the guests who were serious in the first place, which is exactly the crowd you want in the room. This is one of the levers behind actually filling seats, covered in full in how to fill an experience.
Then cash flow. Most in-person events ask you to spend real money before a single guest arrives — a venue deposit, a catering minimum, a materials order, a first hotel night. That upfront spend is the scariest part of hosting, because you're out of pocket on faith. Deposits turn some of your guests' commitment into cash you can put toward those bills, so you're not financing the whole event from your own account and hoping it fills. If you're still sizing what those upfront costs even are, how much does it cost to host an event breaks the line items down, and is hosting an experience profitable walks the full margin.
Finally, commitment is psychological. Once someone has money in an event, they plan around it — they book the babysitter, they clear the calendar, they tell a friend. The deposit is the moment the event becomes real in their head. That's why a deposit belongs in your operational plan from the start, not bolted on later; the whole sequence of running an event lives in how to host an event, and validating that anyone wants it at all comes first in how to validate demand for an event.
How big should the deposit be?
Set the deposit as a share of the ticket price — usually somewhere between 20 and 50 percent — large enough to hurt if they walk, small enough that saying yes still feels easy. Too small and it doesn't filter anyone; a five-dollar deposit on a four-hundred-dollar seat protects nothing. Too large and you've just made the full ticket the barrier you were trying to lower. The point of a deposit is to split the "yes" into a small commitment now and a larger one later, so aim for a number a serious guest pays without flinching but a flake won't.
A practical rule: the deposit should at least cover the per-guest cost you can't recover if they cancel. If each seat commits you to roughly $80 of non-refundable catering and venue cost, your deposit needs to be at least that, or a no-show costs you money even after keeping the deposit. Price the ticket first — how much to charge for an experience covers that — then set the deposit as a slice of it.
Illustrative worked example — round numbers, not a quote. Say a seat at your event is $400 and you set a 30 percent deposit. The guest pays 0.30 × 400 = $120 now to reserve, and the remaining 400 − 120 = $280 as the balance before the event. The two add back to the full 120 + 280 = $400. That $120 is enough to sting if they bail and enough to put toward your catering minimum, while $280 later keeps the initial "yes" small.
Pick round, legible numbers — a 25, 30, or 50 percent deposit reads clearly on a checkout page and is easy to explain in your policy. Guests trust a number they can understand.
What are your options for collecting one with Stripe?
You have three honest ways to collect a deposit with Stripe, and one tempting option that does not work for events. The three that work: charge the deposit as a normal payment now and charge the balance later off a saved card; charge the deposit now and send a follow-up invoice or payment link for the balance; or take the full amount upfront and treat part of it as non-refundable. All three are built from standard Stripe pieces, and none require anything exotic.
The option that does not work is a plain authorization hold. It's the intuitive idea — put a "hold" on the card now, capture it later — but a Stripe card authorization that hasn't been captured expires after about 7 days. For an event that's weeks or months out, the hold is long gone before you'd charge it. Holds are for same-week transactions, not for a deposit you're carrying until an event in the fall. To reserve money across that gap you need a real charge now, or a card saved with the guest's permission to charge later. Get this part right and the rest is straightforward.
Here's how each working method actually behaves.
Method 1: Charge the deposit now, save the card, charge the balance later. The guest checks out and pays the deposit as an ordinary payment today. At the same time, with their agreement, Stripe saves their card to their customer record so you can charge it again later without them present — an "off-session" charge. When the balance is due, you charge the saved card for the remaining amount. To the guest it feels like one purchase split in two; to you it's the smoothest version, because you don't have to chase anyone for the second payment. The trade-off is that it leans on saving a payment method and charging it off-session, so you need the guest's clear consent up front and you have to handle the case where the later charge fails.
Method 2: Charge the deposit now, send an invoice or payment link for the balance. The guest pays the deposit today, and when the balance comes due you send them a Stripe invoice or a Stripe Payment Link for the rest, which they pay themselves. This is the simplest to reason about — two separate, guest-initiated payments — and it doesn't require saving a card or charging anyone off-session. The cost is that collecting the balance is now an action the guest has to take, so some won't, and you'll spend the final week sending reminders and re-sending links.
Method 3: Collect the full amount upfront, make part of it non-refundable. Instead of splitting the payment, you charge the whole ticket at signup and declare in your policy that a defined portion — effectively the deposit — is non-refundable if they cancel. There's no balance to chase because there's no balance; the "deposit" exists only in your refund policy, not as a separate charge. This is the least operational work and the strongest cash position, but it's the biggest ask at the moment of signup, which can cost you fence-sitters who'd have said yes to a smaller first step.
The 7-day rule is the single most common way hosts get deposits wrong. An uncaptured card authorization is not a way to reserve money for a future event — Stripe releases it after roughly a week. If you want to hold a guest's commitment from signup until an event months away, you must either take an actual charge now or save their card (with consent) to charge later. When in doubt, check Stripe's own documentation on saving cards, off-session charges, invoices, and payment links before you build anything.
| Method | How it works | Best for | Watch out for |
|---|---|---|---|
| Deposit now + saved card for balance | Guest pays deposit today; card saved with consent and charged off-session for the balance later | Smoothest guest experience; hosts who don't want to chase the second payment | Needs clear upfront consent to save and re-charge; handle the case where the later charge fails |
| Deposit now + invoice / payment link for balance | Guest pays deposit today; you send a Stripe invoice or payment link for the balance, which they pay | Simplest to reason about; no saved-card setup | Balance is guest-initiated, so some won't pay on time; expect to send reminders |
| Full amount upfront, part non-refundable | Whole ticket charged at signup; a defined portion is non-refundable per your policy | Least admin; strongest cash position | Biggest ask at signup; can lose people who'd take a smaller first step |
None of the three is wrong. Pick the deposit-plus-saved-card path when a frictionless guest experience matters most, the invoice path when you want simplicity over automation, and the full-charge path when you'd rather carry no balance at all. What matters is that you chose deliberately and wrote the policy to match.
How do you charge the remaining balance?
Charge the balance a set number of days before the event — commonly one to three weeks out — using whichever collection method you chose at signup: an automatic off-session charge on the saved card, or an invoice or payment link the guest pays. Pick the date up front and put it in writing, so the balance charge is something the guest already agreed to rather than a surprise.
If you saved the card, the balance is an off-session charge you trigger on that date — the cleanest path, because nothing depends on the guest remembering. If you're invoicing, send the balance invoice or payment link with enough runway that a busy person can pay it before the deadline, then send one or two reminders. Either way, state the balance due date at the moment of the deposit ("Your $120 deposit reserves your seat; the $280 balance is due two weeks before the event"), so the second payment is expected.
Give yourself a cutoff. Set the balance deadline far enough ahead that if someone doesn't pay, you still have time to resell the seat to your waitlist. A balance due the night before helps nobody; a balance due two or three weeks out turns a non-payment into a recoverable open seat instead of an empty chair. The general logic of cutoffs and reselling seats sits alongside your refund and cancellation policy for experiences, which is the document that says what happens when the balance doesn't come.
Is a deposit refundable?
A deposit is only as strong as the policy printed next to it — so decide in advance whether it's refundable, say so in plain language at checkout, and treat a non-refundable deposit as the default for events with real upfront costs. The whole protective power of a deposit comes from the guest knowing they lose it if they bail. A deposit you quietly refund on request is just a free RSVP with extra steps.
The clean, common structure: the deposit is non-refundable, and the balance is refundable up to a stated cutoff date, after which it isn't. That splits the risk fairly — the guest can change their mind early and only forfeit the small first payment, while you keep enough to cover the costs their seat already committed you to. Whatever you choose, write it where the guest sees it before they pay, in language a normal person understands, and repeat it in the confirmation email. Most disputes come from surprise, not from the policy itself; a guest who read "deposit is non-refundable" before paying rarely fights it later.
Build this alongside the deposit, not after. The full version — cutoff dates, tiered refunds, cancellation-by-the-host clauses, and the exact wording — lives in the refund and cancellation policy for experiences guide, which is the sibling every deposit needs.
How do the fees work on a deposit?
A deposit is a normal card payment, so it carries the normal processing fee — Stripe's standard US online rate is 2.9% + 30¢ per transaction — and if you split the payment in two, you generally pay that fee twice, once on the deposit and once on the balance. Rates vary by country and payment method, so treat 2.9% + 30¢ as the US online baseline, not a universal number.
Run it on the worked example. On the $120 deposit, the fee is about 120 × 0.029 = $3.48 plus the 30¢ flat, so roughly $3.78, leaving you about $116.22. When you later charge the $280 balance, that's a second transaction with its own fee. Two charges means two flat 30¢ fees instead of one, so splitting a payment costs marginally more in processing than taking it all at once — a few dimes, not a reason to change your approach, but worth knowing.
The fee detail that actually matters for deposits: when you refund a charge, the processing fee is generally not returned to you. If a guest pays a $120 deposit and you refund it, you're typically out the ~$3.78 fee even though the guest gets their full $120 back. That's a concrete reason non-refundable deposits and clear policies matter — every refund you issue is a small cost you eat on top of the returned money. It's also why "we don't refund the deposit" is a fair, standard policy rather than a stingy one: the deposit is doing real work, and refunding it costs you twice. For how these fees stack across a whole event, how much does it cost to host an event has the full picture.
How does a platform handle this for you?
A purpose-built platform collects the deposit, schedules the balance, and sends the reminders for you — all running on your own Stripe account — so you get the protection of a deposit without wiring the payment plumbing yourself. Everything above is buildable by hand, but "buildable" and "worth your afternoon" aren't the same thing. Saving cards with consent, timing off-session charges, generating balance invoices, chasing failed payments, and keeping the refund policy in sync is a real project.
This is the gap Meuse is built to close. You set the deposit as a share of the ticket, and the platform takes it at signup, holds the balance due date, charges or invoices the rest on schedule, and nudges guests who haven't paid — with the money moving through your Stripe account, so the buyer stays your customer, with Meuse's flat 10% platform fee applying on top of processing. The deposit, the balance, the reminders, and the guest list live in one place instead of across a spreadsheet, a calendar reminder, and your payment dashboard. If you're deciding where to sell in the first place, how to sell tickets on your website and how to host an in-person experience cover the surrounding setup, and deposits slot straight into it.
Related guides
Keep building the money-and-logistics side of your event:
- How to Host an Event
- Refund and Cancellation Policy for Experiences
- How Much to Charge for an Experience
- How Much Does It Cost to Host an Event
- How to Sell Tickets on Your Website
- How to Fill an Experience
- Installment Payments & Payment Plans for Experiences
- What Is a Deposit? Definition for Experience Bookings
Frequently asked questions
How much deposit should I ask for?
Set it as a share of the ticket, usually between 20 and 50 percent, and at minimum enough to cover the per-guest cost you can't recover if someone cancels. On a $400 seat, a 30 percent deposit is $120 now and $280 later — small enough that saying yes stays easy, large enough to filter out people who were never really coming. If each seat commits you to, say, $80 of non-refundable catering, your deposit should clear that so a no-show never costs you money after you keep it.
Can I make the deposit non-refundable?
Yes, and for events with real upfront costs it should usually be the default. The protective power of a deposit comes from the guest knowing they forfeit it if they bail. State it in plain language at checkout and repeat it in the confirmation email, so nobody is surprised — surprise is what causes disputes, not the policy itself. A common, fair structure is a non-refundable deposit with a refundable balance up to a cutoff date. Build the full wording alongside your refund and cancellation policy.
How do I collect the balance?
Charge it a set number of days before the event, using the method you chose at signup. If you saved the guest's card with their consent, the balance is an automatic off-session charge on your chosen date. If you didn't, send a Stripe invoice or payment link and follow up with a reminder or two. Either way, announce the balance due date at the moment they pay the deposit, and set the deadline far enough ahead that an unpaid balance leaves you time to resell the seat.
Do deposits work for far-future events?
Yes, but not with an authorization hold. An uncaptured Stripe card authorization expires after about 7 days, so a "hold" is useless for an event weeks or months out — it's released long before you'd capture it. For a far-future event you need an actual charge now (the deposit as a real payment) plus either a saved card to charge for the balance later or a follow-up invoice. The deposit sits safely in your account the whole time; only the balance waits.
What if someone's card fails for the balance?
Plan for it, because some will. If you're charging a saved card off-session and it declines, Stripe surfaces the failure so you can retry or reach out — have a short backup flow ready: email the guest, send a fresh payment link, and give them a couple of days against your cutoff. If you're invoicing, the same reminder cadence applies. The reason to set the balance deadline two or three weeks out is exactly this: a failed or late payment becomes a seat you can resell to your waitlist instead of an empty chair on the day.
Should I use a platform or wire it up in Stripe myself?
Both work; it's a question of your time. Doing it by hand in Stripe means managing saved cards, off-session timing, balance invoices, failed-payment retries, and reminders yourself. A platform like Meuse runs all of that on your own Stripe account — deposit at signup, scheduled balance, automatic nudges — at a flat 10% platform fee on top of processing. If you're running one small event and enjoy the control, hand-wiring is fine. If you'd rather spend the afternoon on the event itself, a platform pays for the setup it removes.
A deposit is the cheapest insurance a host can buy: it filters the room down to people who meant it, puts cash toward the bills you pay before anyone arrives, and turns a maybe into a plan. Take a clear share now, collect the rest before the doors open, and print the non-refundable policy right next to the checkout. If you'd rather not build the deposit-plus-balance-plus-reminders machinery yourself, Meuse handles all of it natively on your own Stripe — you set the deposit, it takes the balance and sends the nudges, and the guest stays your customer the whole way through.
