At the table — card-present
Server taps "Charge" on the waiter app or POS. The bill amount, the tip rule, and the table reference go to the terminal. Card tap or chip. Receipt comes back. Order closes.
Payment Integrations
We tell the POS to charge. We don't hold your money.
dojofood orchestrates the payment — your terminal and your processor do the rest. No middleman on your settlement.
What we are
What dojofood is, and what dojofood isn't.
dojofood is not a payment processor. We are not a bank. We are not a PSP. We don't open a merchant account for you. We don't settle your funds. We don't take a cut of your card volume.
What we do is simpler. When a server hits "Charge" on the waiter app, or a customer pays through a QR menu, dojofood sends one instruction to the POS terminal or the online checkout: charge this amount, this tip, this table. The terminal does its job with your processor. The processor talks to the card network. The money lands in your account — the same account it would have landed in before dojofood existed.
Then the terminal sends one thing back to us: a confirmation and a receipt. We close the order, print the slip, log it against the ticket, and move on.
Your money moves on its own rails. We just orchestrate the conversation.
Three places a guest pays
One model, three contexts.
The orchestration works the same way regardless of where the payment happens.
Online — card-not-present
A customer ordering through your QR menu, online ordering page, or branded app pays inside the checkout. dojofood passes the order amount to the online processor; the customer enters their card; we receive the confirmation. The ticket is fired to the kitchen the second the payment clears.
QR and mobile wallets
Apple Pay, Google Pay, and local mobile wallets ride on the same rails — they are presented by the terminal or the online checkout, not by us. We tell the terminal "accept these methods"; the wallet does its job.
One model, three contexts. Same orchestration shape every time.
Who we plug into
We connect to your existing stack, not the other way around.
Card terminals
Terminals and processors
Major bank-issued POS terminals running standardised terminal protocols, including bank-owned acquirers and PSPs. If your bank issues the device, we work with the device. We do not need you to switch banks.
Online
Online payments
Local PSPs and gateways for online card payments, including the ones your operators already use for QR-menu checkout. Mobile wallets are supported through the gateway layer.
Regional acquirers
Terminals and online
Mainstream acquirers and PSPs in the markets we operate in. PIN, contactless, Apple Pay, Google Pay over standard terminal and online APIs.
Missing yours?
About two weeks
Tell us on the demo call. New processor integrations take about two weeks once we have access to the API and a test terminal.
The honest version: we add the integrations our operators actually need. We don't list every PSP on earth as "supported" — we list the ones we've put in production.
Your processor stays yours
The difference between a payment-locked POS and a real POS.
This is the one operators ask about first, so we'll answer it first.
You keep your processor relationship
Whoever you signed with for your terminal and your online payments — you still own that contract. dojofood does not insert itself between you and your bank.
You keep your rates
Whatever you negotiated for card-present, card-not-present, and per-transaction fees — that's what you keep paying. We don't take a percentage. We don't take a basis point. We don't share a commission with your processor. We have no financial interest in which processor you use.
Switch processors without switching dojofood
If your bank raises your rate next year and you move to a different acquirer, you change one integration setting in dojofood and keep working. The waiter app, the POS, the KDS, the marketplace orders, the catalogue — none of it changes.
Some competitors won't let you breathe without their card processing. We won't compete with your bank.
Receipts & fiscal compliance
The boring detail that matters: the receipt always matches the ticket.
Fiscal devices
Fiscal receipts on certified hardware
Printed on the certified fiscal device you already use. dojofood drives the receipt content; the certified printer handles the fiscal signature and reporting. Electronic-archive flows are supported through the same path. If the local receipt rule changes, we update the template — you don't reprint a new device.
Digital + thermal
Digital by default, fiscal per country
Digital receipts by default; thermal printer where the operator wants one; fiscal compliance handled per country to local certification standards. Receipt content includes order, items, modifiers, tip, tax line, branch ID, ticket number — whatever the local rule needs.
Operators reconciling at end-of-night don't find an order on the KDS without a matching slip, or a slip without a matching order. One queue means one record of what happened.
Tips, refunds, voids
Done cleanly.
Tips
Set the tip rule per channel — card-present prompt on the terminal, percentage suggestions in the online checkout, no-prompt for marketplace orders that already include a tip line. Tip amounts log against the server, the ticket, and the shift report.
Refunds and voids
A void cancels the ticket and reverses the authorisation on the terminal before settlement. A refund triggers a return through the same processor that captured the charge — full or partial, item-level if you want it that way. Both actions are tied to a role permission, so not every server can refund €120 at 11pm on a Saturday.
Partial payments and splits
Split by item, by guest, or by amount. Each split is a separate charge to the terminal — multiple cards on the same ticket close cleanly without manual maths.
The orchestration handles the conversation. The processor handles the money. The receipt always reflects what actually happened.
What we don't do (yet)
Honest panel. Same posture as the rest of the site.
On the roadmap
- Currency. EUR and TRY live. GBP on the roadmap, lined up with our UK rollout.
- Pay-by-link from inside the POS. In flight — landing next quarter. Useful for phone orders and corporate accounts.
Not our job
- Direct merchant onboarding. We don't open a processor account for you. If you don't have one yet, we'll point you at the local options and step out of the way.
- If a payment integration matters to your operation and it isn't here, tell us on the demo. We won't pretend it works when it doesn't.
Have questions? Let's talk.
See your money stay on your rails.
20 minutes with our team. Bring your current terminal vendor, your online payment gateway, and your processor contract. We'll show you exactly where dojofood sits — and where it doesn't. Real human, your language, under 2 hours if anything breaks. Monthly billing. No payment-processing lock-in. We don't hold your money.