...
...
Table of Contents | ||||
---|---|---|---|---|
|
...
Sample Xml
Expand | |||||
---|---|---|---|---|---|
| |||||
|
Additional HotelReservationID
To use the Payments in pmsXchange function the PMS will first need to be certified with Siteminder and subsequently be enabled to accept payments from pmsXchange. The PMS will also need to handle an additional identification value that contains the “Payment Context ID”. This new ID identifies the master record of all the payments taken for a Siteminder reservation.
Enabled PMS will see an additional HotelReservation / ResGlobalInfo / HotelReservationIDs / HotelReservationID
element to the reservation XML. The OTA Unique ID type for the payment context ID will always be "34"
(Master reference).
OTA_ResRetrieveRS / OTA_HotelResNotifRQ
Element | Number | Description |
---|---|---|
HotelReservationIDs / HotelReservationID | 0..3 | Reference number/string or PNR as supplied by the Booking agent will be supplied here. If this reservation is linked under an itinerary, the itinerary id given by the source booking agent will be supplied in a second. |
@ResID_Type | 1 | Will be one of the following values: 14: OTA code for 'Travel Agent PNR'. If this type is used the @ResID_Value will be the reservation identifier as provided by the source booking channel. 26: OTA code for 'Associated itinerary reservation'. If this type is used the @ResID_Value will be the itinerary identifier for one or more bookings in an itinerary as provided by the source booking channel. 34: OTA code for “Master Reference”. If this type is used the @ResID_Value will be the identifier for auxiliary messages, such as payment transactions. |
@ResID_Value | 1 | Reference number/string for the ResID_Type. ResID_Value could potentially contain special characters such '/'. |
...