--- title: Legacy Theme Parks API Overview slug: legacy-fraud-apis/legacy-theme-parks-api-overview createdAt: 2026-03-10T14:50:53.558Z --- ::::ExpandableHeading ### **Topic type: Concept** :::hint{type="warning"} **Purpose**: Legacy Theme Parks Fraud API overview, differences, and hashing requirements. **Audience**: API integrators and client developers. **Applies to**: Legacy Theme Parks clients implementing via API. **Does not apply to**: Universal APIs, any other industry, or theme parks clients who opt for a non-API integration. ::: :::: :::hint{type="info"} ******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 Requirements](docId\:yuGHwVL8eOn7vCgSwPcd3)** (Constraint) and **[Accertify Hash Algorithm](docId\:rKIK1Lb6EUUWsz3sxPCe-)** (Reference). ## Field Reference ::::LinkArray{contentSource="CUSTOM"} :::LinkArrayItem{headerType="IMAGE" headerImage="https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/sAIDzfcJBc4IwRRbre8Pl-20260326-200546.png"} [US Theme Parks Fields](docId:43CHsE3PKL5DB_Z-JIpqm) ::: ::::