Can my customers also pay online through the POS system?

What I tell guests and staff clearly from the start

Yes, my customers can pay through the POS system online in some cases, but not automatically in every imaginable one. Based on the verified Bonzumo functions, there is a payment connection for configured card payments and there is also an intended online payment flow for buying gift vouchers. What is not verified is a general promise that every ordinary restaurant bill can later be paid through a universal online link. That distinction matters in daily service, because I do not want my team promising too much or guests assuming they can always settle an open table from home after the visit.

I explain it with a simple example. If a guest sits in the restaurant and pays by card after dinner, that payment belongs to the specific sales transaction in the system. If the same person buys a gift voucher through a configured online channel, a payment connection is intended for that process as well. But if an office asks whether ten people from a company dinner can each pay their share later that evening through an online link, I cannot promise that without a verified function for it. Clear wording saves awkward follow-up questions at the counter and avoids trouble when the shift is already trying to close.

The crucial difference between online, digital and terminal payment

Many people use “online payment” to mean simply “not cash,” but in my business those are three different situations. First, there is card payment in the restaurant: digital, yes, but usually still on site at a terminal. Second, there is a true online payment flow where the guest pays through a website or purchase path without standing at the table. Third, there is a later remote payment for an already open invoice. Bonzumo clearly supports the first situation through terminal integration and, in addition, online purchase of gift vouchers. For the third variant, I do not have reliable proof in the verified facts, so I do not sell it as a standard promise.

That distinction helps my team most when service is busy. If a guest calls and says, “I want to pay online,” I do not answer technically first. I ask what they actually mean: card payment on collection, a voucher purchase on our website, or settling an existing bill later. Only then do I choose the right process. That keeps people out of dead ends. It also keeps the till cleanly managed, because each case is handled where it belongs in the workflow instead of being improvised through side agreements in emails, chat messages or handwritten notes tucked beside the register.

How Bonzumo handles payment during live service

In restaurant practice, the strongest point is not some abstract payment button but the connected transaction. In Bonzumo, order, table, payment, split payment, tip and closing all refer to the same recorded data. So if four guests dine together and two want to pay cash while two pay by card, the open balance remains visible against the table until everything is settled. The team does not have to build parallel calculations outside the POS. That is the practical advantage, especially with split bills: less searching, less duplicate entry and fewer cashiering mistakes in the last minutes of service.

For my venue, that means I first set up the payment path that actually happens most often. If guests usually pay at the counter, the team needs a clean counter workflow. If they mostly pay at the table, I need to check which terminal connection fits the device and payment provider. Bonzumo itself describes that preparation as a prerequisite. So I do not simply promise, “card payment works.” I clarify in advance which device is used, who carries it, how split bills are handled and what happens if a guest has a follow-up question. That is how a feature becomes a dependable operating process. Finish a good visit with a clear payment experience.

A concrete hospitality example: evening service with a group and a voucher

Take a Saturday evening in a wine bar with a small kitchen. A group of six orders mixed items, later splits the bill by article, one person adds an €8 tip, two pay by card, three in cash, and one person also redeems a voucher that was bought online earlier. This is exactly where it matters that Bonzumo keeps partial payments, voucher use, receipts and the remaining open amount together in the same transaction. The team can see what has already been paid and what is still open. The table is only closed once the remaining balance is actually settled, which prevents rushed guesswork just before the next seating begins.

A second example looks different. A company reserves for twelve people and wants each person to pay independently online the next day. For that, I do not have a general Bonzumo promise in the verified facts. So I organise it fairly in another way: either one joint receipt on site, a split by items or equal shares during service, or one clearly agreed central payment. That is not less guest-friendly; it is cleaner. It avoids the common trap where a server promises a later online solution that was never truly set up and the unresolved problem lands with the shift lead or the office the following morning.

When I actively offer online payment to guests

I actively promote online payment only where the benefit is clear for both guests and team. The best verified case is online gift voucher purchase. Around Christmas, Mother’s Day or before company dinners, that is genuinely practical: the guest does not need to call during service, my team does not need to note down an amount over the phone, and the payment flow is intended as its own defined process from the start. Reservations can also be added to my website through an embedded booking page, but that does not automatically mean that every reservation comes with online payment. Here too, I stay precise instead of sounding broadly promotional.

For the normal restaurant visit, I would rather promote quick and clear payment in the venue than a vague remote payment idea. After dessert, guests usually do not want to learn a complicated extra payment route; they want to finish simply. So I decide by concept. In a café with lots of takeaway trade, card payment at the counter matters more. In an à la carte restaurant, clean bill splitting at the table matters more. Only when the desired flow fits our service style do I configure it. If I want to review those handovers properly, I look at them through Restaurant connections with clear setup requirements..

The questions I settle before setup so it does not break later

Before I activate anything, I work through five practical questions. First: where do guests actually pay, at the counter, at the table or at one central till? Second: are we dealing mostly with single bills, frequent splits or groups needing a hospitality receipt? Third: which payment methods do I truly want to offer, and which are only wish-list ideas? Fourth: who in the team may handle corrections, tip entry or invoice details? Fifth: which exceptions occur in reality, such as a voucher plus residual payment, part-payment in two rounds or an interrupted payment attempt? This preparation is not glamorous, but it prevents most friction later.

A typical pitfall is vague wording. When management says “online payment,” they may only mean card acceptance. The service team may hear “payment link.” Accounting may think of transactions that can be clearly assigned at closing. I solve that with a short setup sheet for each location: payment points, devices, responsibilities, permitted special cases and the escalation path if something fails. In a venue with a terrace or a second dining room, that saves real time because new staff do not have to guess. To me, that is good organisation: not the most buzzwords, but a process that still makes sense on a packed evening.

My fair conclusion for the business, the team and the guest

So I do not answer the question with a blanket yes or no. Yes, if you mean configured card payments connected to the sale, and yes for the intended online purchase of gift vouchers. No, or at least only with caution, if you mean a general later online settlement option for every open restaurant bill; on the verified facts available, I do not have reliable proof for that. That honesty is not a weakness. It protects guests from false expectations and protects my team from improvised exceptions under time pressure at the end of a busy service.

For my business, the best solution is always the one that works reliably in real service. I therefore organise payments around real situations: quick checkout at the counter, clean splitting at the table, clearly recorded tips, traceable receipts and an unmistakable remaining balance while anything is still open. If I also offer online gift vouchers, that payment route gets its own defined place as well. Then I do not end up with a loose collection of tools, but with one understandable process for guests, service and closing. That is how I judge whether a payment function is truly useful: not by the largest promise, but by a calmer final step of the visit.