Tickets and the Door, at Cost
Core has its own ticketing: sell tickets from the Portal at cost, check them at the door, offline if need be, and keep the buyer record in your own name.
What It Does
Commerce
Ticketing and payments, at cost.
Ticketing, built in
Presale, guest lists, refunds, voids and an offline door, run from Core.
Wallets
Tickets saved to the fan's iPhone with Apple Wallet. Google Wallet, the same for Android, is in build.
Payouts
Payments and payouts through Stripe Connect. You are the merchant of record.
Already on DICE or Eventbrite?
Planned: link out to DICE, Eventbrite or Ticketmaster events, or bring their data into Core.
In Use
Questions
- Can we sell tickets through the Portal?
- Yes: the Ticketing module sells tickets through Core Commerce and checks them at the door through Core Access. Fans get an event pass that shows valid, used or transferred.
- Can we stop people buying too many tickets?
- Yes: organisers set a per buyer cap, counted across account and payment method. A cap is not an automated purchase ban.
- How does entry work at the door?
- One scan per ticket is enforced at the database, and door checks work offline. At the door a human decides, and we never refuse entry automatically.

Membership
Applications, levels and access, reviewed by people and checked on every visit.More on Membership →- Integrations
Integrations
Exports, wallets, payments, music and messaging today; CRM and marketing tools next.More on Integrations → 
Fan CRM
A record per fan, built from taps and consent, with segments, campaigns and exports.More on Fan CRM →
Run It in Core
Already running TapTech, or in the beta?
Buying for a brand, a tour or a venue?
Order tags ↗Open a Portal ↗No account needed