Stayntouch PMS Tabit POS
Tabit POS allows hotels to streamline and enhance their guest experience by integrating guest charges across the hotel ecosystem by name and room number, including mobile ordering at the hotel restaurant, pool, casino, and beach resort.
IMPLEMENTATION
Tabit POS will import Stayntouch charge codes via /hotels/{id}/charge_codes and map them on their end based on the hotel’s information. This also includes POS payment codes, since Tabit POS supports non-residential revenue coming across to the POS, as well.
API USAGE
- post/oath/token
- get/reservations/checked_in (filtered by last name and room number)
- post/reservations/{id}/transactions
- get/posting_accounts (filtered by name and code)
- post/posting_accounts/{id}/transactions
- Note: Taxes are calculated and posted in Stayntouch and are not to be sent over via APIs as part of the check.
WEBHOOK USAGE
- There are no webhooks in use.
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 positive integers.
- One check can be settled by multiple methods at the same time—guest rooms, house accounts, POS settlement
- Split checks
- Split checks settled by different method of payment
- Discounts: Stayntouch will receive the final amount only
- Void: A full void on the same business date as the original transaction is supported only; no partial voids are supported
- Restrict post
Restrict Post Enabled in Stayntouch PMS
GENERATING OAUTH KEYS
- Implementations will request API OAuth keys using the below process.
- Tabit POS requires the following Stayntouch Connect credentials:
- client_id
- client_secret
- hotel_id
Once the OAuth key data is received, please forward to ONE person (not an email chain) the data for use on Tabit POS's side.
CONTACTS
- Ofer Freund, Development, ofer@tabit.cloud
- Eli Sadan, Sales, Eli@tabit.cloud