Create Reservation Notification

10.33
Channel Connect
Reservations
SOAP API
Booking Solutions
OTA Integration

10.33 | July 13, 2024

Enhanced to support new functionality from the Support Custom Call Center Applications and Tokenization Support through Channel Connect enhancements.

Read more

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>
Child ElementAttributeDescription
SupplementalData SupplementalData element contains the template for the confirmation email that is sent for the current reservation.
Note: If this element is not included in the request with the specific template code, the email is sent using the default template.
 @NameThe email confirmation template code.
Type: String
Email Additional email address associated to the reservation for reservation communications.
Multiple Email elements are allowed.
Type: String

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>