TicketOpus

Security and trust

Operational trust should be visible, not implied

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

Security built into everyday work

Access

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 permissions
Records

Sensitive changes leave a trail

Refunds, permission changes, pricing edits, capacity overrides, and cancellations are recorded with who made them and when.

Explore the platform
Payments

Card details stay with Stripe

Guests enter card details in Stripe's secure payment form, so card numbers are not stored by TicketOpus.

Ask a security question

No online service can promise perfect security or uninterrupted availability. Our commitments are set out in the Terms of Service.

Access control

Your data stays with your business, and staff see only what their role allows.

  • Data kept separate for each business
  • Roles and permissions for every staff member, down to the locations they can see
  • A record of refunds, price changes, and permission changes
  • Merge duplicate customers, or erase a guest's personal data on request

Bookings and payments

Every booking, payment, and refund is recorded step by step.

  • Spots are held briefly during checkout so they are not sold twice
  • Every payment and refund is recorded against its booking
  • Outgoing messages and webhooks are retried if delivery fails

Questions before launch

Straight answers before you decide.

Can TicketOpus start with one workflow?

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.

Does TicketOpus support an existing website?

Yes. Add the booking widget to your current site, or build a new site with the TicketOpus website builder.

How should we evaluate a migration?

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.

Are all integrations live today?

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.