Unique guest access
Invitation QR codes are unique to guest records rather than relying on a reusable public list.
Access, payments & settlement
Clear guest access. Traceable money. Fewer loose ends.
SecVite connects unique guest access, event-team roles, visible payment fees and the transaction settlement workflow in one event record.
A visible payment trail
Guests review the gift, ticket amount and service fee before confirming. Organisers receive reconciled event records.
Access by role
Check-in officers and event-team members get the tools for their work without needing the organiser's full account.
Offline resilience
Prepared check-in devices can keep validating guests when a crowded venue network disappears, then sync later.
How settlement works
Money should arrive with a record, not a mystery.
- 1
The guest confirms
The guest sees the ticket or gift amount and the flat 5% service fee before payment.
- 2
The payment is processed
Supported payments are processed through providers including Flutterwave where available and associated with the event transaction.
- 3
The transaction remains traceable
SecVite's settlement workflow keeps the payment associated with the event while provider and verification requirements are completed.
- 4
The event is settled
The verified balance is paid out subject to identity checks, disputes, refunds, chargebacks and external payment systems.
Responsibility boundaries
Security is a workflow shared by the organiser, SecVite and payment providers
No event tool can decide who belongs on a private guest list or guarantee the behaviour of a venue team. SecVite provides controlled records and role-based workflows; organisers still define the policy, and external providers handle parts of payment processing and verification.
The organiser decides
Who is invited, which responses need approval, who joins the event team, what refund or entry terms apply and who can resolve exceptions on the day.
SecVite keeps connected records
Unique invitations, guest status, team roles, check-in activity and supported event transactions remain associated with the event workflow.
External systems still matter
Payment methods, identity checks, provider availability, chargebacks and settlement timing can depend on third-party systems and regulatory requirements.
Before doors open
A safer setup is prepared, tested and understood
- ✓Remove team access that is no longer required and confirm who owns guest-policy exceptions.
- ✓Load the latest approved guest data on check-in devices and test the offline fallback.
- ✓Make ticket, gift, fee and refund information visible before guests are asked to pay.
- ✓Complete applicable organiser verification early enough to resolve questions before settlement is due.
Frequently asked questions
Does SecVite store card details?
Payment details are handled through the payment-processing flow rather than entered into the organiser's guest list. Guests see the amount and fee before they confirm a payment.
How are cash gifts settled?
Supported gifts move through SecVite's transaction and settlement workflow, with payout subject to verification and the payment provider's requirements.
Can every team member see financial information?
No. Event roles are designed to give team members the access they need for their job, such as gate check-in, without exposing unrelated organiser controls.
How are invitation QR codes controlled?
SecVite uses unique invitation QR codes connected to guest records, with an invitation-code fallback for legitimate arrivals.
Run your next celebration with SecVite
Creating and managing an event is free. Get SecVite and keep the whole event connected.