Ticket Validation is the verification process performed before an attendee is allowed to enter an event. Every QR code scan or manual ticket lookup passes through multiple validation checks to ensure that the ticket is genuine, belongs to the correct attendee, and is eligible for check-in.

Rather than relying solely on a QR code, Eventixa validates the associated attendee, booking, and ticket information before recording a successful check-in. This multi-step process helps prevent unauthorized access, duplicate entries, and invalid ticket usage.

Available in: Eventixa Pro

How Ticket Validation Works

Whenever a ticket is scanned or a ticket number is entered manually, Eventixa performs a series of validation checks.

The overall process is shown below.

Scan QR Code or Enter Ticket Number
        │
        ▼
Locate Ticket
        │
        ▼
Locate Attendee
        │
        ▼
Validate Booking
        │
        ▼
Validate Ticket Eligibility
        │
        ▼
Check Existing Check-In Status
        │
        ▼
Validate Event Occurrence
        │
        ▼
Check-In Approved or Rejected

Only after every validation step succeeds is the attendee checked in.

Ticket Identification

The first step is identifying the attendee’s ticket.

Eventixa supports two identification methods:

• QR Code
• Ticket Number (when manual lookup is enabled)

Both methods locate the same attendee record.

Example Ticket Number:

TKT-2026-000125

Once the ticket is identified, Eventixa retrieves the associated attendee and booking information.

Attendee Validation

After locating the ticket, Eventixa verifies that the attendee record exists.

This confirms that:

• The attendee is registered.
• The ticket belongs to a valid attendee.
• The attendee information can be used during check-in.

If no attendee record is found, validation fails.

Booking Validation

Each attendee must belong to a valid booking.

During validation, Eventixa verifies that:

• The booking exists.
• The attendee belongs to the booking.
• The booking is eligible for check-in according to your QR Check-In settings.

If booking validation fails, the attendee cannot be checked in.

Booking & Payment Requirements

Depending on your QR Check-In configuration, Eventixa can require a booking to be completed before allowing check-in.

When this option is enabled, the system verifies that the booking or payment satisfies the configured requirements before continuing.

This helps prevent attendees with incomplete registrations from entering the event.

Duplicate Check-In Detection

Before recording a new check-in, Eventixa checks whether the attendee has already been checked in.

If the attendee is already checked in:

• A second check-in is prevented.
• The attendee’s existing check-in status is preserved.
• Duplicate event entry is avoided.

This ensures accurate attendance records throughout the event.

Event Validation

Every ticket is linked to a specific event.

During validation, Eventixa confirms that the attendee’s ticket belongs to the correct event before recording the check-in.

This prevents tickets from being used for unrelated events.

Recurring Event Validation

For recurring events, validation includes an additional occurrence check.

Each ticket is associated with the specific occurrence selected during registration.

Example:

Weekly Coding Workshop

July 10 Ticket
        │
        ▼
✓ Valid for July 10

July 17 Ticket
        │
        ▼
✓ Valid for July 17

July 10 Ticket used on July 17
        │
        ▼
Validation Failed

This prevents attendees from using a ticket for a different occurrence of the same recurring event.

Successful Validation

When every validation check succeeds, Eventixa:

• Marks the attendee as Checked In.
• Records the check-in time.
• Records the staff member performing the check-in.
• Updates the attendee record.
• Adds the action to the attendee history.
• Records the activity in the related booking notes.

The attendee is then admitted to the event.

Validation Failures

A ticket may fail validation for several reasons.

Common validation failures include:

• Ticket cannot be found.
• Attendee record does not exist.
• Booking cannot be validated.
• Booking is not eligible for check-in.
• Attendee has already checked in.
• Ticket belongs to a different recurring event occurrence.

When validation fails, Eventixa does not update the attendee’s check-in status.

Relationship with Other Features

Ticket Validation is the central process used by multiple Eventixa features.

Feature	Purpose
QR Tickets	Provides the ticket and QR code used for validation.
QR Check-In	Initiates the validation process during event entry.
Bookings	Confirms booking eligibility.
Attendees	Updates attendee check-in records after successful validation.
Recurring Events	Verifies the attendee belongs to the correct occurrence.
Booking Notes	Records successful check-in activity.
Attendee History	Maintains a complete history of attendee entry and exit.

Validation Workflow

The following diagram summarizes the complete validation process.

QR Code / Ticket Number
          │
          ▼
Locate Ticket
          │
          ▼
Locate Attendee
          │
          ▼
Validate Booking
          │
          ▼
Validate Booking/Payment Eligibility
          │
          ▼
Already Checked In?
      │           │
     Yes          No
      │           │
      ▼           ▼
 Reject      Validate Event
                  │
                  ▼
      Validate Recurring Occurrence
                  │
                  ▼
          Check-In Approved

Security

Ticket Validation helps protect events from unauthorized access by ensuring that every attendee is verified before entry.

The validation process includes:

• Unique ticket identification.
• Individual attendee verification.
• Booking validation.
• Booking/payment eligibility checks.
• Duplicate check-in prevention.
• Recurring occurrence verification.
• Secure attendee record updates.

These checks work together to maintain accurate attendance records while reducing the risk of invalid or duplicate entries.

Best Practices

• Require completed bookings before allowing attendees to check in.
• Encourage attendees to present their QR tickets rather than manually entering ticket numbers.
• Test the validation process before the event begins.
• Use recurring event validation to ensure attendees enter the correct occurrence.
• Review attendee history and booking notes if validation issues occur during an event.

Tips

• Ticket Validation happens automatically whenever a QR code is scanned or a ticket number is entered—no manual verification is required.
• Validation checks more than just the QR code; it also verifies the associated attendee, booking, and event before approving entry.
• Duplicate scans are automatically detected, helping prevent multiple entries with the same ticket.
• For recurring events, validation ensures that attendees can only check in to the specific occurrence selected during registration.
• Ticket Validation is the foundation of Eventixa’s QR Tickets and QR Check-In system, ensuring secure and reliable event access.