Travel Extension Overview
The Universal Travel API extends the Universal Fraud API shared transaction model for multi-component travel purchases.
Travel transactions may include combinations of flights, lodging, vehicle rentals, cruises, activities, agency information, and insurance information within a single request.
Travel Extension Model
The Universal Travel API may extend the shared transaction structure with:
- Flight Information
- Lodging Information
- Car Rental Information
- Cruise Information
- Activity Information
- Agency Information
- Insurance Information
Note: See Travel Complete Request Structuremm for the full path.
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).