Operations

Taking Payments Online: What Restaurants Need to Get Right

Online payments for restaurants without the jargon: cash on delivery vs prepaid, which methods suit which order type, refunds, and what a chargeback really is.

Ordering.ToolsNovember 18, 202611 min read
A guest paying for a restaurant order on a phone at checkout

It is 19:40 on a Friday. A driver has been standing at a door on the fourth floor for six minutes with a bag of food that has gone cold. Nobody is answering. The order was forty euros, cash on delivery, placed two hours earlier by somebody who has since decided to eat somewhere else. The food is a write-off, the round trip is an hour of a driver you are paying for, and the phone number on the order goes to voicemail.

Nobody enjoys thinking about payments. It is the least interesting part of running a restaurant and the part where the smallest decisions cost the most. But the question is not "should we take cards" — almost everyone does by now. The question is which methods you switch on, for which kind of order, and what happens on the days when something goes wrong. That is what this guide is about.

Cash on Delivery Versus Paying Up Front

Cash has one enormous advantage and operators are right to defend it: it converts. There is no card to find, no bank app to open, no three-digit code to hunt for on the back of a wallet, and no fear about who is being handed a card number. In markets where people still shop this way, removing cash on delivery removes orders — that is not a superstition, it is a real drop you can see in the first week. What it costs you is spread out and therefore easy to miss. A cash order is a promise, not a sale: it can evaporate at the door, and it does, most often on the highest-value orders, on the worst nights, at the addresses furthest away. Your drivers carry change and therefore carry risk. Somebody has to count a till at 02:00 and reconcile it against a report. And a cash order tells you nothing about the guest — no card on file, no verified identity, nothing to appeal to when the same address does it again next month.

What paying up front actually changes

A paid order is a decision that has already been made. The guest cannot change their mind at the door, so the abandonment moves earlier — to the checkout page, where it costs you nothing but a page view. The kitchen cooks against money that already exists. The driver carries no cash. And the no-show problem stops being a food-cost problem and becomes, at worst, a refund conversation. It is a genuinely different business on delivery, on catering, on large orders, and on anything scheduled for a future date.

Do not remove cash on delivery overnight in a market that still runs on it. Add card as the default, put it first in the list, and let the split move on its own. Watch it for a month. If cash has fallen to a small minority of delivery orders, you can then restrict it — to a distance, to an order value, or to repeat customers — with evidence rather than a hunch.

Card Payment on Your Own Site, and the Redirect Nobody Explains

Here is what actually happens when a guest pays by card on your ordering page, described honestly. They press Pay. The browser leaves your page and opens a payment page hosted by the bank or the card processor. They enter their card there, their own bank may ask them to confirm it in their banking app, and then they are sent back to your site, where the order shows as paid. The whole detour takes a few seconds and the guest sees a page with your restaurant's name and the amount on it.

Operators sometimes read that as a weakness — "why does my customer leave my website?" It is the opposite. The card number is typed on the processor's page, into the processor's systems, and never touches your restaurant, your website or your staff. That means there is nothing on your side to be stolen, no card data in your database, and none of the compliance burden that handling card numbers yourself would drag in. It is also the flow the guest's own bank expects, which is why the confirmation step in their banking app works at all. The redirect is the security property. A checkout that never leaves your page is either doing something clever and expensive, or something you would not want it to do.

Wallet payments on a phone

Most of your orders arrive from a phone, and on a phone a card is a small object in another room. Apple Pay and Google Pay remove that entirely: the guest confirms with a fingerprint or a face and the card details come from the wallet they already set up. Nothing is typed. On mobile this is the shortest path between wanting your food and having paid for it, and for a guest ordering from you the first time, it also side-steps the moment of hesitation about entering a card into a restaurant site they have never used. Switch them on if your payment provider offers them. There is no downside and the setup is a checkbox.

Paying the Bill at the Table From a Link

The other half of online payments has nothing to do with delivery. A table finishes at 22:15 and then waits — for a server to notice, for the terminal to be free, for the bill to be printed, for the card machine to come back. That wait is dead time on a table you could have turned, and it is the last thing the guest remembers about the evening. A bill that can be opened as a link, split between the people at the table and paid from their own phones removes the queue for the card machine entirely. Several people can pay their share of the same bill without anybody dividing anything on paper, and the total settles as they go. The staff-side benefit is quieter but bigger: nobody is walking a terminal across a full room during the busiest hour of the night.

Refunds and Chargebacks: The Two Words Worth Understanding

  • •A refund is you deciding to give the money back. You issue it — from your admin panel where the payment provider allows it, or from the provider's own dashboard where it does not. Check which of the two your provider does before you need it, not on the night a guest is waiting.
  • •A refund goes back to the card it came from. Not to a different card, not in cash at the door, not to a bank transfer the guest suggests. That rule is not negotiable and it is worth saying out loud to a guest who asks, because it sounds like an excuse and is not one.
  • •It is not instant. Your side is done in seconds; the money appears on the guest's statement in a few working days depending on their bank. Say "a few working days" when you issue it, or you will get the phone call on day two.
  • •A partial refund is usually the right instrument. One missing dish out of a family order is a refund of that dish, not of the evening. Guests accept partial refunds far more readily than operators expect, provided somebody explains the number.
  • •A cash order has no refund mechanism at all — only you, handing money back, with nothing recorded unless you record it. That is a reason to prefer card on high-value orders, not just a footnote.

A chargeback is a different animal, and the difference matters: a refund is you being a good restaurant, while a chargeback is you losing an argument nobody told you about. It is the cardholder going to their own bank and disputing the charge, rather than coming to you. The bank pulls the money back from your account and asks you to prove the transaction was legitimate. You usually find out days or weeks after the food was eaten, there is a fee attached whichever way it ends, and the process is paperwork you do not want. The good news is that restaurant chargebacks are overwhelmingly caused by a handful of avoidable situations, not by fraud.

  • •An unrecognisable name on the statement. If the charge reads as a company name the guest has never heard of, they will report it as fraud in good faith. Make sure the descriptor on the card statement is the name above your door.
  • •A charge with no confirmation. Every paid order needs an immediate email or message with the items, the total and the order number. A guest with a receipt argues with you; a guest without one argues with their bank.
  • •A double charge that was never a double charge. A pending authorisation that later disappears looks exactly like a second charge to a guest reading their banking app. Explain it once, calmly, before they escalate.
  • •A refund you promised and did not issue. This is the single most common cause. The moment you agree to a refund, issue it — a chargeback filed while your refund is in flight ends with the guest getting the money twice and you paying the fee.
  • •An order that never arrived and nobody answered the phone about. Answer the phone. Most chargebacks are a guest's second choice after failing to reach a human.

Which Methods to Switch On, Per Order Type

The instinct is to offer everything everywhere, on the theory that more choice means more sales. It does not. A checkout with six payment options is a decision the guest did not want to make, on the last screen before their money leaves — and each option you show is one your staff has to support, reconcile and explain. Choose per order type instead.

  • •Delivery — card and wallet first, cash optional and last. If you keep cash, consider capping it by distance or order value: the far, expensive orders are exactly the ones that go wrong at the door.
  • •Pickup — either, genuinely. The guest is standing in front of you, so a no-show costs you the food and nothing else. Prepayment here is a convenience, not a defence.
  • •Dine-in at the table — the bill link and your terminal. Cash always stays for the table; nobody has ever been talked out of paying a restaurant bill in cash.
  • •Scheduled and pre-ordered — prepaid only. An order for next Saturday that has not been paid for is a hope. You are buying stock against it.
  • •Catering, group and large orders — a deposit at minimum, ideally the whole amount, and an invoice if a company is involved. This is where an unpaid cancellation actually hurts.
  • •Anything on a busy fixed-price night — prepaid, no exceptions. That case has its own article, on ticketed dinners.

Two practical rules on top of that. Whichever provider you use, run a real transaction on your own card before you go live and then run a refund of it — the refund is the half nobody tests, and it is the half you will need in front of a guest. And if you sell in more than one currency or across more than one location, check that each venue is wired to its own payment account; money settling into the wrong one is a bookkeeping problem that takes months to unpick. Beyond that, be honest about what payments are: they will not make anybody order from you. They quietly decide how many of the people who already wanted to order actually finish, how many of them turn up, and how much of your week goes into chasing money that should have arrived on its own. Get the methods that matter right, test the refund, and then stop thinking about it. Our payment processing feature page has the setup detail per provider, and if you are weighing prepayment for a fixed-price night, the guide to ticketed dinners takes it further.

Frequently asked questions

Should a restaurant accept cash on delivery or require payment up front?

Both, in that order of preference. Card and wallet payment first, because a paid order cannot evaporate at the door and the driver carries no cash. Keep cash on delivery if your market still uses it — removing it overnight removes orders. The middle path is to cap cash by distance or order value, since the far, expensive orders are the ones that fail at the door.

Why does the customer leave my website when they pay by card?

Because the card number is typed on the payment provider's own hosted page, not yours. That is a security property, not a shortcoming: no card data ever touches your restaurant, your site or your database, so there is nothing on your side to steal, and it is the flow the customer's bank expects when it asks them to confirm in their banking app. The detour takes a few seconds and returns them to your order page.

How do refunds work for an online restaurant order?

You issue the refund yourself — from your admin panel where the payment provider supports it, or from the provider's own dashboard where it does not. The money always returns to the card it came from, never to a different card or in cash, and it appears on the guest's statement in a few working days. A partial refund for one missing dish is usually the right instrument.

What is a chargeback and how does a restaurant avoid one?

A chargeback is the cardholder disputing a charge with their own bank instead of contacting you; the bank pulls the money back and asks you to prove the transaction. Most restaurant chargebacks come from avoidable situations: an unrecognisable name on the card statement, no confirmation email, a pending authorisation mistaken for a double charge, a promised refund that was never issued, and an undelivered order where nobody answered the phone.

Which payment methods should I offer at checkout?

Fewer than you think, and different ones per order type. Delivery: card and wallet first, cash optional. Pickup: either. Dine-in: a bill link plus your terminal, and always cash. Scheduled, catering and fixed-price event nights: prepaid only. Every extra option on the checkout screen is one more decision for the guest and one more thing your staff has to reconcile.

Try Ordering.Tools for Free

Set up your digital menu in under 2 minutes. No credit card required.