To set up pay at the table, choose one of three methods (a handheld payment device, a QR code on the check, or a tablet at the table), connect it to your POS so checks sync automatically, train servers on a simple script, and test with a few tables before going live. Most restaurants can finish the whole rollout in about a week, and the payoff is faster table turns, fewer card-handling risks, and often higher tips.
Why pay at the table is worth doing
Waiting for the check is the most common guest complaint after a good meal, and it ties up a table that could seat the next party. Every minute you shave off checkout adds up. If a table stays 6 minutes longer than needed and you turn 40 tables on a busy night, that is four hours of lost seating time. Pay at the table also keeps the card in the guest's hand, which reduces skimming risk and billing mistakes.
For more on the turn-time side, see how to improve table turnover time and how to reduce wait times during a rush.
The three ways to do it
| Method | Best for | Upfront cost | Watch out for |
|---|---|---|---|
| Handheld payment device | Full-service, busy floors | Device per 2 to 4 servers | Charging, Wi-Fi coverage, drops |
| QR code on the check | Casual, bars, patios | Almost none | Guests without phones, older guests |
| Tablet or kiosk at the table | Fast casual, buffets | Highest | Theft, cleaning, upkeep |
Handhelds are the safest first step for table service because servers stay in control of the experience. QR payment works well as an add-on, especially for large groups splitting a check. Read handheld POS and tableside ordering and how to set up contactless payments for hardware detail.
Step-by-step setup
- Check your POS first. Pay at the table only works smoothly if payments post to the open check automatically. If your system makes servers retype amounts, you will create errors, not save time.
- Test your Wi-Fi. Walk every section with a phone and check the signal at the farthest booth, the patio, and the bar. Dead zones are the number one cause of failed rollouts.
- Pick a tip screen. Set suggested tips, such as 18, 20, and 25 percent, and a custom option. Keep the screen simple and unpressured.
- Allow split checks. Make sure the device can split by seat, by item, or evenly.
- Write a server script. Something like: "I'll bring the check to you so you can pay whenever you're ready." Avoid hovering.
- Pilot for three days on one section, then compare checkout time and tip percentage with the other sections.
What it does to tips and cost
Servers are often nervous that a tip prompt will cut their tips. In practice, a clear on-screen suggestion usually holds or raises averages, but test it rather than assuming. Track average tip percent for two weeks before and after. Also compare card processing: the device itself rarely changes your rate, but understanding your fees helps. See how to reduce credit card processing fees and should your restaurant add a credit card surcharge.
Security and training notes
Keep devices on a charging dock at the station between uses, and lock them with a staff PIN. Train servers never to take a card out of sight. Review data security and PCI compliance for restaurants so your setup stays compliant, and confirm in writing which party is responsible for chargebacks. If a dispute comes up, how to handle credit card chargebacks shows the steps.
Common mistakes
Buying too few devices, so servers queue at the dock, is the classic one. Plan one device for every two to three servers on a busy shift. Another is skipping the offline plan: know how you will take payment if Wi-Fi drops, and practice it once.
Pay at the table works when the device, the POS, and the Wi-Fi all agree. Test the connection first, pilot one section, and let the numbers tell you whether to expand.
Let the POS do the heavy lifting
Cobblestone POS is a free, all-in-one POS for independent restaurants, with payments, reporting, and ordering built in and no monthly fee. That means tableside payments post straight to the check and your tip and speed data land in the same reports you already use. Versus platforms that run around $470 a month, you keep the money for the hardware you actually need.