Define each ticket type
Name the access, date, age rule or seating category attached to every tier. Clear differences reduce support requests and make scanning decisions easier at the gate.
Event ticketing
Sell tickets without surprising anyone at checkout
Set a ticket price and keep the stated price. The current standard 5% service fee is shown to the buyer before confirmation, and payment then moves through SecVite's settlement workflow.
Fees that appear at checkout cost you the sale
Ticket buyers abandon checkouts over charges they were not told about, and organisers who absorb the fee quietly lose margin on every seat. SecVite shows the fee, names it, and puts it on the buyer rather than skimming your price — so the number you set is the number you receive.
What you gain
You keep the ticket price
Set a ticket at any price and receive it in full. The 5% is added on top at checkout, so your pricing decisions are not quietly eroded.
Buyers see the breakdown
The fee is itemised before confirmation, so nobody discovers it later on a bank statement.
A traceable settlement workflow
Ticket revenue remains associated with the event through payment processing and settlement.
Tickets are entry passes
A paid ticket carries a unique QR code, so ticketed events can use the same offline-capable gate workflow.
A simple workflow
How it works
- 01
Create your ticket types
Set the price and how many are available. Free events stay free — there is no charge to create or run them.
- 02
Share and sell
Buyers use the payment methods available at checkout and see the applicable service fee before they confirm.
- 03
Scan and settle
Each ticket is scanned at the gate like an invitation, and revenue settles from escrow after the event with a reconciled statement.
What changes in practice
| The job | Typical manual setup | With SecVite |
|---|---|---|
| Service fee | Discovered at checkout | Itemised before confirming |
| What you receive | Price minus the fee | The full ticket price |
| Payout | Immediate, unprotected | Escrow until after the event |
Before tickets go on sale
Set expectations at the same time as the price
A good ticket page answers more than the amount due. Buyers should understand what the ticket admits, which terms apply and what they need at the entrance before they reach checkout.
Publish change and refund terms
State what happens if a buyer cannot attend or the event changes. SecVite records the transaction, but the organiser still needs clear event-specific terms.
Connect sales to capacity
Set quantities against the real venue plan and review sales alongside guest access. Revenue targets should not quietly create an entrance or safety problem.
Explore the connected workflow
Frequently asked questions
Who pays the ticketing fee?
The buyer. A flat 5% is added at checkout and shown before they confirm, so you receive the full ticket price.
When do I receive ticket revenue?
Payout follows the event settlement workflow and depends on successful verification and the external payment provider.
Are free events really free?
Yes. Creating an event, sending invitations, collecting RSVPs and running QR check-in cost nothing.
What payment methods can buyers use?
The available methods are shown in the payment flow and are processed through SecVite's payment provider.
How is repeat entry handled?
Each ticket carries a unique QR code and check-in activity is recorded against the ticket's guest record.
Turn this plan into a real event
Start with Atlas on WhatsApp, then manage every guest and event-day detail in SecVite.