Applies to: Stayntouch PMS
TiPOS
TiPOS POS system was optimally developed for the needs of the gastronomy, bakery, and retail sectors. These three basic packages can be expanded with a variety of additional modules, so clients always get the right software for their needs.
API USAGE
- post/oath/token
- get/hotels/{id}/transaction_codes – Upon setup
- get/posting_accounts – Filtered by name or code/ID
- get/reservations/checked_in – Filtered by last name and/or room number
- post/posting_accounts/{id}/transactions
- post/reservations/{id}/transactions
- Note: Taxes are calculated and posted in Stayntouch PMS and are not to be sent via APIs as part of the check.
WEBHOOK USAGE
- There are no webhooks in place.
SUPPORTED FUNCTIONALITIES
- Guest bill postings
- House account bill postings
- Non-residential postings including attached payments settled at POS – POST/posting_accounts/{id}/transactions call needs to include revenue and payment posting, both as a positive integer.
- Split checks closed as separate checks
- Split checks settled by different method of payment – First as a room charge + second as cash, for example.
- Discounts – Discounts are applied in TiPOS, and only the final amount will be posted to Stayntouch PMS.
- Void – A full void on the same business date as the original transaction is supported only. No partial voids are supported.
- Restrict post
IMPLEMENTATION
- TiPOS will import Stayntouch PMS charge codes via /hotels/{id}/charge_codes and map them on their side based on the hotel’s information.
- This also includes POS payment codes via /hotels/{id}/payment_types, as TiPOS support a full real-time revenue push for non-residential charges to come across to Stayntouch PMS.
GENERATING OAUTH KEYS
- Implementations will request API OAuth keys using the below process.
- TiPOS require the following Stayntouch Connect API credentials:
- client_id
- client_secret
- hotel_id