Release Note - 29. June 2026

Sabre & Travelport – Custom PAR Title Structure

A new Unique PAR Title Structure field has been added to the Company Interface Setup for Sabre and Travelport+.

Open

This new option allows administrators to define a custom format for PAR Titles using standard and custom profile fields, enabling PAR naming conventions to better match customer requirements.

Examples include:

• {name} {firstname}

• {name}/{firstname}

• {name}/{firstname} {middlename}

• {genInternalEmployeeID}

When a custom PAR Title Structure is configured, it is used instead of the standard PAR generation logic.

Note:

• For Travelport+, automatic PAR numbering is not applied.

• Changes to the PAR Title Structure do not trigger automatic mass publishing. Any required profile updates must be published manually through the Profile Center.

New Standard Field: Payment Usage Type "Miscellaneous"

A new standard payment usage type, “Miscellaneous”, has been added to both Company and Traveler Profiles.

This new option is available alongside the existing payment usage types:

• Use as form of payment (Air Ticket)

• Hotel Guarantee

• Car Rental Guarantee

• Web Card

• Miscellaneous

The “Used by Traveler” setting is available for the new Miscellaneous payment usage type in Company Profiles, consistent with the existing payment usage types.

Additional updates include:

• The new field is available in Standard Field Customization.

• The new field is included in CSV Import and Export files

No standard mapping is provided for target systems. Customers can configure their own mappings if required.

Source Company:
miscPaymentCard.type,miscPaymentCard.number,miscPaymentCard.expiration
Source Traveler:
miscPaymentCardExtended.type,miscPaymentCardExtended.number,miscPaymentCardExtended.expiration

This enhancement allows payment cards to be assigned for miscellaneous payment purposes that do not fit into the existing guarantee or web card categories.

Agency Setup - Import actions

As preparation for a future enhancement of the Read from Profile functionality, a new Import Actions tab has been added to the agency setup. While the full Import Actions functionality is not yet available, the new configuration area is now in place.

Key benefits:

• Import mappings can be maintained separately from custom publish actions (COPY).

• When Import Actions become available, they will be used for profile imports instead of custom publish actions (COPY).

• Existing behaviour remains unchanged if no Import Actions are defined.

This enhancement lays the foundation for more accurate profile imports and improved control over data mapping. Further details will be provided in a future release announcement when the full Import Actions functionality becomes available.

Amadeus Tenzing V2 - new error message for invalid Frequent Flyer Numbers

The error message displayed when an invalid Frequent Flyer Number is detected during synchronization with Amadeus Tenzing V2 has been enhanced.

Previously, only a generic error message (FREQUENT TRAVELER NOT FOUND) was shown, making it difficult to identify which Frequent Flyer Number caused the issue when multiple memberships were stored in a traveler profile.

The enhanced error message now includes the relevant airline and Frequent Flyer Number returned by Amadeus, allowing users to quickly identify and correct the affected membership.

Example new error message:

FREQUENT FLYER NUMBER NOT FOUND (LH-992002333256008 [1])

New Credit Card Source – Unspecified Usage Type

A new credit card source, unspecifiedUsageCreditCards, has been added.

This source returns credit cards that are not assigned to any usage type, such as Hotel Guarantee, Car Rental Guarantee, Web Card, Rail Form of Payment, or Miscellaneous Payment, inlcuding if Use as Form of Payment (Air Ticket) is unchecked.

Source:
unspecifiedUsageCreditCards#.type,unspecifiedUsageCreditCards#.number,unspecifiedUsageCreditCards#.expiration

This enhancement provides additional flexibility for interface mappings and synchronization scenarios.

Sabre Source - Form of payment

A new source is available for mapping credit card details directly to the Sabre Form of Payment (FOP) field.

Please note that Read from Profile support is not available for this functionality.