Restaurant POS and Payments: Why Using One Platform Matters
Restaurant POS and Payments: Why Using One Platform Matters
Plenty of restaurants run the POS and the card terminal as two separate things. Two contracts, two support numbers, two sets of fees. Nobody thinks much about it until the end-of-day totals don't match, or the terminal dies on a Friday night and each supplier says it's the other one's problem.
What integrated POS and payments means
With an integrated setup, the POS sends the bill amount straight to the card terminal. The customer pays, the result goes back to the POS and the order closes. Nobody types anything.
Without integration, someone reads the total off the POS screen, keys it into the card machine, takes the payment, then goes back to the POS and closes the order by hand. It's one extra step. Do it a few hundred times a day and it costs time, causes mistakes and leaves a mess to sort out at close.
Where separate systems cost you
Keying errors
Staff mistype amounts, mostly when it's busy. The card machine has no idea what the bill was, so it charges whatever number it's given. You get undercharges, overcharges and the odd disputed transaction.
Slower payments
Every manual step at the till or the table adds a few seconds. On a busy night those seconds hold up the next table. Integration takes the keying step out completely.
Reconciliation
At close, the POS total and the terminal total should match. With separate systems someone has to check one against the other by hand, and when they don't match, work out why. With integration both totals come from the same transactions, so they match.
Two suppliers
When a payment goes wrong you can end up stuck between the POS company and the payments company, each blaming the other. With one platform there's one number to call.
Split data
If payment data sits in one system and order data in another, basic questions get awkward. Which dishes bring in the money? How many customers pay by card versus Apple Pay versus cash? When are your real peaks across every channel? You can still answer them, but it means exporting two sets of data and lining them up yourself.
Side by side
| Feature | Separate POS + terminal | Integrated POS + payments |
|---|---|---|
| Amount transfer | Typed in by staff | Sent automatically |
| Transaction time | Longer | Shorter |
| Keying errors | Can happen | No keying |
| Reconciliation | Manual | Automatic |
| Reporting | Two systems | One set of reports |
| Support | Two contacts | One contact |
| Contract | Two agreements | One agreement |
Payment rates
The headline card rate is only part of what you pay. Ask about:
- authorisation fees, charged on every transaction whatever its value
- monthly terminal rental
- PCI compliance charges
- chargeback fees
- currency conversion on international cards
A low card rate can still work out expensive once those are added on. Ask any provider for the full cost per transaction, not just a percentage.
Every channel, not just the counter
The same goes for table ordering, kiosks, online and app. If your online ordering uses a different payment processor from your POS, you have two sets of payment data, two sets of reports and two sets of fees.
On one platform, every order goes through the same payments system, whether it came from the counter, a self-service kiosk, your own app, your website or a phone call.
How Flipdish does it
Flipdish includes integrated payments in its restaurant platform. Card payments go from the terminal straight into the POS, and online and kiosk payments land in the same reports.
In practice:
- staff don't type amounts into the terminal
- end-of-day reconciliation happens automatically
- payments from every channel show up in one set of reports
- one contract and one support team cover the lot
Groups with several sites can see payments for all locations together or click into a single site, in the same dashboard they use for menus and order reports.
To see how it would work in your restaurant, talk to Flipdish.