Pay at the table: charge the right amount, confirm every payment

A table of four asks for the check, but a drink was added after the mains. The server has to find that add-on and check the quantities before stating the total. If the guest sees an amount that doesn't match what they ordered, paying by phone won't fix it. You'll be redoing the check in front of them.

Decide who prepares the total and who signs off on it, especially when several servers share a section. Show extras and voided items clearly. If guests want to split the check, decide how to work out each share and how to track each payment before you mark the table as closed.

A table might pay in cash, by card or with a mobile wallet, depending on what your venue has set up. Tell guests the options and the final amount before asking them to do anything. For a QR code payment, explain which code to scan and who the payment goes to. The QR code on your menu isn't automatically a payment QR code.

The right flow depends on your payment provider, your hardware and your connection. Run a practice round with your team on the phone or card terminal you'll use during service. A short, clear rule stops everyone from improvising their own method when the room is packed.

Once the guest has paid, someone on your team checks the confirmation in the payment provider's app, or follows your procedure for cash and card. A message or screenshot shown on the guest's phone doesn't always prove the money has arrived. Note the confirmed amount, the method used and any payments still pending.

If the connection drops or a payment fails, don't send a second request right away without checking the status of the first. Give the guest a simple answer: "I'm just checking whether your payment went through before we try again." Have another accepted payment method ready, and someone who can sort out the issue without leaving the table hanging.

With Zeat, guests can browse dishes and prices on a mobile menu they open with a QR code. Zeat also offers ordering by the guest or by staff, with tracking through to the kitchen and bar. These steps help build a clear, itemized check for each table. On their own, they don't prove that a payment has been initiated, received or reconciled in Zeat.

Ask us to demo a late add-on, a split check and a failed payment. Confirm the providers, payment methods, devices, receipts and how the manager sees that a table has paid. You'll know exactly what your team can do in Zeat and what stays in another tool.

Over a few similar services, write down when guests ask for the check, when the amount is presented and when payment is confirmed. Ask your team which mistakes they had to fix, too. This shows whether the wait comes from preparing the check, from the payment itself or from not having someone free to confirm it.

The goal: a clearer end to the meal for guests, and more control for your team. Don't count on faster turns at every table: that also depends on the kitchen, the host stand and how busy the day is. Start by fixing the step that actually keeps people waiting.