Paid and free tickets on your own site — with zero sales cut.

Configure ticket types inside your EmDash editor, accept cards through Stripe Checkout or bank transfers by invoice, deliver scannable QR tickets, and scan visitors in at the doorway.

  • Commercial · USD 30 / 100 / 200 / yr
  • 0% share of ticket sales
  • English & French
Eventual RSVP – Tickets setup page: licence status, card-payment checklist with Stripe keys not yet saved, and the steps to connect Stripe.Eventual RSVP – Tickets setup page: licence status, card-payment checklist with Stripe keys not yet saved, and the steps to connect Stripe.
Tickets setup: Stripe stays optional until you charge by card; free tickets and invoices work without it.
Separate from free Registrations events
Events explicitly set to Tickets are handled by Tickets, leaving free Registrations registrations untouched so the same place can never be issued twice.
Stripe stays optional
Free tickets and pay-by-invoice bookings work out of the box with no Stripe credentials or server encryption key required.
Offline key verification
A signed key validates your domain locally with zero external calls. Existing orders, QR pages, and refunds keep working at all times.

From ticket setup to confirmed payment

Every checkout reserves places atomically so sessions never overbook—whether a buyer pays immediately by card or pays a bank invoice later.

Ticket categories right inside the event editor

Add up to 20 ticket categories per event (adult, concession, free, member) with optional per-category quotas inside the event’s overall capacity, per-order caps (1–50), sales windows, and custom questions.

  • Enable pay by invoice per event with custom bank transfer payment instructions.
  • Visitor checkout, transactional emails and the admin run in 21 languages, with each language’s price and date formats.
Tickets panel in the event editor for a concert: tickets sold, Standard, Concession and Under 16 ticket types in GBP with sales counts, and ticket settings.Tickets panel in the event editor for a concert: tickets sold, Standard, Concession and Under 16 ticket types in GBP with sales counts, and ticket settings.
Ticket types managed inside the event editor: name, price or free, quota per date and order limit.
Ticket checkout on a phone for a concert: Standard, Concession and Under 16 quantities in pounds, buyer name and email, and a choice of card or invoice.Ticket checkout on a phone for a concert: Standard, Concession and Under 16 quantities in pounds, buyer name and email, and a choice of card or invoice.
Checkout on a phone: pick quantities and pay by card or invoice, without an account.
Pay-by-invoice confirmation on a phone: places reserved, the organiser’s bank transfer instructions, the order reference and a link to view or cancel the order.Pay-by-invoice confirmation on a phone: places reserved, the organiser’s bank transfer instructions, the order reference and a link to view or cancel the order.
Pay by invoice: places are held while the transfer arrives; the buyer can still cancel.

Buyer QR order portal and doorway check-in

Buyers open their order directly from an email link with no account or password needed—and staff verify tickets at the venue door in one scan.

Buyer’s order page for two free places: confirmed status, QR code, typed fallback code and the self-cancellation deadline.Buyer’s order page for two free places: confirmed status, QR code, typed fallback code and the self-cancellation deadline.
Buyer’s order page: one QR code that admits the whole order, a fallback code and a cancellation window.
Door check-in page after a ticket code was entered: Admit 2, with the buyer’s name and ticket type.Door check-in page after a ticket code was entered: Admit 2, with the buyer’s name and ticket type.
Door check-in: scan the QR code or type the code; the screen says how many people to admit.

Orders, refunds, privacy erasure, and measured limits

From Admin → Orders, mark bank transfers paid to email buyer QR tickets, issue manual full or partial Stripe refunds, and download formula-safe treasurer CSV reports in the event’s local time zone.

  • Configurable personal-data retention (30–3,650 days, 365 default) clears buyer names, emails, and answers while keeping financial totals intact.
  • Email lookup erasure clears past and cancelled buyer details while protecting active upcoming orders.
Tickets Orders page just after an invoice was marked paid: confirmation that the buyer was sent their ticket, and the remaining invoices awaiting payment.Tickets Orders page just after an invoice was marked paid: confirmation that the buyer was sent their ticket, and the remaining invoices awaiting payment.
Orders: mark a bank transfer paid and the buyer gets their tickets by email; cancel, refund or export to CSV.
OperationDocumented bound (10-call sandbox)Behaviour past the bound
Automatic reconciliation per date≈ 700 ordersSkipped cleanly and retried later; split large events into separate dates.
Orders CSV export≈ 700 ordersTruncated cleanly with header notice; filter by individual event and date.
Automatic card refunds2 per 5-minute cycleRemaining refunds dispatch safely on subsequent cycles using idempotency keys.
Overdue checkout hold sweep2 per minuteQueries Stripe session status before releasing places across subsequent minutes.

Straightforward one-year pricing — USD 30 / 100 / 200

Site licence USD 30/year · Ten-site licence USD 100/year · Unlimited sites USD 200/year. Localhost and preview domains (*.workers.dev, *.pages.dev) run free. Versions released during your paid year continue working forever, backed by an unconditional 30-day refund.

Coming soon: Eventual RSVP – Tickets is on its way to npm and the EmDash Registry. To order a licence now, write to support@eventual.rsvp.