Modification of Hotel Booking

There is an option to modify the form of payment (FOP) from any non-virtual form of payment (VFOP) supported for Lodging bookings to Virtual Payment Card. Modification of booking parameters for the hotel booking that already has a Virtual Payment Card assigned is also supported.

4.7.3 Modification of Form of Payment to VFOP

During the sell process, if any of the following forms of payment have been used: Credit Card, Agency Address, IATA Number, Company, or Corporate ID - there is an option to change it to Virtual Card during modify. For modify, similar to the sell process, when the Virtual Card has been used as the FOP, Sabre sends the information to Conferma. If Conferma approves the virtual FOP, Sabre generates the hotel update request with the card details (provided by Conferma) from the issuer.

Important: If the hotel booking is already associated with the Virtual Card, modification to another Virtual Card is not supported during modify and the following error will be returned: UNABLE TO MODIFY FORM OF PAYMENT FOR A SEGMENT WITH VIRTUAL CARD.

Payment Instructions

Similar to the sell process, if modifying the FOP to Virtual Card, the payment instructions must be added under SpecialInstructions in the request. This field is mandatory for VCN forms of payment. If the information is not present in the hotel modify request, an error response will be returned: Invalid Special Instructions.

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

Note: It is optional to include customer's email address.

The system will verify if the email address is present. If present, the information will be sent to Conferma. From there, the system will verify the hotel modify request and the PNR associated with the email address.

Email Address Hierarchy

The lead guest's email address will be present in the hotel segment 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 address.

Other Validations

Note: Modification of the FOP to Virtual Card is allowed only for the agencies that has VFOP activated in the TJR.

When modifying FOP to a Virtual Card, there are other validations performed for the modify request to successfully generate the Virtual Card number and deployment ID.

Apart from Payments Instructions and Virtual Card Account Code validations,

The agency email address needs to be provided in the UpdateReservationRQ or added to the session.
The following need to be provided in the modify request:
- The hotel fax number
- The length of stay (StayDateRange)
- Hotel Information (Hotel Code and Name)
- Price information (AmounAfterTax)
- Room Description
- The Lead Guest name (FirstName and LastName)

PNR Information Before Form of Payment Modification

Example – Host Display

*I«    
 1  HHL HY HK1 MIA IN10OCT T-OUT11OCT   1NT   23927 HY    /DCHY 
 ATT HOUSE MIAMI A 11DXADPR-1/  296.67USD/RC-¤¤¤-¤¤¤-R/CMN-C/CMT 
 -10.000 PERCENT COMMISSION/AGT99999999/GDPSTVIXXXXXXXXXXXX1111E 
 XP XXXXX-SMITH/NM-SNAKE LUIS/CNOR/SI-CF-HY0020779442-    
 *FOP«      
 FORM OF PAYMENT     
 NO FORM OF PAYMENT DATA        
 *P5H«   
 ‡NO PSGR DATA‡

PNR Information at Modify Initiate

Once the response from Conferma is successful and FOP modification request is accepted by the Hotel Supplier, information regarding the FOP gets modified in the Segment information.

    *I«                                                             
    1  HHL HY HK1 MIA IN10OCT T-OUT11OCT   1NT   23927 HY    /DCHY 
    ATT HOUSE MIAMI A 11DXADPR-1/  296.67USD/RC-¤¤¤-¤¤¤-R/CMN-C/CMT 
    -10.000 PERCENT COMMISSION/AGT99999999/GDPST*VCNSABREAIRONE-CON 
    FERMA DUMMY CARD/NM-SNAKE LUIS/CNOR/SI-SEGMENT SPECIAL INSTRUCT 
    ION         -CF-HY0020779442-

Agencies with PNAPNR-ON (Use Passenger Association and FOP Field)

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

New VCN FOP

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

Existing VCN FOP

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

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

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

*P5H«                                          
REMARKS                                        
  1.H-*VCNSABREAIRONE DEPLOYMENTID 11600858

PNR Information at COMMIT

When the reservation is completed and the hotel modification is successful, the confirmation number and status of the Deployment ID will be added to the PNR.
If the hotel modification is denied, the system will remove the Deployment ID and 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 the reservation is not confirmed by the hotel. The system will then remove the Deployment ID and send a cancel notification to Conferma.

Storage of Confirmation Code

PNAPNR-ON

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

Example – UpdateReservationRS

<or114:FormOfPayment migrated="false">
<or114:VirtualCard>
<or114:CustomerAccountCode>SABREAIRONE</or114:CustomerAccountCode>
<or114:Transactions>
<or114:Transaction index="1" paymentReferenceNumber="01341688393749721182">
<or114:LastUpdateTime>2023-07-03T09: 15: 51</or114:LastUpdateTime>
<or114:DeploymentId>11600848</or114:DeploymentId>
<or114:ConfirmationNumber>HY0020779442</or114:ConfirmationNumber>
<or114:FaxHistory>
<or114:DeliveryAddress>1-305-269-1925</or114:DeliveryAddress>
</or114:FaxHistory>
</or114:Transaction>
</or114:Transactions>
</or114:VirtualCard>
</or114:FormOfPayment>

PNAPNR-OFF

*P5H«                                                                         
  1.H-*VCNSABREAIRONE DEPLOYMENTID 11600858
  2.H-*VCNSABREAIRONE CONF/HY0061668294

Example – UpdateReservationRS

<stl19:Remark index="1" id="86" type="HS" elementId="pnr-86">
<stl19:RemarkLines>
<stl19:RemarkLine>
<stl19:Text>*VCNSABREAIRONE DEPLOYMENTID 11600858</stl19:Text>
</stl19:RemarkLine>
</stl19:RemarkLines>
</stl19:Remark>
<stl19:Remark index="2" id="143" type="HS" elementId="pnr-143">
<stl19:RemarkLines>
<stl19:RemarkLine>
<stl19:Text>*VCNSABREAIRONE CONF/HY0061668294</stl19:Text>
</stl19:RemarkLine>
</stl19:RemarkLines>
</stl19:Remark>

Deployment ID Status

Regardless of the PNAPNR option, the Deployment ID status is added in the form of historical remarks.

*P5H«                                                                         
3.H-*/SVP*01 DEPLOYMENTID 11600858 DEPLOYED ***********       
4.H-*/SVP-01 HTL/1010/1110/1/HY0061668294/23927

where

Example	Description
SVP*01 SVP-01	Hotel segment (first hotel segment)
11600858	Deployment ID
1010	Check-in date
1110	Check-out date
HY0061668294	Confirmation code
23927	Property code

Example – UpdateReservationRS

<stl19:Remark index="1" id="144" type="HS" elementId="pnr-144">
<stl19:RemarkLines>
<stl19:RemarkLine>
<stl19:Text>*/SVP*01 DEPLOYMENTID 11600848 DEPLOYED ***********</stl19:Text>
</stl19:RemarkLine>
</stl19:RemarkLines>
</stl19:Remark>
<stl19:Remark index="2" id="145" type="HS" elementId="pnr-145">
<stl19:RemarkLines>
<stl19:RemarkLine>
<stl19:Text>*/SVP-01 HTL/1010/1110/1/HY0020779442/23927</stl19:Text>
</stl19:RemarkLine>
</stl19:RemarkLines>
</stl19:Remark>

Ignore Modification

If the modification of FOP is ignored before COMMIT, a cancellation message will be sent to Conferma. FOP will not be modified for the segment and deployment ID will not be stored in the PNR.
Information in the PNR once segment modification has been ignored – FOP is not modified in the segment and Deployment ID is cancelled.

*I«                                                             
 1  HHL HY HK1 MIA IN10OCT T-OUT11OCT   1NT   23927 HY    /DCHY 
ATT HOUSE MIAMI A 11DXADPR-1/  296.67USD/RC-¤¤¤-¤¤¤-R/CMN-C/CMT 
-10.000 PERCENT COMMISSION/AGT99999999/GDPSTVIXXXXXXXXXXXX1111E 
XP XXXXX-SMITH/NM-SNAKE LUIS/CNOR/SI-CF-HY0020779442-           
*FOP«                                                           
FORM OF PAYMENT                                                 
NO FORM OF PAYMENT DATA                                         
*P5H«                                                           
‡NO PSGR DATA‡

Navigate to the section Modify CSL Segment for UpdateReservationRQ request and response examples for modification of FOP from Credit Card to Virtual Credit Card.

4.7.4 Modification of Booking Parameters of the Reservation with VFOP

If during modification process any of the following parameters will be updated for the booking for which Virtual Card has been used during sell as form of payment:

Room Type
Check In/Check Out date outside date range
Guest Number
Check In/Check Out date within date range

Sabre will send request to Conferma (Modify Notification) to update previously deployed Virtual card booking. This request happens when there is any modification to a booking where the amount that is applied to Virtual Card changes.

In case of modification of any other information, communication with Conferma is not necessary.

Amount Information

If modifying any booking parameter that can impacts price or dates, providing modified AmountAfterTax and StayDateRange information in the UpdateReservationRQ modify request is necessary. This is crucial to sent correct information to Conferma.

Below example presents how information stored in the PNR changes at different stages of modify.

PNR Information Before Stay Date Range Modification

*I«                                                             
 1  HHL GI HK1 ALB IN10OCT T-OUT11OCT   1NT   27316 HI    /DCGI 
LTON GARDEN INN A 1A0CD96 -1/  167.34USD/RC-¤¤¤-RAC-R/CMN-C/CMT 
-NON COMMISSIONABLE/AGT12345678/GDPST*VCNSABREAIRONE-SABRE TEST 
/ID-LOY123450/FT-FLY123450/CD-CD1234567/NM-SNAKE LUISE/C05D/SI- 
SEGMENT SPECIAL INSTRUCTION.-CF-3360299369-

*FOP«                                                           
FORM OF PAYMENT                                                 
  1. VIRTUAL CARD TYPE                                          
     *VCNSABREAIRONE                                            
                                        UHL                     
     DEPLOYMENT ID: 11604986   CONF: 3360299369                 
*P5«                                                            
REMARKS                                                         
  1.H-*/SVP*01 DEPLOYMENTID 11604986 DEPLOYED ***********       
  2.H-*/SVP-01 HTL/1010/1110/1/3360299369/27316

PNR Information at Modify Initiate

Once request to Conferma to modify previously deployed Virtual Card booking has been sent and stay date range has been accepted by Hotel Supplier, information regarding dates is modified in the Segment information.

*I«                                                             
 1  HHL GI HK1 ALB IN10OCT T-OUT12OCT   2NT   27316 HI    /DCGI 
LTON GARDEN INN A 1A0CD96 -1/  167.34USD/RC-RAC-RAC-R/CMN-C/CMT 
-NON COMMISSIONABLE/AGT12345678/GDPST*VCNSABREAIRONE-SABRE TEST 
/ID-LOY123450/FT-FLY123450/CD-CD1234567/NM-SNAKE LUISE/C05D/SI- 
SEGMENT SPECIAL INSTRUCTION.-CF-3360299369-

Information regarding Deployment ID does not change in the Modify process, so generated Deployment ID number stays unchanged during the whole modify transaction.

Agencies with PNAPNR-ON – Deployment ID Stored in FOP Field

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

Agencies with PNAPNR-OFF – Deployment ID Stored as Historical Remark

*P5H«                                                                         
  1.H-*VCNSABREAIRONE DEPLOYMENTID 11600858
  2.H-*VCNSABREAIRONE CONF/HY0061668294

Deployment ID Status is also unchanged at this stage of modify phase (Initiate). It will be modified accordingly at Modify COMMIT.

*P5«                                                            
REMARKS                                                         
  1.H-*/SVP*01 DEPLOYMENTID 11604986 DEPLOYED ***********       
  2.H-*/SVP-01 HTL/1010/1110/1/3360299369/27316

PNR Information at COMMIT

When the reservation is complete and the hotel modification is successful, the Deployment ID status will be updated in the PNR.
If the hotel modification is denied, the system will resent initial booking information to Conferma – the segment and Virtual payment information gets reverted to their state before modification.

PNR information if the modification is rejected by Hotel supplier – no changes in the booking and payment information.

*I«                                                             
 1  HHL GI HK1 ALB IN10OCT T-OUT11OCT   1NT   27316 HI    /DCGI 
LTON GARDEN INN A 1A0CD96 -1/  167.34USD/RC-¤¤¤-RAC-R/CMN-C/CMT 
-NON COMMISSIONABLE/AGT12345678/GDPST*VCNSABREAIRONE-SABRE TEST 
/ID-LOY123450/FT-FLY123450/CD-CD1234567/NM-SNAKE LUISE/C05D/SI- 
SEGMENT SPECIAL INSTRUCTION.-CF-3360299369-                

*FOP«                                                           
FORM OF PAYMENT                                                 
  1. VIRTUAL CARD TYPE                                          
     *VCNSABREAIRONE                                            
                                        UHL                     
     DEPLOYMENT ID: 11604986   CONF: 3360299369                 
*P5«                                                            
REMARKS                                                         
  1.H-*/SVP*01 DEPLOYMENTID 11604986 DEPLOYED ***********       
  2.H-*/SVP-01 HTL/1010/1110/1/3360299369/27316

Deployment ID Status Update

If the COMMIT is successful, the Deployment status gets updated in the PNR which reflects in the status change of the historical remark from DEPLOYED to MODIFIED.

*P5«                                                            
REMARKS                                                         
  1.H-*/SVP*01 DEPLOYMENTID 11604986 MODIFIED ***********       
  2.H-*/SVP-01 HTL/1010/1210/1/3360299369/27316

where

Example	Description
SVP*01 SVP-01	Hotel segment (first hotel segment)
11604986	Deployment ID
1010	Check-in date
1210	Check-out date
3360299369	Confirmation code
27316	Property code

Example – UpdateReservationRS

<stl19:Remark index="1" id="49" type="HS" elementId="pnr-49">
<stl19:RemarkLines>
<stl19:RemarkLine>
<stl19:Text>*/SVP*01 DEPLOYMENTID 11604986 MODIFIED ***********</stl19:Text>
</stl19:RemarkLine>
</stl19:RemarkLines>
</stl19:Remark>
<stl19:Remark index="2" id="50" type="HS" elementId="pnr-50">
<stl19:RemarkLines>
<stl19:RemarkLine>
<stl19:Text>*/SVP-01 HTL/1010/1210/1/3360299369/27316</stl19:Text>
</stl19:RemarkLine>
</stl19:RemarkLines>
</stl19:Remark>

Ignore Modification

If the FOP modification is ignored before COMMIT, the system will resent the initial booking information to Conferma; and the segment and Virtual payment information are reverted to their original state before modification.
Information in the PNR once segment modification has been ignored – the FOP does not get modified in the segment and the Deployment ID status remains unchanged (DEPLOYED).

*I«                                                             
 1  HHL GI HK1 ALB IN10OCT T-OUT11OCT   1NT   27316 HI    /DCGI 
LTON GARDEN INN A 1A0CD96 -1/  167.34USD/RC-¤¤¤-RAC-R/CMN-C/CMT 
-NON COMMISSIONABLE/AGT12345678/GDPST*VCNSABREAIRONE-SABRE TEST 
/ID-LOY123450/FT-FLY123450/CD-CD1234567/NM-SNAKE LUISE/C05D/SI- 
SEGMENT SPECIAL INSTRUCTION.-CF-3360299369-                

*FOP«                                                           
FORM OF PAYMENT                                                 
  1. VIRTUAL CARD TYPE                                          
     *VCNSABREAIRONE                                            
                                        UHL                     
     DEPLOYMENT ID: 11604986   CONF: 3360299369                 
*P5«                                                            
REMARKS                                                         
  1.H-*/SVP*01 DEPLOYMENTID 11604986 DEPLOYED ***********       
  2.H-*/SVP-01 HTL/1010/1110/1/3360299369/27316

Navigate to the section Modify CSL Segment for UpdateReservationRQ request and response examples for modification of FOP from Credit Card to Virtual Credit Card.