Reservations
Reservations PULL
The Reservations PULL
enables Property Management Systems (PMS) to retrieve reservations, modifications, and cancellations from the SiteMinder platform. This integration ensures that PMSs receive up-to-date booking information from various channels, maintaining consistency and reducing the risk of overbooking.
Reservations Upload
The Reservation Upload
allows PMSs to push reservations, modifications and cancellations to SiteMinder, where certified Apps can collect this data. The PMS will use their existing SiteMinder web service endpoint to post the OTA_HotelResNotifRQ message.
Reservations Import
The reservation-import
endpoint allows PMSs to request a full refresh of all future reservations and modifications for a hotel associated with that PMS. This request triggers a background job that queues these reservations and delivers them to the PMS through the standard Reservations PULL flow. During the import process, the hotel will receive both ‘live’ reservations and ‘imported’ reservations.
Payment Transaction Record
The Payment Transaction Record
is a one-way API that allows a PMSs to retrieve reservation payment transaction data. These transactions represent payments made against a reservation using SiteMinder Pay, which facilitates secure payment processing for booking channels and direct bookings through the SiteMinder Platform.
Each payment transaction includes specific details related to the payment and its corresponding reservation. As multiple payments can be processed at different stages of a reservation’s lifecycle, these transactions should be treated as a single entity within the PMS.
Benefits:
Enables PMS systems to pull payment details related to channel reservations.
Eliminates the need for manual entry, enhancing user experience and reducing the time spent on payment management.
Customers will gain visibility into payments processed through the Channel Manager and Property Platform within their PMS, allowing for more efficient invoicing and payment tracking.
To access Payment Transaction Record data the PMS must certify Reservations PULL, be able to accept payment data from SiteMinder and to manage a identification value known as the Payment Context ID
, which serves as the master record for all payments linked to a SiteMinder reservation.
Credit Card Tokenization
Reservations PULL supports tokenization, which replaces sensitive credit card details with a unique identifier or token. This enhances security by ensuring no payment data is stored in the PMS.
PMSs platforms can use a third-party proxy service to receive tokenized reservation data instead of retrieving reservations directly from SiteMinder, as in the standard Reservations PULL
model.
Last updated
Was this helpful?