| Table of Contents | ||||
|---|---|---|---|---|
|
...
| Expand | |||||
|---|---|---|---|---|---|
| |||||
|
Reservation IDs/UniqueID
Because a reservation in Siteminder can be delivered to a PMS as multiple notifications but of how payments are taken at the master reservation leveland handled in Siteminder. You now need to keep track of an extra reservation Unique ID.
So This new ID will be in addition to the exisiting type=14 that contains the unique reservation ID of the of the reservation notification that was delivered. This additional . Know as the Siteminder-Id eg - 'BDC-79860526'
There will now an additional UniqueID of type=34 this . This ID is for the master reservation contains the payment context ID (this is where payments were taken). This master reservation may have been broken into multiple reservation notifications. IE in the case of a multi room booking. For example one 3 room booking could be split into three 1 room bookings. eg - '74a63a92-d988-46b8-8476-3319285af8ac'
The last id is the pms confirmation Id (this is assigned by the PMS and is the unique Id of the transaction in the PMS). This is optional. eg - '077887-200098'
| Code Block | ||
|---|---|---|
| ||
<UniqueID ID="BDC-79860526" Type="14" /> <!-- Reservation Id--> <UniqueID ID="74a63a92-d988-46b8-8476-3319285af8ac" Type="34" /> <!-- Master Res id --> <UniqueID ID="077887-200098" Type="40" /> <!-- Delivery Confirmation Id --> |
...
SM_HotelResPaymentResultRQ
Element | Number | Description |
SM_HotelResPaymentResultRQ | 1 | Root element |
@Version | 1 | Current Version 1.0 |
@EchoToken | 1 | Globally unique identifier for the request, value will be returned as an EchoToken in the response. |
@TimeStamp | 1 | Time of the transaction in xml schema dateTime format |
SM_HotelResPaymentResultRQ/HotelResPaymentResult | 0..n | HotelResPaymentResult data |
@HotelCode | 1 | Hotel code as recognised by pmsXchange |
@TransactionId | 1 | Transaction Identifier |
SM_HotelResPaymentReadRS/HotelResPaymentList/HotelResPayment/UniqueID | 2..3 | Container for the Reservation Identifiers and Confirmation id. See Unique ID |
@ID | 1 | Reservation Identifier or confirm id |
@Type | 1 | 14, 34 & if success 40 - See UniqueId@Type |
SM_HotelResPaymentResultRQ/Success | 0..1 | Present If successfully stored and processed |
SM_HotelResPaymentResultRQ/Errors | 0..1 | Present If unsuccessfully processed See Error Handling |
SM_HotelResPaymentResultRQ/Errors/Error | 1 | Mandatory if Error present. Text can contain a human readable description of the error |
@Code | 1 | Mandatory if Error present. Any type from the OTA code table for 'Error Warning Type (EWT)' can be used. |
@Type | 1 | Mandatory if Error present. Any code from the OTA code table for 'Error Codes (ERR)' can be used. |
SM_HotelResPaymentResultRS
Element | Number | Description |
SM_HotelResPaymentResultRS | 1 | Root element |
@Version | 1 | Current Version 1.0 |
@EchoToken | 1 | Globally unique identifier for the request, value will be returned as an EchoToken in the response. |
@TimeStamp | 1 | Time of the transaction in xml schema dateTime format |
SM_HotelResPaymentResultRS/Success | 0..1 | Present If successfully stored and processed |
SM_HotelResPaymentResultRS/Errors | 0..1 | Present If unsuccessfully processed See Error Handling |
SM_HotelResPaymentResultRS/Errors/Error | 1 | Mandatory if Error present. Text can contain a human readable description of the error |
@Code | 1 | Mandatory if Error present. Any type from the OTA code table for 'Error Warning Type (EWT)' can be used. |
@Type | 1 | Mandatory if Error present. Any code from the OTA code table for 'Error Codes (ERR)' can be used. |