Simulate Test Transactions

Currently, we need to manually post a transaction using Postman. You will need to download and import the environment and collections below:

Below is an environment where you can update the PMS Endpoint, Username, Password, PMS Code, Hotel Code, Reservation ID, and Payment Context ID (This can be found in the reservation message, ResID_Value of ResID_Type="34").

Postman Collection

To assist with automating your testing, please fork SiteMinder's PMS Postman Collection, where you will see various request scenarios, as well as the detailed breakdown of the Reservation Certification Scenarios.

Step 1 - Fork SiteMinder's PMS Transaction Record Collection and pmsx-api environment.

Step 2 - Update the PMS environment with your specific details.

Step 3 - Select Run Collections.

Step 4 - After running the collection, a summary will display showing which scenarios passed or failed.

Step 5 - Click View Results to see more details on each test, including the Request sent and the Response received.

For more details on using Postman, see the article Test your API using the Collection Runner.

SiteMinder provides a test account for use during the active development phase. This account is intended solely for development purposes and should not be used for ongoing testing or demonstrations. Access to the test account will be disabled upon completion of the SiteMinder certification.

PMS Transaction API Environment

Please fork the following Postman Environment: PMSX Transaction Record

Postman Transactions collection

Please fork the following Postman Collection: pmsx-transaction-api

This is used to post a transaction for PMS to pull. You may update the details below:

• transactionCreatedAt

• type - Transaction type

• chargeType - Charge Type Mapping Definition

• amountInCents - Ex: "amountInCents": 30050 means 300.50

• amountDueInCents - remaining amount (for room deposit charges)

• currency

• paymentCard

• remark

Transactions will be available to be pulled 4 times if not confirmed by the PMS. After it has been provided 4 times, the transactions will no longer be available and will return with an empty response.

Test pull request SM_HotelResPaymentReadRQ collection

After you post a transaction above, you may test if it is available in the SM_HotelResPaymentReadRS

This is completed via the SM_HotelResPaymentReadRQ request in the provided Postman collection.

---

Certification Scenarios / Criteria

1. PMS must pull payment transactions every 2-5 minutes per Hotel (SM_HotelResPaymentReadRQ)

2. Validate that you can handle the transactions scenarios:

   1. Processing a charge for a reservation

   2. Processing a charge for a modification

   3. Processing a charge for a cancellation

   4. Processing a refund for a reservation

   5. Processing a refund for a modification

   6. Processing a refund for a cancellation

   7. Processing different type - Transaction type

   8. Processing different chargeType - Charge Type Mapping Definition

3. Validate that a SM_HotelResPaymentResultRQ is returned to SiteMinder to confirm transactions.

4. Validate that your systems can handle the SM_HotelResPaymentResultRS returned from SiteMinder after each transaction.