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_HotelResModifyNotifRQ 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_HotelResModifyNotifRQ>

The ability to Reinstate Canceled Reservations was also added to the Channel Connect API for the specific use with the Property Direct channel only. To reinstate a previously canceled reservation, the @ResStatus="Reinstate" must be included in the request. In the case of reinstatement, modification requests cannot contain any sections of the message which detail reservation information other than the information needed to identify the reservation to reinstate, like in the following example.

The @HotelCode attribute includes the hotel ID identifying the hotel to search for the existing reservations. When an existing reservation is not found, the reinstatement request is rejected.

• The reinstatement cannot be performed on a reservation that was not previously canceled.
• Canceled reservations with a departure date in the past cannot be reinstated.
• Canceled reservations which used any type of loyalty redemption cannot be reinstated.

Note: The user requesting the reinstatement must have the "Can Reinstate Canceled Reservations" Access Point assigned.

When a canceled reservation is reinstated, the reservation status goes back to confirmed. When a reservation response is returned for a reinstated reservation, it looks identical to a reservation that was never canceled.

<OTA_HotelResModifyNotifRQ EchoToken="12345" ResStatus="Reinstate" xmlns="http://www.opentravel.org/OTA/2003/05">
	<POS>
		<Source>
			<RequestorID ID="2500" ID_Context="Synxis">
				<CompanyName Code="CODE"/>
			</RequestorID>
		</Source>
	</POS>
	<HotelResModifies>
		<HotelResModify>
			<UniqueID Type="14" ID="61028WT000193" ID_Context="CrsConfirmNumber"/>
			<Verification>
				<TPA_Extensions>
					<BasicPropertyInfo HotelCode="12345"/>
				</TPA_Extensions>
			</Verification>
		</HotelResModify>
	</HotelResModifies>
</OTA_HotelResModifyNotifRQ>

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>