PMS-provider service workflows

PMS-provider service workflows

After a hotel guest pays their restaurant check with a room charge payment option, the Toast tender API sends the payment details through the PMS-provider service. Transactions sent through the PMS-provider service convert Toast order details into a message that your hotel’s PMS can use to post the room charge accordingly. API messages from your PMS to your Toast platform must also be converted into a format that your Toast platform can understand. The procedure below describes the PMS-provider service workflow, with a supporting diagram.

  1. A hotel guest charges a restaurant transaction to their room using a room charge payment option.

  2. The PMS-provider service looks up the hotel's restaurant information using a database that stores hotel configuration information and guest details.

  3. Your Toast platform queries guest data using guest search configuration.

    Note

    See this diagram for an example of the guest search configuration.

  4. The guest details are transmitted back through the Toast tender API from your PMS to your Toast platform.

  5. The Toast tender API manages the following actions:

    1. The PMS-provider service calls to the Toast orders API and sends the transaction details to the PMS-provider service.

    2. The PMS-provider service makes API calls to your PMS server, providing the order details to your PMS.

    3. Your PMS sends an acceptance message to the PMS provider-service where the message is converted, and delivered to your Toast platform.

Diagram showing the PMS-provider service workflow.