Legacy Travel 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 Travel Fraud API is intended for transactions where the purchase represents a travel itinerary that may include multiple components (air, lodging, rental, cruise, activities, agency, insurance), in addition to the shared core event model.
What Makes Travel Different
Travel transactions can be:
- Future-dated (book now, consume later)
- Multi-component (flight + lodging + rental + activities)
- Third-party booked (agency/OTA involvement)
The Travel API supports optional structures for:
- lodging reservations, guests
- car rental details
- cruise details
- activity/excursion details
- agency details
- insurance policy context
Hashing Requirements
The Travel 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).
