What selling a ticket cost the park before, what it would cost on a platform the park owns — pricing, fees, and hardware, side by side.
Through the 2023 season, this was the path a family took to buy a ticket — and it's the setup the park would return to by default when it reopens.
Every way a park can sell tickets online, and what each one takes off the top. Card processing (roughly 2.9% + 30¢) is the same for everyone — the real difference is what's stacked on top of it.
| This platformbuilt for the park | Attraction SaaSConvergence, ROLLER, CenterEdge… | Per-ticket platformse.g. TicketSpice | Marketplacese.g. Viator | |
|---|---|---|---|---|
| Software fee | $75/mo hosting — that's it | Quote-based — reported $300–$1,000+/mo | $0 / month | $0 / month |
| Per-ticket fee | $0 | Varies — often per-booking fees on top | $0.99 per ticket | ~20–30% commission |
| Support | Traded for season passes | Paid support plans | Email support | — |
| Card processing | Stripe, 2.9% + 30¢ | Via the vendor's gateway | ~3% + card fees | Built into the commission |
| Hardware | iPads + Stripe Reader S710 ($299) | Proprietary terminals & kiosks, sold or leased by the vendor | Bring your own | — |
| Contract | None — you own it | Typically annual, with setup fees | Month to month | Their terms |
| Guest data | Yours, in your database | Lives in the vendor's system | Exportable | Theirs — you get a manifest |
| Where checkout lives | chesapeakebeachwaterpark.com | The vendor's domain | Their hosted checkout | viator.com |
Sources and reported ranges are listed at the bottom of this page. Quote-based vendors don't publish pricing; the ranges shown are what operators report paying.
An illustration, not a forecast: say the reopened park sells 25,000 tickets online in a season at the current $22 weekend rate. Here's what each model takes off the top — on top of the card fees everyone pays.
Assumes ~25,000 online tickets at $22. Card processing (~2.9% + 30¢) applies equally in every scenario and is excluded from all three figures.
The staff-device screens are already built as clickable mockups — a front-gate register, a gate scanner, and a kitchen display. They run on ordinary iPads and tablets, with the Stripe Reader S710 handling cards. Try all three live →
Built in three phases, in the order the park actually needs them — selling first, running the park second, the gates last, timed to the reopening.
The chosen storefront design built for real: day tickets and season passes sold on the park's own domain, embedded Stripe checkout, guest accounts with "My Wallet," promo codes, and party inquiries. The park starts selling the moment this ships.
Park Manager: the dashboard, orders and refunds, customer profiles, the cabana map, pricing and promo controls, and the party pipeline — plus the staff learning system, so training and certifications are in place before seasonal hiring ramps up.
The Front Gate POS, QR gate scanner, and kitchen display running on iPads with Stripe Reader S710 terminals — built and installed close to opening day, so the gate crew trains on the real thing.
Each phase is quoted, built, and handed over on its own. Hardware (~$2,000 at retail) is purchased directly by the park with no markup. Hosting is $75/month, and ongoing software support is traded for season passes under a simple written agreement.
The park reopens after renovation with new slides, new capacity — and a fresh choice about what runs the front gate. This is the window to own the platform instead of renting it.
Read the full proposal