How it works
Your waiter brings the terminal to the table. The customer taps their card. The bill's settled, the tab's closed, and your POS is updated — no running back and forth to the till.
Pay At Table (PAT) is built for hospitality. Split bills, add tips, and keep your EPoS and yetipay terminals in sync over a persistent WebSocket connection. The terminal talks to your POS in real time: it fetches open tables, locks the one the waiter selects, takes payment, and reports back so you can reconcile.
How it fits together
Your EPoS (or POS) maintains a WebSocket connection to yetipay. When a waiter picks up a yetipay device and selects a table, the terminal asks your system for the bill. You send back the amount and any receipt lines you want printed. The customer pays on the device. You get the transaction details and unlock the table. Done.
No REST polling, no manual reconciliation — the flow is conversational: request, response, next step.
Quick links
- Integration flow — The flow from table lock to payment to unlock
- API Reference — JSON-RPC messages and shapes
- PAC Virtual Devices — Test without physical hardware
What you’ll need
- An EPoS or POS that can hold a WebSocket connection to yetipay
- Your yetipay credentials and connection configuration
- (Optional) Virtual devices for sandbox testing