Build the event.
General admission or reserved seating. Set the basics in the dashboard: name, description, dates, capacities, ticket types. Save as draft, publish when you’re ready.
What’s in the platform.
Built for organizers who need the essentials done well.
A focused set of features for selling tickets to events. No subscriptions, classes, season passes, marketing automation, or volunteer management. The platform does ticketing, and it does it well. If you need something you don’t see here, it’s probably not what we do.
§ Building the event
Build the event the way it needs to be sold.
The dashboard handles general admission events, reserved seating events, or a combination of both. Set up multiple dates, multiple price types per date, and ask buyers the questions you actually need answered at checkout.
Reserved seating with a built-in seat map editor.
Build your own seat maps with our visual editor. Sections, rows, seats, accessibility designations. No designer needed and no separate tool to learn. Buyers select seats visually at checkout.
Multiple dates per event.
One event listing, many showtimes. Each date has its own capacity, its own sales window, and its own sales report. Buyers see the dates that are still available; sold-out dates display as sold out.
Multiple price types.
Adult, child, member, student, early-bird – set as many price types as the event needs, per date. Each type counts against the same capacity.
Custom questions per event.
Collect dietary restrictions, t-shirt sizes, accessibility needs, party affiliations – whatever the event requires. Per-event, per-ticket, optional or required.
Event pages with your branding.
Your logo. Your colors. Your event description, set the way you wrote it. Buyers see the venue or organization, not the platform.
§ Selling tickets
Get from “interested” to “purchased” without losing the buyer.
Buyer experience is what determines whether a cart abandons or completes. Plumticket’s checkout is fast, fee-transparent from the first ticket selection, and supportable after the fact when something goes wrong.
Embedded checkout, on plumticket.com.
Buyers never leave your event page to pay. Stripe Elements handles the card form inline. No redirect to a third-party checkout, no “you’re now leaving” handoff.
Mobile-first checkout flow.
Most buyers will use a phone. The checkout is built for that first: large tap targets, one-thumb operation, no horizontal scrolling, no surprise overlays. It works on desktop too.
Fees shown upfront, not at the final step.
Buyers see the all-in price from the first ticket selection. No surprise fees added at checkout. Lower abandoned cart rates because the price doesn’t change.
§ At the event
Run the night.
The features that matter once the doors open. A built-in box office for at-the-door sales, and mobile ticket scanning that works on any phone without a separate app to provision in advance.
Built-in box office.
Sell tickets at the door from the same dashboard you used to set the event up. Card or cash, single tickets or batches. Box-office sales appear in the same reports as online sales.
Mobile ticket scanning.
Scan QR codes from any phone with a web browser. No app to install, no devices to ship, no licenses per scanner. Multiple staff can scan the same event simultaneously. Each scan logs who and when.
§ After the event
Reconcile, report, repeat.
The back-office side of ticketing. The part that determines whether you’ll run another event with us next month. Reports that export. Payouts that arrive. Refunds you can manage.
Sales window controls.
Set open and close times per event date. Or toggle sales on and off manually. Useful for early-bird windows, member-only pre-sales, and capping ticket availability when you’re close to capacity.
Per-event reports with CSV export.
Sales, fees, rebate, attendance, custom-question responses – all in one report per event. Export to CSV for accounting, custom analysis, or import into your own tools.
Automatic payouts to your bank.
Payouts run on Stripe’s standard schedule (typically two business days after the transaction) directly to the bank account on your Stripe Connect record. No manual withdrawals, no minimum balances, no requests to send.
Self-serve refunds.
Issue refunds from the dashboard. Partial or full, single ticket or whole order. The buyer is refunded through Stripe and notified by email. The transaction shows as refunded in your reports.
Team accounts with role-based permissions.
Invite team members to your organization with the access level they need. Admins manage events and refunds; staff can scan tickets and view sales reports without seeing financial details. One account per person, not one shared login.
Reviewed within 48 hours