Payment Transaction Record

Payment Transaction Record is a one-way API that allows a PMS to retrieve reservation payment transaction data. These payment transactions are payments taken against a reservation via SiteMinder's Pay product.

The SiteMinder Pay integration with the Channel Manager & Property Platform offers customers the ability to process payments for their Channels/OTAs and Direct Booking reservations, and secure their funds effectively.

Each payment transaction will include specific details about the payment and its related reservation, and they should be treated as a single entity. Multiple payments can occur for a reservation at different stages during its lifecycle.

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.

Supported Messages

SM_HotelResPaymentReadRQ/RS - used to pull payment transactions every 2-5 minutes per Hotel.

SM_HotelResPaymentResultRQ/RS - used to confirm the payment transaction has been processed and stored by the PMS.

Additional HotelReservationID

To use the Payment Transaction Record in pmsXchange, the PMS must first be certified with SiteMinder and then enabled to accept payments from pmsXchange. Additionally, the PMS will need to manage a new identification value known as the "Payment Context ID," which identifies the master record for all payments associated with a SiteMinder reservation.

Enabled PMS systems will find an extra HotelReservation / ResGlobalInfo / HotelReservationIDs / HotelReservationID element in the reservation XML (OTA_ResRetrieveRS). The OTA UniqueID Type for the Payment Context ID will always be "34" (Master reference).

OTA_ResRetrieveRS

      </RoomStays>
      <ResGlobalInfo>
        <HotelReservationIDs>
          <HotelReservationID ResID_Type="14" ResID_Value="BDC-12345"/>
          <HotelReservationID ResID_Type="34" ResID_Value="74a63a92-d988334"/>
        </HotelReservationIDs>
      </ResGlobalInfo>
    </HotelReservation>
  </ReservationsList>
</OTA_ResRetrieveRS>

Specifications

HotelReservationIDs / HotelReservationID	0..3	Reference number/string or PNR as supplied by the Booking agent.
@ResID_Type	1	Will be one of the following values: 14: OTA code for 'Travel Agent PNR'. The @ResID_Value will be the reservation identifier as provided by the source booking channel. 26: OTA code for 'Associated itinerary reservation'. 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 payment transactions.
@ResID_Value	1	Reference number/string for the ResID_Type. ResID_Value could potentially contain special characters such as '/'.

Test Web Service

Test Web Service URL: https://tpi-pmsx.preprod.siteminderlabs.com/webservices/{RequestorID}

WSDL: https://tpi-pmsx.preprod.siteminderlabs.com/webservices/{RequestorID}/pmsxchange_pms_payments.wsdl

WSDL for dotNet: https://tpi-pmsx.preprod.siteminderlabs.com/webservices/{RequestorID}/pmsxchange_pms_payments_flat.wsdl The above WSDL for dotNet is recommended for .NET clients as several known issues will arise when using proxy generators from the .NET framework (such as wsdl.exe or svcutil.exe) with the OTA spec.