Each business sees only its own data
Every booking, customer, and payment belongs to one business, and staff roles and permissions decide who can view or change it, down to the locations each role or person can see.
See team permissionsSecurity and trust
Each business's data is kept separate, staff see only what their role allows, sensitive changes are recorded, and card payments are handled by Stripe.
How we protect you
Every booking, customer, and payment belongs to one business, and staff roles and permissions decide who can view or change it, down to the locations each role or person can see.
See team permissionsRefunds, permission changes, pricing edits, capacity overrides, and cancellations are recorded with who made them and when.
Explore the platformGuests enter card details in Stripe's secure payment form, so card numbers are not stored by TicketOpus.
Ask a security questionNo online service can promise perfect security or uninterrupted availability. Our commitments are set out in the Terms of Service.
Your data stays with your business, and staff see only what their role allows.
Every booking, payment, and refund is recorded step by step.
Questions before launch
Yes. The platform is designed so an operator can begin with direct booking or another priority workflow and add connected capabilities as the operation matures.
Yes. Add the booking widget to your current site, or build a new site with the TicketOpus website builder.
Start with future bookings, catalog and schedules, customer records, payments and balances, integrations, domains, reporting, and the staff workflows that must work on launch day.
No. Stripe payments, the External API, webhooks, and SCIM directory sync are live. QuickBooks, Xero, OTA marketplaces, and Google Things to Do are not connected yet, so check with us about any connection your launch depends on.