How to sell tickets to a community event (5 options compared)

You run a Discord, Slack, Telegram, or WhatsApp community. Someone suggests a workshop, meetup, or online cohort. Then the practical question arrives: how do you sell tickets online without turning a friendly community event into a finance project?

There is no single right tool. There are five realistic approaches — and most organizers pick the wrong one for their size, then fight the tool instead of the guest list.

What you’ll learn

• Whether charging makes sense for your community event
• Pricing psychology that works for members (not stadium concerts)
• Five ways to sell tickets, from a plain Stripe link to a community invite/event page
• A structural comparison of what each approach handles — and what fee model to expect
• Why this guide will not quote competitor fee percentages (and where to check current numbers)
• Refunds, taxes/VAT, no-shows, and the ops details people get wrong

Should you charge at all?

Before you compare platforms, decide whether money belongs in this event.

Charge when:

• There is a hard cost (venue deposit, catering, AV, guest speakers, software seats)
• A price filters for commitment — free RSVPs that ghost you every time
• The format is a workshop or cohort with limited seats and real prep time
• Members have asked for something “more serious” than a casual hangout

Stay free when:

• The goal is discovery, onboarding, or belonging
• You are testing a new format and do not know demand yet
• Collecting payment would create more ops work than the revenue is worth
• Your community’s culture treats paid events as a trust breach (some do — listen)

A useful middle path: free RSVP with optional paid add-ons (dinner, recordings, merch) or a low “deposit” ticket that you refund at the door. That captures commitment without framing the night as a product launch.

Pricing psychology for community events

Community tickets are not conference tickets. Members already give you attention; a high price can feel like a tax on belonging.

Practical patterns that tend to work:

1. Anchor to cost, not prestige. “Covering the room and coffee” reads cleaner than “premium mastermind access” for a Tuesday meetup.
2. Offer a member rate. If outsiders can buy a seat, price members lower — or open sales to members first. That rewards the people who already showed up in chat.
3. Keep tiers simple. One general admission ticket beats a maze of Early Bird / VIP / Super-VIP for a 40-person workshop. Add a second tier only when the deliverable actually differs (for example, ticket vs ticket + 1:1).
4. Publish the refund rule next to the price. Ambiguity creates support tickets; clarity creates trust.
5. Prefer round numbers members can remember when they tell a friend — but do not optimize for “growth hacking” tricks. Community reputation compounds slower than conversion rate tricks decay.

If you are unsure, run a one-question poll in the community: free, low-cost, or full workshop pricing. Members will tell you what the room can bear.

Five realistic ways to sell tickets

These are categories, not a shopping list. Inside each category, products change features and prices often — evaluate the job first.

1. Plain Stripe Payment Link or invoice

What it is: You create a Stripe Payment Link, Checkout page, or invoice for a fixed amount. Buyers pay. You track who paid in Stripe (and usually a spreadsheet).

What you handle yourself: guest list, capacity, waitlist, reminders, check-in, refunds policy, and the public event story page (Notion, your site, a Google Doc — anything).

Fee model to expect: payment processing only (card networks + Stripe). No separate “event platform” layer unless you add one. Confirm current rates on Stripe’s pricing page for your country and payment methods.

Best for: one-off events, tiny guest lists, organizers who already live in spreadsheets.

Weak when: you need public discovery, QR check-in, automatic capacity caps, or a polished event page strangers will trust.

2. General-purpose events platforms

What it is: Tools built around hosting and listing events — think products in the vein of Luma and similar “create an event page, take RSVPs or payments, manage the guest list” platforms. The event page is the product.

What they usually handle: public event page, RSVP or ticketing, email updates, calendar invites, sometimes discovery/network effects if the platform has a consumer audience.

What you still do: show up, moderate the room, decide membership rules for your community home (Discord etc.), and reconcile whether the guest list matches who is actually in chat.

Fee model to expect: often a mix of free RSVPs plus paid-ticket economics — commonly a platform cut and/or payment processing. Do not trust a number you saw in a tweet. Open the vendor’s current pricing or help page before you publish tickets. For Luma specifically, start at their site and look for the current pricing/billing docs (product packaging changes). Our Luma comparison is for positioning, not a substitute for their live pricing.

Best for: events where the page and guest list matter more than deep integration with your chat community.

Weak when: you need the ticket purchase tightly gated to community membership, or you already resent running yet another destination members must visit.

3. Dedicated ticketing platforms

What it is: Software whose core job is selling and scanning tickets — Eventbrite is the name most people know; others include organizer-focused tools with door scanning, reserved seating, and marketing add-ons.

What they usually handle: ticket types, promo codes, capacity, refunds workflows, buyer fees vs organizer fees options, check-in apps, and sometimes paid promotion.

Fee model to expect: typically a percentage of ticket price and/or a per-ticket fee, plus payment processing — sometimes passed to the buyer as a “service fee.” Structures differ by plan, country, and whether the event is free. Check Eventbrite’s organizer pricing (and the equivalent page for any other vendor) right before you launch. Our Eventbrite comparison explains fit for communities; it is not a fee quote.

Best for: larger public events, multi-ticket types, door scanning, or when you want a marketplace-style listing.

Weak when: fees feel heavy relative to a low community ticket price, or the platform UX is overkill for a 25-person workshop in your existing Discord.

4. Community platforms with ticketing built in

What it is: All-in-one community homes (for example Circle, Skool, and similar) that also sell courses, memberships, or event-style access inside the same product where discussion happens.

What they usually handle: membership billing, some event or cohort primitives, and keeping everything behind one login.

Fee model to expect: usually a SaaS subscription for the organizer, sometimes plus payment processing on transactions. Ticket-style fees may be secondary to “host your whole community here” pricing. Always open the vendor’s current pricing page — packs and percentages change.

Best for: organizers willing to move the community into that platform, not only sell a ticket.

Weak when: your members already live in Discord/Telegram/WhatsApp/Slack and will not migrate for one workshop. Ticketing that requires a platform move is a migration project wearing a checkout button.

5. Purpose-built community invite / event pages

What it is: A public page in front of the chat community you already run — applications or open join for the community, plus event pages and Stripe checkout for ticketed nights. The chat home stays where it is; the page is the front door and the ticket desk.

What they usually handle: branded public URL, event details, Stripe payments, sometimes approval or screening before someone lands in chat, and a guest list tied to the same audience you already moderate.

Fee model to expect: commonly a platform percentage on ticket sales (sometimes lower on a paid plan) plus payment processing. SaaS subscription may exist separately from ticket fees.

Best for: communities that want paid events without leaving Discord/Telegram/WhatsApp/Slack, and that care about screening joiners over time — not only selling one SKU.

Weak when: you need arena-scale box office features (complex seating maps, promoter workflows) or you have no community home at all — then you want a general events or ticketing product.

Structural comparison (not a fee quote sheet)

Competitors change prices. Publishing a table of someone else’s percentages is how blog posts become wrong six months later. Below is what actually stays useful: structure.

Approach	Handles for you	You still do yourself	Fee model shape	Suits
Stripe Payment Link / invoice	Collecting card payments, basic receipts	Event page, capacity, guest list, check-in, reminders	Payment processing only	Tiny or one-off sales
General events platform	Event page, RSVPs/tickets, guest messaging	Community home integration, sometimes discovery strategy	Platform fee and/or processing on paid tickets (verify live)	Page-first public events
Dedicated ticketing	Ticket types, door tools, promo codes, larger-event ops	Keeping the sale connected to your chat community	% and/or per-ticket + processing (verify live)	Bigger or public ticketed events
Community suite with billing	Membership + some events in one login	Migrating members onto that suite	SaaS sub + processing (verify live)	Willing to host community in-platform
Community invite/event page	Public front door + Stripe tickets beside existing chat	Venue/ops of the event itself	Platform % on tickets + processing; plan may change the %	Chat community stays put

When you compare options for a real launch, build a tiny spreadsheet with your ticket price, expected headcount, and the fee lines from each vendor’s current page. Run the math on your numbers — not on a blog’s memory.

The mechanics organizers get wrong

Refunds

Decide these before the first sale:

• Full refund until when? (48 hours before start is a common community default — pick what you can honor)
• What happens if you cancel? Full refunds, promptly, without making people chase you
• Partial refunds / credit for recordings if someone cannot attend live
• Who clicks the button? Know how your tool issues refunds (Stripe Dashboard vs platform UI) before you need it at 11pm

Write the policy on the event page. Support tickets are just unpublished policy.

Taxes and VAT

If you sell tickets, you may have obligations around sales tax, VAT, GST, or similar — depending on where you are, where buyers are, and how you are organized legally.

This guide will not pretend that is simple. Thresholds, reverse charge rules, and “is this a digital service?” questions are jurisdiction-specific. Check with an accountant who understands your country before ticket revenue becomes material. Your payment tool may offer tax features; those features are not a substitute for advice.

No-show rates

Free RSVPs no-show more than paid tickets. Paid tickets still no-show.

Plan for it:

• Overbook slightly only when the room format allows (online workshops tolerate this better than seated dinners)
• Send a reminder 24 hours out with the cancel/refund link
• For free events, require a double confirm or a deposit you refund at attendance
• Do not take personal offense — no-shows are usually logistics, not rejection

Track no-show rate for two or three events. That number teaches you more than generic “industry benchmarks” (which we will not invent here).

Capacity and waitlists

If the tool cannot waitlist, you will invent a waitlist in DMs. Prefer a system that closes sales at capacity and queues the next people. Manual “we’ll squeeze you in” promises create awkward door conversations.

Communication after purchase

Buyers need: confirmation, calendar details, access links (Zoom/venue), and a place to ask questions. If your ticketing tool’s emails are weak, schedule your own messages. Silence after payment is how chargebacks start.

Day-of check-in

Decide how you will answer “who paid?” at the door or in the Zoom waiting room:

• A searchable guest list export from your tool (name + email is usually enough)
• QR or order-number scan if you chose a dedicated ticketing product
• A single admin account that owns the list — not five conflicting spreadsheets in DMs

Online events need a backup: what if the payment email is delayed and someone is stuck outside? Have a moderator who can verify in Stripe (or your platform) without derailing the host.

Currency, payouts, and timing

If members are in multiple countries, check whether your payment tool settles in a currency you can actually use, and how long payouts take. A sold-out workshop with funds stuck in a pending balance is still a successful sale on paper — and a stressful week in practice. Read the payout section of your provider’s docs before you announce the date.

How Inviter fits (optional)

If your community already lives on Discord, Telegram, WhatsApp, or Slack, and you want a public event page with Stripe checkout in front of that home, Inviter’s events are built for that pattern — not as a full arena box office.

Facts worth knowing if you evaluate it:

• Free to start
• Event ticketing via Stripe: 10% platform fee on Free, 5% on Pro, plus Stripe’s processing fees on both
• Pro at $19.99/month or $191.90/year (yearly is 20% off)
• Applications, email verification, country allow/deny rules, and captcha on invite flows
• Event pages emit schema.org Event structured data
• Used by 1,200+ communities

Compare plan math on pricing. If you are weighing page-first tools, read /vs/luma and /vs/eventbrite for fit — then verify those vendors’ live prices yourself.

Inviter is optional. A Stripe Payment Link and a careful spreadsheet remain a correct answer for many community nights.

Pick a path

Situation	Practical choice
Under ~30 seats, one-off, you hate new SaaS	Stripe Payment Link + page you control
You want a beautiful public event page and guest list	General events platform
Door scanning, many ticket types, public promo	Dedicated ticketing platform
You are ready to move the whole community	Community suite with built-in billing
Chat stays put; you need a front door + tickets	Community invite/event page (or Stripe if tiny)

Selling tickets for a community event is mostly ops design: price honestly, publish the refund rule, pick a fee model you understand, and only then worry about which logo sits on the checkout button. Start with the smallest stack that will not embarrass you at the door — you can always graduate tools when the guest list demands it.