Pay at table: minutes back on every turn

Pay at table means guests settle the bill without leaving their seats: the server brings a card terminal to the table, or guests pay from their own phones, and the table is free moments later. It sounds like a small convenience. On a busy night, it is one of the simplest ways to give a room back the minutes it loses at the end of every meal, which are often the minutes the next party is waiting for.

The end of the meal is where guests most often feel stuck. They have finished, they are ready to leave, and the bill has not arrived. When it does, someone has to work out who pays what, the server has to fetch a terminal, each card takes its turn, and receipts are printed. Ten or fifteen minutes can pass between "could we have the bill?" and an empty table. Guests spend those minutes waiting, and the venue spends them with a table it cannot sell.

This guide follows the time from the request for the bill to the guests' departure, step by step. It looks at what each minute is worth on a night with two turns, how pay at table, contactless payments and paying by QR code each save time, how splitting the bill fits in, and what to measure. The figures are illustrative; time your own tables to see where your minutes go.

Pay at table covers any way of paying that brings the payment to the guest rather than the guest to a till. The most common is a portable card terminal that the server carries to the table, where each guest taps or inserts their card. Another is paying by QR code, where guests scan a code, see the bill on their phone and pay from it. Some venues use both.

Either way, the aim is the same: to remove the walking, waiting and handing back and forth that a traditional payment involves. The guest never has to stand at the counter, and the server never has to carry a card away from the table, which many guests prefer for security as well as speed.

Pay at table does not replace good service at the end of the meal. It removes the dead time from it, so the goodbye can be warm rather than hurried.

Break the end of a meal into steps and the lost minutes become visible. Here is an illustrative sequence for a table of four paying separately, the traditional way:

That is 17 minutes from the moment guests were ready to leave to the moment the table is free, and only the last two minutes are time guests chose to spend. The rest is waiting: for attention, for the bill, for the terminal and for each other.

On a quiet night, these minutes cost little; there is nobody waiting for the table. On a busy night with two turns, they can decide whether the second sitting starts on time. A table that frees fifteen minutes late delays the next party by fifteen minutes, and that delay can ripple through the rest of the evening.

There are several ways to put a value on the minutes. One is revenue per seated hour: if a table typically earns a certain amount for every hour it is occupied, each minute saved on a busy night is worth roughly one sixtieth of that, provided there is a guest waiting to use it. Another is the second sitting itself: if faster payment lets one more table in a section reach a second sitting, the value is that sitting's whole spend.

The third value is harder to count but just as real: the guest's last impression. A guest who waits ten minutes for the bill after a lovely meal leaves remembering the wait. Our guide to table turnover rate covers how the end of the meal fits into the whole sitting.

The first lost minutes come before the bill is even requested. Guests who are ready to leave often wait several minutes to catch someone's attention. Servers are busy, sections are large, and a raised hand at a corner table can go unseen.

Train servers to read the signs: closed menus, finished coffees, guests looking around, coats being reached for. Offer the bill when the table is ready, rather than waiting to be asked several times. Where guests can ask for the bill from their table, for example from the digital menu they ordered from, the request reaches the floor straight away instead of waiting for someone to notice a hand.

A request that arrives in a shared queue, visible to the whole team, means the nearest free server can respond, not only the one assigned to the table.

The second delay is the bill itself. The server walks to the till, prints the bill, walks back and waits for guests to read it. On a busy night, that round trip can take several minutes, and it is often repeated if guests ask for a change.

Pay at table removes most of it. A server carrying a terminal can show the bill on the terminal or a tablet at the table and take payment in the same visit. With paying by QR code, guests can see the bill on their own phones as soon as it is ready.

Whatever the method, the bill should be correct the first time. A bill with a missing item, a wrong price or a dish the table did not have means another trip and another wait. Accurate orders, taken and sent correctly, are what make a fast payment possible.

Splitting the bill is where many tables slow down. Groups need to agree who had what, who is paying for whom and how to share dishes that everyone ate. The conversation can take longer than the payment.

The simplest split is by item: each guest pays for what they ordered. It is fair and easy to understand, and if the bill already shows which items belong to whom, it is fast. Splitting by share, where the total is divided equally, is quicker still for groups who prefer it. Our guide to splitting the bill for a table of eight covers the methods in detail, and why splitting by item usually saves the server most time.

Ask early. A server who asks "will you be paying together or separately?" when taking the order, or when offering dessert, can prepare the bill in the right shape before guests ask for it.

The payment itself has become much faster. Contactless payments, by card or by phone, take a few seconds each, and most guests now expect to pay that way. The general idea of contactless payment, paying by tapping a card or device on a reader, has made the payment one of the quickest steps.

What slows it down is the terminal's journey. A terminal shared between several servers, kept at the till or low on battery is a terminal that arrives late. Give each section its own terminal, keep them charged, and make sure they work in every corner of the room, including the terrace.

Make receipts optional. Many guests do not want a paper receipt; those who do can have one printed or sent by email. Not printing every receipt saves time and paper.

Paying by QR code lets guests pay from their own phones: they scan a code on the table or the bill, see what they owe, and pay without waiting for the server. For guests who are ready to leave, it can remove the wait for the terminal entirely.

It works well for guests comfortable with their phones and for casual venues where speed matters. It also suits groups who want to split the bill themselves, if the payment page allows it.

It has limits. Some guests prefer to hand over a card, some do not have their phones or data, and some venues feel it removes a moment of hospitality at the end of the meal. Offer it as one option rather than the only one, and make sure a server can still bring a terminal for guests who want one.

Guests care about how their cards are handled. Paying at the table, with the card never leaving the guest's sight, is reassuring. Card payments should follow the industry's security standards, such as those set by the PCI Security Standards Council, and any payment provider you use should meet them.

Make sure the terminal or payment page clearly shows the venue's name and the correct amount, so guests can check before they pay. Train servers never to take a card away from the table, and to hand the terminal over rather than tapping cards themselves.

Trust also depends on the bill being right. A guest who finds an item they did not order, or a price that does not match the menu, trusts the payment less. Accurate orders and accurate prices are part of a fast, comfortable payment.

In many places, the payment is also the moment guests add a tip. Pay at table makes this easier, because the terminal or payment page can offer the option directly. How tips are offered, shared and recorded depends on local custom and law, so check what applies where you trade.

Offer tips simply and without pressure. A clear choice, including the option of no tip, is more comfortable for guests than a screen that seems to demand one. Make sure tips reach the team fairly and are recorded properly.

Not every service needs a faster finish. The minutes matter most when someone is waiting for the table: the first sitting on a two-turn night, a busy weekend brunch with a queue at the door, or a pre-theatre sitting where guests have a curtain to catch. In each case, a slow payment either delays the next party or makes the current one late for something else.

Focus your efforts on those services first. Make sure terminals are charged and distributed before the first sitting ends, brief servers to watch for tables that are ready to leave, and keep an eye on the tables whose next booking is closest. On a quiet weeknight, the same habits still help, but the stakes are lower.

Some parts of the room are harder to serve than others. Terraces, gardens and distant corners are often where guests wait longest for the bill, because the server is further away and the terminal may lose its connection. Test every terminal in every part of the room, including outside, before a busy service, and keep a spare that is known to work there.

The bar has its own rhythm. Guests at the bar often pay as they go, or keep a tab open and settle at the end. Either way, the bartender should be able to take payment without leaving the bar, and a tab should be easy to find and close when the guest is ready.

A faster finish depends as much on habits as on equipment. Train servers to offer the bill when the signs show a table is ready, to ask early how guests want to pay, and to carry the terminal with the bill rather than making two trips. Show them how each step adds minutes, so the reason for the habit is clear.

Practise the end of the meal like any other part of service. Walk through a table of six paying separately, and time it. Then walk through it again with the bill prepared in the right shape and the terminal in hand. The difference makes the point better than any instruction.

A faster payment should never mean a colder goodbye. The time saved at the end of the meal is time the server can spend thanking guests, asking how everything was and inviting them back. A warm farewell is the last thing guests remember.

Make the goodbye part of the routine: thank the guests by name where you know it, mention something from their visit, and, for guests who enjoyed themselves, invite them to book again. The minutes saved on waiting are best spent here.

To know whether pay at table is working, measure the time it saves. On a few busy services, note when guests ask for the bill and when the table is free. Do the same after any change, such as adding terminals or offering paying by QR code, and compare.

Look at the gap between sittings on busy nights, too. If tables are freed faster, the gap should shrink, and more tables should reach a second sitting. If the gap stays the same, the bottleneck may be elsewhere: the reset, the host stand or the kitchen.

Watch payment problems as well: declined cards, terminals that drop their connection and bills that have to be corrected. Each one adds minutes that the faster payment was meant to save.

Here is an illustrative Saturday for a 20-table room with two sittings, to show how the minutes add up. The figures show the method, not typical results.

No guest was rushed. The minutes came from waiting nobody wanted: for attention, for the bill, for the terminal and for each other.

In servearound, guests who ordered from the table's QR code menu can ask for the bill from their phone, and the request arrives in a live queue for the team, marked as it is dealt with, alongside calls for a server. The point of sale opens checks on the same floor plan the host seats from, so the server can go straight to the right table's check.

A check can be split by moving some dishes onto a new check for the same table, merged with another, handed to another server or moved to another table. Payment is taken by the team on the point of sale, by cash or card, or recorded as a transfer or an external terminal, against the check. Payment analytics shows how each day's takings were tendered and who collected them, and the table report shows revenue per seated hour and the gap between seatings. See fulfillment, or get in touch to see it on your floor.

Enough that no server waits for one on a busy night. Many venues aim for one per section, plus a spare.

They suit different guests. QR payment removes the wait for the terminal; a terminal suits guests who prefer to hand over a card. Many venues offer both.

Not if the time comes from waiting. Guests who are ready to leave rarely want to wait for the bill.

Offer it when the signs show the table is ready, rather than placing it unasked. On a busy night, a friendly offer is welcome.

Ask how they want to pay early, and prepare the bill in that shape. Splitting by item is usually the fairest and fastest.

Less for turnover, but it still improves the end of the meal. Nobody enjoys waiting for the bill.

It can. Fewer trips between the table and the till mean fewer chances to bring the wrong bill to the wrong table, and guests check the amount themselves before they pay.

Pay at table brings the payment to the guest, removing the walking and waiting between asking for the bill and leaving. Most of the minutes lost at the end of a meal are spent waiting: for attention, for the bill, for the terminal and for the split. On a busy night with two turns, those minutes can decide whether the second sitting starts on time.

Notice when guests are ready, let them ask for the bill easily, prepare the split early, give each section a charged terminal and use contactless payments, with paying by QR code as an option. Measure the time from request to empty table, and the gap between sittings, and keep removing the waits that nobody chose.