Purpose: Document the people, systems, data, controls and exceptions in a real merchant workflow.
Written and reviewed by Raied Muheisen · Last reviewed June 21, 2026
Trigger
A server presents or settles a guest check at the table.
Actors
- Guest
- Server
- Manager
- Kitchen/bar
- Payment provider
Normal workflow
- Server confirms the correct open check.
- Guest reviews items and total.
- Tender and tip are entered on the approved device.
- Authorization result is returned.
- Receipt preference is completed.
- Check status updates and server confirms closure.
- Batch and tip totals are reviewed.
Exceptions
- Wrong table or check
- Split payment
- Decline
- Tip correction
- Device battery or connectivity issue
- Refund after closeout
Required data
- Table/check owner
- Items and adjustments
- Tender and authorization
- Tip and server attribution
- Receipt
- Batch and settlement
Controls and ownership
- Device assignment and charging
- Wi-Fi coverage validation
- Manager permission for exceptions
- Tip and closeout review
- Support escalation
Acceptance tests
- ☐ Single and split payment
- ☐ Decline and retry
- ☐ Tip and receipt
- ☐ Connectivity problem
- ☐ Closeout and settlement