How TixFin fits together
The dashboard, the shop, the TixFin app and the API, who uses which, and how plans work
TixFin is a few products on one set of data. A project (your organisation) holds events; each event has ticket types; every ticket sold, wherever it was sold, is checked at the same door against the same record.
| Product | Who uses it | For |
|---|---|---|
| Dashboard (beta.tixfin.com) | Organisers and their team | Everything except buying and scanning: events, tickets, shop, orders, invoices, team, crew, marketing |
| Shop (your subdomain) | Buyers | Finding events, choosing tickets and seats, paying |
| My tickets (in the dashboard) | Buyers with an account | Their tickets and QR codes, transfers, refunds, memberships |
| TixFin app (iOS, Android) | Door staff, crew, organisers on site | Scanning, offline check-in, Safety, shifts, today's figures |
| Partner API | Developers | Reading events, tickets and orders into your own systems |
The dashboard
Where you set up and run everything. The sidebar groups the areas by what you do: Home, Events & tickets, Sales, Customers & marketing, Operations, Project. You see only what your role and plan allow. Find your way in the dashboard · Organiser tasks

- Project switcher
- Sidebar area, e.g. Tickets
- Search… opens the command palette
- Star to pin an area
- Account menu
The shop
Each project gets a branded shop on its own subdomain. Buyers browse events, pick tickets (and seats for seated events), pay through your own payment provider, and get their tickets by e-mail and in My tickets. You design it under Events & tickets → Shop design. Shop · Buy tickets (for buyers)
The TixFin app
The app is for the people working the event, not for buyers. Door staff scan tickets, also offline; crew check in for shifts and read briefings; anyone with Safety can report an incident in one tap. Each person sees only the screens their role allows. Door & crew app
Roles and permissions
Access is a set of permissions per project, grouped into roles (Owner, Admin, Manager, Accountant, Crew Manager, Staff, or your own). A role decides which areas appear in the dashboard and which screens open in the app. For a one-off door helper, a temporary scanner scans without a personal account. Buyers are not project members; they see only their own tickets. Team and roles
Money
TixFin never holds your money. Buyers pay you through your own payment provider (Mollie, PayPal or Adyen), and the provider pays you out. TixFin charges you its plan and its per-ticket fee. Payments · Billing and plans
Plans
TixFin starts free. Higher plans add seatmaps, season subscriptions and more, and each paid ticket carries a fee set by your plan. Buyers pay no TixFin fee; payment processing is billed by your provider. Current plans and fees are on the pricing page. Details: Billing and plans · tixfin.com/pricing
Security and privacy
- Two-factor authentication is required to work inside a project; passkeys and e-mail codes are offered for sign-in (Account security).
- Every scan is checked against TixFin, so a copied QR code admits once. Scans made offline that clash are reported after the sync (Scan offline).
- Personal data is shown only to roles that need it, and administrative actions are logged.
- Invoices to your buyers can be downloaded as PDF, ZUGFeRD XML or XRechnung (Invoicing).
