TicketPOS operations

Ticket lifecycle

A typical TicketPOS ticket moves through these stages:

Issued – a ticket has been created for a player.
Active – the ticket is valid for entry.
Used – a single-use ticket has been redeemed at a gate.
Revoked / Expired – the ticket is no longer valid.

You control these transitions via events on the API object in AG | TicketPOS.

Selling or granting tickets

Ticket creation can happen in different ways:

Purchased by the player via a UI.
Granted as a reward or staff permission.
Imported from an external system.

Example pattern to grant a ticket:

local TicketPOS = workspace["AG | TicketPOS"]
local API = TicketPOS:WaitForChild("API")

local function giveVipTicket(player)
  local createTicketEvent = API:WaitForChild("CreateTicket")

  createTicketEvent:Fire(player, {
    eventId = "concert_2025_07_01",
    ticketTypeId = "vip",
  })
end

Gate checks

Gates decide whether a player can pass based on their tickets. Example pattern from a server script attached to a door or zone:

local function canEnter(player, eventId, requiredTicketType)
  local checkTicketEvent = API:WaitForChild("CheckTicket")
  local result = checkTicketEvent:Invoke(player, {
    eventId = eventId,
    ticketTypeId = requiredTicketType,
  })

  -- `result.allowed` and `result.reason` are example fields
  return result and result.allowed, result and result.reason
end

You can then open doors or teleport players based on the result.

Revoking access

Sometimes you need to revoke a ticket:

Player refunded.
Moderation action.
Event cancelled.

Example pattern:

local function revokeTicketsForPlayer(player, eventId)
  local revokeEvent = API:WaitForChild("RevokeTickets")

  revokeEvent:Fire(player, {
    eventId = eventId,
  })
end

The exact event names and payloads depend on your implementation; use these examples as a pattern and align them with your actual API object.

Operational best practices

Log ticket creation and revocation so you can audit who had access.
Use clear messages when access is denied at a gate.
Combine TicketPOS with Dynaban risk scores to deny access for high-risk players before they reach sensitive areas.

Overview

RestaurantPOS

TicketPOS

EasyAPI (Roblox Lua)

Ticket lifecycle

Selling or granting tickets

Gate checks

Revoking access

Operational best practices

​Ticket lifecycle

​Selling or granting tickets

​Gate checks

​Revoking access

​Operational best practices

Ticket lifecycle

Selling or granting tickets

Gate checks

Revoking access

Operational best practices