Pass Through Point Redemption (FEA90497)

For hotel chains using their own Custom Booking Engine (CBE), the ability to make point redemption reservations directly with their Customer Relationship Management (CRM) vendor and communicate the redemption information to the PMS is crucial for supporting the loyalty program and enhancing the overall guest experience. SynXis can receive information from the CBE that a redemption has occurred and will store it and pass information to the PMS.

HTNG primary reservation delivery will be enhanced to communicate the following redemption details for points redemption bookings.

• ProgramName - Loyalty program 
• MemberNumber - Member number
• ID - Award number
• ID_Context - Award type
• Total points redeemed
• RedemptionCash - Total cost of booking not covered by points for points and cash redemptions 

<RoomStay>
	...
	<Guarantee GuaranteeCode="GCC"
	           GuaranteeType="GuaranteeRequired">
		<GuaranteesAccepted>
			<GuaranteeAccepted>
				<LoyaltyRedemption MemberNumber="MEMBERSHIPNUMBER"
				                   ProgramName=" LOYALTYPROGRAMCODE"
				                   RedemptionQuantity="10000">
					<LoyaltyCertificate ID="AWARDNUMBER"
					                    ID_Context="AWARDTYPECODE"/>
				</LoyaltyRedemption>
			</GuaranteeAccepted>
		</GuaranteesAccepted>
		<GuaranteeDescription>
			<Text>Hotel requires credit card guarantee</Text>
		</GuaranteeDescription>
	</Guarantee>
	<Total CurrencyCode="USD"
	       AmountBeforeTax="100.00">
		<Taxes Amount="0.00"
		       CurrencyCode="USD"/>
		<TPA_Extensions>
			<PointsRedemptionInfo CurrencyCode="USD"
			                      RedemptionCash="100.00"/>
		</TPA_Extensions>
	</Total>
	...
</RoomStay>

HTNG Reservation Delivery - Support Additional Service Pricing Types and Consolidation (FEA92562)

SynXis HTNG has been enhanced to provide flexibility in how package and SRS order items are communicated in the reservation message. This empowers Sabre customers and partners to customize their integrations and optimize the functionalities supported between systems.

SynXis HTNG now supports the option to communicate various service pricing types in the reservation message. This allows consuming systems to use this field to recognize how the service item should be applied to the stay.

Prior to this enhancement, SynXis HTNG only supported “Per use” as a service pricing type. With this enhancement and when configured in SynXis to send the new pricing types in the integration, the following additional service pricing types are supported:

• Per stay
• Per night
• Per person
• Per person per night

To further enhance how service items can be communicated and to provide greater flexibility in the SynXis HTNG interface, the option to consolidate service items in the reservation message has also been added. Prior to this enhancement, service items were always provided as single line items for each night of the stay they applied. When enabled, the consolidation logic will combine like service items with consecutive dates into a single service element.

Both of the new SynXis HTNG reservation format behaviors are configurable by independent integration attributes and require certification to adopt.

Identifier for FinTech payment methods (FEA92354)

When the guest’s reservation has a Fintech Provider stored as the Fintech Payment Provider in the reservation and the CC used is for Guarantee, then the Fintech Provider code will be passed in the / HotelReservations / HotelReservation / RoomStays / RoomStay / Guarantee / GuaranteesAccepted / GuaranteeAccepted / PaymentCard / TPA_Extensions section:   

• TPA_Extensions/ TPA_Extensions/FintechPaymentProvider 
• FintechPaymentProvider/@Code - Fintech Provider code (10 characters max) 

Example:

<Guarantee GuaranteeCode="GCC"
           GuaranteeType="GuaranteeRequired">
	<GuaranteesAccepted>
		<GuaranteeAccepted>
			<PaymentCard CardType="1"
			             CardCode="VI"
			             CardNumber=" XXXXXXXXXXX2111"
			             SeriesCode="123"
			             ExpireDate="1225">
				<CardHolderName>TESTBOOKER</CardHolderName>
				<TPA_Extensions>
					<FintechPaymentProvider Code="FLEXPAY"/>
				</TPA_Extensions>
			</PaymentCard>
		</GuaranteeAccepted>
	</GuaranteesAccepted>
	<GuaranteeDescription>
		<Text>Hotel requires credit card guarantee</Text>
	</GuaranteeDescription>
</Guarantee>  

When the guest’s reservation has a Fintech Provider stored as the Payment Provider in the reservation and the CC used is for Deposit, then the Fintech Provider code will be passed in the / HotelReservations / HotelReservation / RoomStays / RoomStay /DepositPayment/ GuaranteePayment / AcceptedPayments / AcceptedPayment / PaymentCard / TPA_Extensions  section:  

• TPA_Extensions/ TPA_Extensions/FintechPaymentProviderFintechPaymentProvider/@Code - Fintech Provider code (10 characters max) 

Example:

<DepositPayments>
	<GuaranteePayment>
		<AcceptedPayments>
			<AcceptedPayment PaymentTransactionTypeCode="reserve">
				<PaymentCard CardType="1"
				             CardCode="VI"
				             CardNumber="XXXXXXXXXXX2111"
				             ExpireDate="XXXX">
					<CardHolderName>TestName TestSurname</CardHolderName>
					<TPA_Extensions>
						<FintechPaymentProvider Code="FLEXPAY"/>
					</TPA_Extensions>
				</PaymentCard>
			</AcceptedPayment>
		</AcceptedPayments>
		<AmountPercent Amount="636.50"
		               CurrencyCode="USD"/>
		<Deadline OffsetTimeUnit="Day"
		          OffsetUnitMultiplier="0"
		          OffsetDropTime="AfterBooking"/>
	</GuaranteePayment>
</DepositPayments> 

Include VAT Information in Reservation Delivery (FEA91049)

SynXis CRS hosts functionality to capture VAT Billing Detail information on reservations made on SynXis Booking Engine (SBE) and SynXis Voice Agent (SVA). To promote automation and on property operational efficiency, SynXis HTNG reservation delivery to PMS integrations has been enhanced to include this information downstream. The information will be included in reservation messages whenever the details are present on a reservation in SynXis CRS.

VAT Billing details are not available in HTNG Alt Res Delivery to secondary endpoints.

Example: OTA_HotelResNotifRQ xml snippet (See full specification for official use case definitions)

<HotelReservation>
	...
	<TPA_Extensions>
		...
		<BillingInformation>
			<VAT CompanyName="VatCompanyName"
			     VATNumber="123456789">
				<Address>
					<AddressLine>VatAddress1</AddressLine>
					<AddressLine>VatAddress2</AddressLine>
					<AddressLine>VatAddress3</AddressLine>
					<CityName>VatCity</CityName>
					<PostalCode>11111</PostalCode>
					<CountryName>US</CountryName>
				</Address>
				<Telephone PhoneTechType="1"
				           PhoneNumber="1-111-111-1111"
				           FormattedInd="false"
				           DefaultInd="false"/>
				<Email>VatEmail</Email>
			</VAT>
		</BillingInformation>
		...
	</TPA_Extensions>
	...
</HotelReservation>

Tracking an External System User’s API transactions (FEA92169)

The SynXis APIs have been enhanced so customers can now provide additional user metadata that will be tracked in SynXis CRS. This metadata will allow visibility into which users from the customer’s application (external system) initiated the API transactions to SynXis CRS.

A new optional parameter (ApplicationUserMetaData) is now supported in the HTTP headers for inbound requests to SynXis CRS, as well as in the header of the token request for use with REST APIs. The ApplicationUserMetaData parameter has a maximum size of 60 characters.

If ApplicationUserMetaData was provided in any reservation transactions via API, the value will be included in reservation delivery OTA_HotelResNotifRQ message as ResID_Type="3". The following partial XML sample shows how the metadata will be communicated:

<HotelReservations>
	<HotelReservation>
		...
		<ResGlobalInfo>
			<HotelReservationIDs>
				...
				<HotelReservationID ResID_Type="3"
				                    ResID_Value="ABCD456782"
				                    ResID_Source="Corporation representative"
				                    ForGuest="false"/>
			</HotelReservationIDs>
		</ResGlobalInfo>
		...
	</HotelReservation>
</HotelReservations>

Loyalty Accrual Indicator (FEA95383)

For chains that allow guests to earn benefits such as points or free nights based on specific rates booked, the SynXis CRS now supports the ability to configure and apply such policies to rates. The SynXis CRS previously supported the ability to configure if a rate is eligible for accrual. This functionality has been expanded to allow the association of a specific accrual benefit a guest would earn.

A new configuration “Include Accrual Details in Reservation Delivery (HTNG Only)” attribute has been added in SynXis CRS to control if the accrual type will be included in the HTNG reservation message, if associated to the rate.

The following is a sample partial XML:

<HotelReservations>
	<HotelReservation>
		...
		<TPA_Extensions>
			...
			<AccrualDetails AccrualIndicator="True"
			                AccrualTypeCode="Points"
			                AccrualTypeName="Earn Points"/>
		</TPA_Extensions>
	</HotelReservation>
</HotelReservations>

Indicate Tax Rules on Rate Plans (FEA90212)

Reservation Delivery to the PMS has been enhanced to include a comment regarding any Exempt or Pre-Paid taxes.

Reservation Delivery to any secondary endpoints (non-PMS) will not include any Exempt or Pre-Paid tax comments.

The following attributes have been added to the Administration > Integration > Integration Detail > Attributes page to control whether the comments are included:

• Include Exempt Taxes in Comments
• Include Pre-paid Taxes in Comments

Sample partial XML for Exempt taxes:

<OTA_HotelResNotifRQ>
	...
	<HotelReservations>
		<HotelReservation>
			...
			<RoomStays>
				<RoomStay>
					...
					<Comments>
						<Comment GuestViewable="false">
							<Text>~EXEMPTTAXES RBT(0.00), RLT(0.00) EXEMPTTAXES~</Text>
						</Comment>
					</Comments>
				</RoomStay>
			</RoomStays>
			...
		</HotelReservation>
	</HotelReservations>
</OTA_HotelResNotifRQ>

Sample partial XML for Pre-Paid taxes:

<OTA_HotelResNotifRQ>
	...
	<HotelReservations>
		<HotelReservation>
			...
			<RoomStays>
				<RoomStay>
					...
					<Comments>
						<Comment GuestViewable="false">
							<Text>~PREPAIDTAXES RBT(45.00), RLT(30.00) PREPAIDTAXES~</Text>
						</Comment>
					</Comments>
				</RoomStay>
			</RoomStays>
			...
		</HotelReservation>
	</HotelReservations>
</OTA_HotelResNotifRQ>

HTNG - Support Child Ages (FEA60440)

SynXis HTNG reservation messages can support child ages included on reservations in reservation delivery to integrating systems, and in reservation synch to SynXis CRS. Automatically integrating child age breakdowns between SynXis CRS and integrating systems provides an opportunity to improve operational efficiency by removing the task of manually aligning the ages of the children between systems.

Configuration to enable child age breakdown in HTNG reservation delivery and reservation synch is defaulted to not include the information. Integrating systems must support child ages functionality prior to enabling the setting.

SynXis HTNG integrating systems wishing to consume/exchange child ages in reservations with SynXis CRS must be certified.

Example: Reservation Including Children with Ages (Partial)
This partial use case shows a reservation with child ages stored. Two Room Reservation includes 2 Adults and 4 Children. Child 1 is 1 years old, Child 2 is 1 years old, Child 3 is 2 years old, Child 4 is 6 years old.

<GuestCounts IsPerRoom="false">
	<GuestCount AgeQualifyingCode="10" Count="2"/>
	<GuestCount AgeQualifyingCode="8" Count="4"/>
	<GuestCount AgeQualifyingCode="8" Count="2" Age="1"/>
	<GuestCount AgeQualifyingCode="8" Count="1" Age="2"/>
	<GuestCount AgeQualifyingCode="8" Count="1" Age="6"/>
</GuestCounts>