Built for the PMS and POS systems hotels already run
No card data
Guests pay with their room key and the amount goes on their hotel bill. No cardholder data is involved anywhere, so the flow is outside PCI scope.
Hashed room keys
Room key codes are hashed with HMAC-SHA256 the moment they arrive. They are never stored or logged in readable form, and dashboards show only the last 4 characters.
EU hosting, encrypted
HotelPay is hosted in the EU, in Frankfurt. Every connection uses HTTPS/TLS, and the credentials for your till system are encrypted at rest with AES-256-GCM.
Every hotel walled off
Each hotel’s data is kept apart twice: in the application, and again in the database with PostgreSQL row-level security. Access is role based, with an audit trail for logins and credential changes.
Scans give nothing away
Each hotel’s till has its own login, and we keep only a hash of its password. Every refused scan gets the same plain “not found”, so keys, rooms and logins cannot be probed.
Never charged twice
Each till order can post to a guest’s bill only once, enforced by the database. Failed postings retry automatically and show on your hotel dashboard.
Report a security issue
Think you have found a security problem? Email our technical team.