Making a Hotel Booking

4.7.2 Making a Hotel Booking

Sabre sends information to Conferma during the hotel segment sell process. If Conferma approves the virtual form of payment, Sabre generates the hotel sell request with card details (provided by Conferma) from the issuer.

Payment Instructions

Payment instructions must be added under SpecialInstructions in the request. This field is mandatory for VCN forms of payment. The system will then retrieve payment instructions stored in the special information field within the hotel sell request.

If information is not present in the hotel sell request, an error response will be returned.

VCN Information

A maximum of 18 alpha-numeric characters can be used as a VCN form of payment:

Example – Virtual Card Account Code – UpdateReservationRQ

<ns8:OpenReservationElement id="13" type="FP">
<ns9:FormOfPayment migrated="false">
<ns9:VirtualCard>
<ns9:CustomerAccountCode>SABREAIRONE</ns9:CustomerAccountCode>
</ns9:VirtualCard>
</ns9:FormOfPayment>
</ns8:OpenReservationElement>

Customer Email Address

Including the customer's email address is optional. The system will verify if a customer email address is present. If present, the information will be sent to Conferma. From there, the system will verify the hotel sell request and the PNR associated with the customer's email address.

Email Address Hierarchy

The lead guest's email address will be present in the hotel segment's details.
The email address in the PE field should match the lead guest name (first occurrence).
If the email address for the lead guest name is not found, send the request without the customer email the address.

Example – Customer Email and Special Instruction – UpdateReservationRQ

<ns9:Lodging>
<ns9:ResGlobalInfo>
<ns9:BookingInfo RequestorID="12345678" CorpDiscount="CD1234567" PromotionalCode="XJKGHLDE" Email="abctravel@agency.com">
<ns9:BookingKey>24c5359f-50c7-4805-84cf-a1ebf4ec2df6</ns9:BookingKey>
<ns9:HotelReservationIds>
<ns9:HotelReservation Id="PNR12345" Type="24"/>
</ns9:HotelReservationIds>
</ns9:BookingInfo>
<ns9:HotelInfo HotelCode="Hotel Code" HotelName="Hotel Name">
<ns9:LocationInfo>
<ns9:Contact Fax="+441614453941"/>
</ns9:LocationInfo>
</ns9:HotelInfo>
<ns9:StayDateRange StartDate="2019-10-01" EndDate="2019-10-03"/>
<ns9:Total AmountAfterTax="232.12" CurrencyCode="USD"/>
</ns9:ResGlobalInfo>
<ns9:Rooms>
<ns9:Room SegmentNumber="1" NonSmoking="true" BedTypeCode="5" AccessibilityInformation="1" RoomIndex="1">
<ns9:Guests>
<ns9:Guest Type="10" Email="customer@email.com" Age="72" Index="1" LeadGuest="true" FrequentFlyerNumber="FLY123450" LoyaltyId="LOY123450" Title="JCJUD" FirstName="OFDXVT" LastName="OWKBWJ">
<ns9:Contact Phone="767738386388" Mobile="027560841"/>
</ns9:Guest>
</ns9:Guests>
<ns9:RoomDescription Name="ADVANCE PURCHASE - NO REFUNDS">
<ns9:Text>ADVANCE PURCHASE - NO REFUNDS</ns9:Text>
</ns9:RoomDescription>
<ns9:RatePlan RatePlanCode="123" RatePlanType="24"/>
</ns9:Room>
</ns9:Rooms>
<ns9:SpecialInstructions>
<ns9:SpecialInstruction>Segment special instruction<ns9:SpecialInstruction>
</ns9:SpecialInstructions>
<ns9:PaymentInformation Type="DEPOSIT">
<ns9:FormOfPaymentReference newRef="13"/>
</ns9:PaymentInformation>
<ns9:POS>

PNR Information at Segment Sell

The hotel segment will contain the VCN as the form of payment and the PNR will be updated to include the Deployment ID:

PNR Example

1 HHL HX HK1 MIA IN20SEP Q-OUT22SEP 2NT 54937 H /DCHX

AMPTON INN MIAMI 1A0DLV4 -1/ 149.00USD/CMN-C/CMT-COMMISSIONAB

LE/TAC-10.00 PCT/G*VCNSABREONE-HOTEL RES PRO1122/C72H/SI-INCLUD

E INTERNET-CF- 83814146

Agencies with PNAPNR-ON (Use Passenger Association and New FOP field)**

The VCN and Deployment ID are included in the *FOP field. If the VCN is not present in the *FOP field, it will be added with Use Type Hotels. If the VCN is already present in the *FOP field, the Deployment ID will be added under the existing form of payment:

Example – Host Display

New VCN FOP

*FOP«                                                           
FORM OF PAYMENT          
  1. VIRTUAL CARD TYPE   
     *VCNSABREAIRONE     
                                   UHL                           
     DEPLOYMENT ID: 10259127

Existing VCN FOP_

*FOP«                                                           
FORM OF PAYMENT         
  1. VIRTUAL CARD TYPE  
     *VCNSABREAIRONE    
     DEPLOYMENT ID: 0001122333    DOC:0012233449922
     DEPLOYMENT ID: 10259127

Agencies with PNAPNR-OFF (Passenger Association is not active)

The system will add a historical remark with the Deployment ID:

Example – Host Display

*P5H«
15.H-*VCNSABREAMEX DEPLOYMENTID 10136274

PNR Information at COMMIT

When the reservation is completed and the hotel booking is successful, the confirmation number and status of the Deployment ID will be added to the PNR.
If the hotel booking is denied, the system will remove the Deployment ID and will send a cancel notification to Conferma.
A pending status is not valid when using VCN FOP; the reservation must be confirmed at ET to be able to continue. If the booking receives a pending (PN) status, that means that the reservation is not confirmed on the hotel side. The system will then remove the Deployment ID and will send a cancel notification to Conferma.

Storage of Confirmation Code

PNRPNR-ON

*FOP«                                                          
FORM OF PAYMENT           
  1. VIRTUAL CARD TYPE    
     *VCNSABREAIRONE      
     DEPLOYMENT ID: 10259127  CONF:  5899115952085

Example – UpdateReservationRS

<or114:FormOfPayment migrated="false">
<or114:VirtualCard>
<or114:CustomerAccountCode>VISAMULTI</or114:CustomerAccountCode>
<or114:Transactions>
<or114:Transaction index="1" paymentReferenceNumber="01411567083634295819">
<or114:LastUpdateTime>2019-08-29T08:00:39</or114:LastUpdateTime>
<or114:DeploymentId>10724395</or114:DeploymentId>
<or114:ConfirmationNumber>EAN1234</or114:ConfirmationNumber>
</or114:Transaction>
</or114:Transactions>
</or114:VirtualCard>
</or114:FormOfPayment>

PNRPNR-OFF

*P5H«
15.H-*VCNSABREAMEX DEPLOYMENTID 10136274                  
16.H-*VCNSABREAMEX CONF/1234567890

Example – UpdateReservationRS

<stl19:Remarks>
<stl19:Remark index="1" id="48" type="HS" elementId="pnr-48">
<stl19:RemarkLines>
<stl19:RemarkLine>
<stl19:Text>*VCNAMEXMULTI DEPLOYMENTID 10724532</stl19:Text>
</stl19:RemarkLine>
</stl19:RemarkLines>
</stl19:Remark>
</stl19:Remarks>

Deployment ID Status

  3.H-*/SVP*01 DEPLOYMENTID 10453099 DEPLOYED ***********
  4.H-*/SVP-01 HTL/2309/2609/1/00171322/2114

Where:

Example	Description
SVP*01 SVP-01	Hotel Segment (first hotel segment)
10453099	Deployment ID
2309	Check-in date
2609	Check-out date
00171322	Confirmation code
2114	Property number

Example – UpdateReservationRS

<stl19:Remarks>
<stl19:Remark index="1" id="51" type="HS" elementId="pnr-51">
<stl19:RemarkLines>
<stl19:RemarkLine>
<stl19:Text>*/SVP*01 DEPLOYMENTID 10724530 DEPLOYED ***********</stl19:Text>
</stl19:RemarkLine>
</stl19:RemarkLines>
</stl19:Remark>
<stl19:Remark index="2" id="52" type="HS" elementId="pnr-52">
<stl19:RemarkLines>
<stl19:RemarkLine>
<stl19:Text>*/SVP-01 HTL/0110/0310/1/2109054215/36848</stl19:Text>
</stl19:RemarkLine>
</stl19:RemarkLines>
</stl19:Remark>

Ignore or Cancel before COMMIT

If the sell operation is ignored, or the hotel segment is cancelled before the first COMMIT, a cancelation message will be sent to Conferma. This will cancel the Deployment ID and the information will not be stored in the PNR.

Hotel Cancelation after COMMIT

If the hotel reservation is cancelled after it is completed, the system will send a cancel notification to Conferma. The reservation will be updated to reflect the new status of the Deployment ID.

Example

*P5 
REMARKS
  1.H-CONFERMA-GETTHERETEST
  2..UU1-1234
  3..UU2-DAVE BROWN
  4.H-*/SVP*01 DEPLOYMENTID 10062605 CANCELLED ***********
  5.H-*/SVP-01 HTL/2309/2609/1/66659921/2114

Examples

Agency with PNAPNR-ON, reservation contains 2 hotel segments:

Deployment ID and Confirmation Numbers

*FOP«                                                           
  1. VIRTUAL CARD TYPE      
     *VCNSABREAIRONE        
     DEPLOYMENT ID: 10259127  CONF:  58991159              
     DEPLOYMENT ID: 10259129  CONF:  58991302

*P5«                                                            
REMARKS                                                         
  1.H-*/SVP*01 DEPLOYMENTID 10259127 DEPLOYED ***********
  2.H-*/SVP-01 HTL/2309/2609/1/58991159/2114
  9.H-*/SVP*02 DEPLOYMENTID 10259129 DEPLOYED ***********
 10.H-*/SVP-02 HTL/2909/0210/1/58991302/2129

Aency with PNAPNR-OFF, reservation contains 2 hotel segments:

*P5«                                                            
REMARKS                                                         
  1.H-*VCNSABREAIRONE DEPLOYMENTID 10453099    
  2.H-*VCNSABREAIRONE CONF/00171322   
  3.H-*/SVP*01 DEPLOYMENTID 10453099 DEPLOYED ***********
  4.H-*/SVP-01 HTL/2309/2609/1/00171322/2114
 11.H-*VCNSABREAIRONE DEPLOYMENTID 10453100     
 12.H-*VCNSABREAIRONE CONF/00172944     
 13.H-*/SVP*02 DEPLOYMENTID 10453100 DEPLOYED ***********
 14.H-*/SVP-02 HTL/2309/2609/1/00172944/2114

Agency cancel hotel segment:

Original Reservation

*N*I*P5*P6«
1.1JONES/D MR
 1  HHL HI HK1 LHR IN23SEP T-OUT26SEP   3NT    2114 HO    /DCHI
LIDAY INN MAYFAIR 1STN013A-2/  289.00GBP/CMN-C/CMT-COMMISSIONAB
LE/AGT99999992/G*VCNSABREONE-CONFERMA DUMMY CARD/C04P/SI-FA-CF-66659921- 
REMARKS
  1.H-CONFERMA-GETTHERETEST
  2..UU1-1234
  3..UU2-DAVE BROWN
  4.H-*/SVP*01 DEPLOYMENTID 10062605 DEPLOYED ***********
  5.H-*/SVP-01 HTL/2309/2609/1/66659921/2114
RECEIVED FROM - SVP ON BEHALF OF 148
2CFG.2CFG*ASP 0550/16SEP14 GZZWFR H

Segment is cancelled

*N*I*P5*P6«
1.1JONES/D MR
NO ITIN  
REMARKS
  1.H-CONFERMA-GETTHERETEST
  2..UU1-1234
  3..UU2-DAVE BROWN
  4.H-*/SVP*01 DEPLOYMENTID 10062605 CANCELLED ***********
  5.H-*/SVP-01 HTL/2309/2609/1/66659921/2114
RECEIVED FROM - SVP ON BEHALF OF 148
2CFG.2CFG*ASP 0550/16SEP14 GZZWFR H