Amusement Extension Overview
4 min
The Universal Amusement API extends the Universal Fraud API shared transaction model for admissions, attractions, events, and ticket package purchases.
Amusement Extension Model
The Universal Amusement API adds:
- Ticket Package Information
- Event Information
- Ticket Information
- Agency Information
- Insurance Information
- Activity Information
Note: See Amusement Complete Request Structuremm for the full path.
What Makes Theme Parks Different
Theme Parks transactions often rely on:
- Venue context (park/venue identifiers)
- Ticket counts and pricing (number of tickets, total ticket price, ticket currency)
- Package context (package ID/class/description)
- Per-ticket guest context (guest name, age classification, ticket class, annual pass flags)
These structures allow admissions and package purchases to be evaluated with the right contextual signals.
Hashing Requirements
The Amusement API follows the platform hashing rules. Fields designated as hash-required must be hashed before submission, including:
- giftCardNumber
- hashedPassword
See: Hashing RequirementsHashing Requirements (Constraint) and Accertify Hash AlgorithmAccertify Hash Algorithm (Reference).