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 Create Reservation Notification response 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>

CBE Support Pass-thru Payment Methods (FEA83429)

The Channel Connect API has been enhanced to allow a Custom Booking Engine (CBE) to send the pass-through payment methods.

The following is a partial sample response when a pass-through payment method is successfully added:

 <OTA_HotelResNotifRS>
 	...
	<HotelReservations>
		<HotelReservation>
			...
			<ResGlobalInfo>
				...
				<Guarantee>
					<GuaranteeDescription Name="PASS-THRU PAYMENTMETHOD">
						<Text>CODE</Text>
					</GuaranteeDescription>
				</Guarantee>
			</ResGlobalInfo>
		</HotelReservation>
	</HotelReservations>
</OTA_HotelResNotifRS>

Loyalty Accrual Indicator (FEA95383)

Loyalty accrual details have been added to the reservation response.

Sample partial XML response:

<OTA_HotelResNotifRS>
	<HotelReservations>
		<HotelReservation>
			...
			<RoomStays>
				<RoomStay>
					...
					<RatePlans>
						<RatePlan RatePlanCode="RateCode"
						          RatePlanName="Rate Name"
						          AccrualIndicator="true"
						          AccrualTypeCode="ACCRUAL1"
						          AccrualTypeName="ACCRUAL1 name"
						          PriceViewableInd="true">
							...
						</RatePlan>
					</RatePlans>
				</RoomStay>
			</RoomStays>
			...
		</HotelReservation>
	</HotelReservations>
</OTA_HotelResNotifRS>

Support Custom Call Center Applications (FEA92115)

Enhancements were made to enable Call Center applications, via the Property Direct channel, to make use of the Channel Connect API for their implementations. 

When booking or modifying the reservation, the user can add additional email addresses. They are included in the WrittenConfInst/Email element. Any reservation communications will be sent to the additional email addresses on the reservation, provided that the guest's main email address is included in the request.

These email addresses will be associated to the reservation and not to any guest profile.

<OTA_HotelResNotifRQ PrimaryLangID="en" EchoToken="echo" ResStatus="Commit" xmlns="http://www.opentravel.org/OTA/2003/05">
	…
	<HotelReservations>
		<HotelReservation RoomStayReservation="true">
			…
			<WrittenConfInst>
				<SupplementData Name="CodeTemp"/>
				<Email>Additional1@sabre.com</Email>
				<Email>Additional2@sabre.com</Email>
			</WrittenConfInst>
		</HotelReservation>
	</HotelReservations>
</OTA_HotelResNotifRQ>

Tokenization Support through Channel Connect (FEA53395)

Configure in Administration > Hotel > Payment Processing Settings > Tokenization Settings
Configure in Manage > Reservation > Credit Card Summary

In an effort to enhance our security, Channel Connect and SynXis CRS improved the existing tokenization support. Prior to this release, only clear Credit Card details were accepted as part of the reservation message in Channel Connect. Starting with this release, tokens are accepted as part of reservations through Channel Connect and stored accordingly in SynXis CRS.

The following partial request example includes the tokenized credit card details in the CardNumber element. When a non-empty value is provided in the PaymentCard/@CardNumber attribute, the reservation is not processed. An error is returned which indicates that the credit card details must be included in either PaymentCard/@CardNumber or PaymentCard/CardNumber.

<ResGlobalInfo>
	<Guarantee>
		<GuaranteesAccepted>
			<GuaranteeAccepted>
				<PaymentCard CardCode="VI" ExpireDate="0919" SeriesCode="123">
					<CardHolderName>Card Holdername</CardHolderName>
					<CardNumber Token="AEGHV234AUD54367"/>
				</PaymentCard>
			</GuaranteeAccepted>
		</GuaranteesAccepted>
	</Guarantee>
	…
</ResGlobalInfo>

The following is a partial response example:

<ResGlobalInfo>
	<Guarantee>
		<GuaranteesAccepted>
			<GuaranteeAccepted>
				<PaymentCard CardType="1" CardCode="VI" CardNumber="XXXXXXXXXXXX4367" ExpireDate="0919">
					<CardHolderName>Card Holdername</CardHolderName>
					<CardNumber Token="AEGHV234AUD54367"/>
				</PaymentCard>
			</GuaranteeAccepted>
		</GuaranteesAccepted>
	</Guarantee>
	…
</ResGlobalInfo>