Legacy Theme Parks API Overview
Legacy API Notice: This API is part of the Legacy Fraud API framework and is maintained for compatibility with existing implementations.
New integrations should use the Universal Fraud APIs instead.
The Universal Fraud APIs provide:
- A shared core transaction model
- Consistent request and response contracts
- Industry-specific extensions
- Unified documentation and onboarding
- Ongoing feature investment
Use this Legacy API documentation only if:
- You are maintaining an existing Legacy Fraud API integration.
- You have not yet completed migration to Universal Fraud APIs.
- Accertify has specifically directed your implementation to remain on the Legacy API framework.
For new implementations, start with Universal Fraud APIs Overview.
The Theme Parks Fraud API supports transactions involving theme park admissions and packages, built on the shared core model and extended with admissions/ticket package context.
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 Retail 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).
