Step-by-step guides for everything you can hook up to DineHopper yourself — your payments, your till, your delivery platforms, your kitchen printers. Every guide below tells you exactly where to click and exactly what's real today, so you're never guessing whether a step actually did anything.
Self-serve nowFollow the steps below and it's live in minutes — nothing to wait on from us.
One step from us firstYou can fill in your details today and they'll be saved, but the last mile needs a one-time approval or setup on DineHopper's side before anything actually flows through.
Coming soonNot built yet. The button links out to the provider's own site for now — nothing is connected to DineHopper.
Payments
Take real deposits and guest payments
Money goes straight to your own account — DineHopper never holds it.
You're handed off to Stripe's own onboarding screen — enter your business and bank details there. This part is entirely Stripe's page; DineHopper never sees your bank details.
Finish Stripe's form and you're brought back to Billing. It now shows Connected, and booking deposits pay straight into your own Stripe account from that point on.
You'll need
Your business details and bank account, ready for Stripe's own onboarding form.
Good to know
If Billing shows Setup incomplete instead of Connected, click Finish setup to pick up exactly where Stripe's form left off. Once connected, Open dashboard takes you straight to your real Stripe dashboard — that's the place to check payouts, refunds, and your Stripe fees.
Point of sale
Run a different till alongside DineHopper
If your register lives on Square, Lightspeed, or Toast rather than DineHopper's own POS, save your account here so DineHopper can pull in orders (and, for some providers, push out your menu).
Square
Self-serve now
Where: POS Integrations → Point of sale → Square
Open POS Integrations and find the Square row under Point of sale.
Fill in the three fields (table below) and click Save.
Click Test connection. It shows Connected — verified the moment Square accepts your token — this is a real, live API call, not a format check.
Once verified, two buttons appear: Sync menu to Square now pushes your DineHopper menu into Square's catalog, and Pull orders now reads back completed Square sales as real DineHopper orders. Tick Automatically pull completed Square orders into DineHopper to do the second one on its own from then on.
Field
What goes in it
Your Square account / store name
Any label — just for you to recognise this connection
Access token
An access token from your Square account / Square Developer dashboard
Location ID
Your Square location ID
Good to know
A newly-arrived order needs its items to match your DineHopper menu by name. Anything DineHopper can't match on its own shows up under Item matching (POS Integrations → Order ingestion) for you to correct once — DineHopper remembers the fix after that.
Lightspeed
Self-serve now
Where: POS Integrations → Point of sale → Lightspeed
Click Connect to Lightspeed — there's no token or account ID to type in any more (as of 2026-09-16). You're taken to Lightspeed's own login/consent page.
Log in and approve access. You're brought straight back, already showing Connected — verified — DineHopper discovers your Account ID automatically, it also doesn't need typing in.
Test-push menu to Lightspeed (unverified) sends exactly one item across first — check it looks right in your real Lightspeed account, then click it again to push the rest.
Pull orders now, or the automatic toggle, works the same way as Square.
Worth knowing before you rely on it
This targets Lightspeed Retail (R‑Series). Lightspeed Restaurant (K‑Series) is a different product with its own separate registration and isn't built yet — check which one you're on before connecting. Connecting itself is real OAuth2, confirmed directly against Lightspeed's own docs — but menu push and order pull are still lower-confidence than Square's on the exact response shape: Lightspeed's own API reference blocked automated verification of that one detail, which is exactly why menu push deliberately starts with one item instead of your whole menu. Double-check the first few pulled orders against Lightspeed directly.
Toast
One step from us first
Where: POS Integrations → Point of sale → Toast
Fill in an account label and your Restaurant GUID (from your Toast account) — there's no separate credential field here, since Toast authorises DineHopper at the account level, not per restaurant.
Save, then Test connection.
Once verified, Pull orders now (or the automatic toggle) reads back completed Toast sales as DineHopper orders.
Why this one's marked "one step from us"
Toast's completed-order pull is real, but it's blocked until DineHopper finishes its own pending Toast partner approval — a one-time step on our side, not yours. Your credentials save and verify today; ask us for a status update if you're waiting on it. Separately, and permanently: Toast's own Menus API is read-only for third-party apps, so DineHopper can never push a menu into Toast — that's not a "not built yet," it's a limit of Toast's own API.
School canteens
LunchFox → KPOS
For school canteens whose till is KPOS, not DineHopper's own POS: pulls the day's LunchFox parent pre-orders and pushes them into KPOS as one combined order.
Set up the LunchFox bridge
Self-serve now
Where: POS Integrations → Order ingestion → LunchFox → Set up (opens its own settings page)
Tick Enabled, then fill in your LunchFox vendor id, LunchFox username, and LunchFox password.
Enter your KPOS ordering URL (the same link KPOS itself uses, e.g. https://www.kpos.com.au/<your-venue>/index_table.php) and your KPOS table number, then Save.
Under Menu mapping, add one row per LunchFox item: its exact LunchFox item name, the matching KPOS barcode on your "‑SCHOOL" menu, and an optional price.
Click Run now to test it immediately — it also runs automatically every morning on its own from here on.
You'll need
Your LunchFox vendor id and login, your KPOS ordering URL and table number, and a barcode for every LunchFox item you sell.
Good to know
Your username and password are encrypted before they're stored. If saving fails with an encryption error, that's a one-time setup step on DineHopper's side (a missing server secret) — ask us to check it, it's not something wrong with what you typed.
EFTPOS terminals
Pair a physical card terminal
Where: Configure → Payment terminals (also shown on POS Integrations & Terminals). Cash and split payments at the till work regardless of whether a terminal is paired.
Revolut Terminal
Self-serve now
Give the register a Register label (e.g. "Register 1") and choose Revolut Terminal as the provider.
The next field relabels itself to Revolut secret key — generate one from Revolut Business → Merchant overview → Merchant API settings → Generate, and paste it in.
Click Pair terminal. DineHopper checks the key against Revolut's own Merchant API in real time.
Worth knowing before you rely on it
This confirms your Revolut secret key is real and accepted — it does not yet confirm that Revolut's API can push a payment to a paired physical terminal the same way Linkly and mx51 do. Test a real in-person payment before depending on it for service.
Linkly & mx51
One step from us first
Give the register a Register label and choose Linkly or mx51 as the provider.
Enter the pairing code shown on the terminal's own screen, then click Pair terminal.
Why this one's marked "one step from us"
Pairing fails with a clear, honest error until DineHopper's own Linkly or mx51 vendor registration goes live — a one-time step on our side. Ask us for a status update if you're waiting on either one.
Once any terminal is paired
A Surcharge % field appears per register — this is disclosed to the guest on the till before their card is charged, and added on top of the total, never hidden in the price.
Kitchen
Kitchen printers (split printing)
On top of the digital Kitchen Display, route each station's items to its own physical printer — the grill ticket prints at the grill, the drinks ticket prints at the bar.
Add a station printer
Self-serve now
Where: Configure → Kitchen printers
First, make sure at least one menu item has a Station set (Menu → open an item → Station) — this is the same station value the digital Kitchen Display already groups tickets by. A printer has nothing to route to until at least one item has one.
Give the printer a Name (e.g. "Grill printer") and its ePOS-Print URL — the network address of an Epson ePOS-Print compatible printer, e.g. http://192.168.1.51/cgi-bin/epos/service.cgi?devid=local_printer&timeout=10000.
Tick every Station this printer should cover, then click Add printer.
You'll need
A network-connected printer that speaks Epson's ePOS-Print protocol, and its local network address.
Worth knowing before you rely on it
This protocol hasn't yet been verified against a real printer on our end, so send a real test order through before service. It fires automatically the instant an order goes to the kitchen (and again for anything added to an already-open order) — there's no manual "print" button. If a station printer can't be reached, that fails silently and the order still shows correctly on the digital Kitchen Display, so nothing here is ever the only record of an order.
Delivery platforms
UberEats & DoorDash
Where: Website tab. These are two separate cards that do very different things — read both before deciding which you need.
Order links
Self-serve now
Open Website → Order links.
Paste your existing Uber Eats link, DoorDash link, and/or your own Pickup / order-ahead link.
Click Save — they show up as real order buttons on your public DineHopper page immediately.
Good to know
This is just links, not an integration — a guest clicks through to your existing UberEats or DoorDash listing exactly as it already is. It needs nothing from DineHopper's side and works the same whether or not you also set up Order ingestion below.
Delivery platform order ingestion (Beta)
One step from us first
Open Website → Delivery platform orders.
Tick Bring in UberEats orders and/or Bring in DoorDash orders, and enter the store ID from your UberEats merchant dashboard or DoorDash merchant portal.
Click Save.
Why this one's marked "one step from us"
This is different from Order links above: once live, an order placed on UberEats or DoorDash lands directly on your till and kitchen ticket strip, automatically. It isn't live yet — DineHopper hasn't finished its own UberEats/DoorDash partner registration, a one-time step on our side, not yours. Your store IDs save today; nothing will flow through until that registration finishes. Ask DineHopper support for a status update.
Website
Point your own domain at DineHopper
Your DineHopper /site/ link keeps working either way — a custom domain is an upgrade, not a requirement.
Custom domain
Self-serve now
Where: Configure → Custom domain
Enter Your domain (e.g. order.yourcafe.com) and click Add domain.
Add the TXT record DineHopper shows you at whoever hosts your domain's DNS (your registrar, or Cloudflare if it's already there) — this proves you own the domain.
Add a CNAME record pointing your domain at the fallback address DineHopper gives you.
Click Check status until it turns to Live. From that moment, your own domain serves your public site directly.
You'll need
Access to your domain's DNS settings (your registrar's dashboard, or Cloudflare if that's where your DNS lives).
If this section shows a setup note instead of the form
Custom domains need Cloudflare for SaaS switched on for the account first — a one-time step on DineHopper's side. Ask us and your /site/ link will keep working in the meantime regardless.
Accounting
Xero, MYOB, QuickBooks
Push bills and wages into your ledger
Coming soon
Honest status
These three tiles appear on Bills, Wages, and Configure so you can see what's planned — there's no adapter built yet for any of them. Clicking Connect today just opens the provider's own site; nothing you enter there talks to DineHopper. The intended workflow, once built: a bill entered on Bills, or a pay run saved on Wages, pushes straight into your connected ledger as a bill or payroll journal instead of only living in DineHopper. We'll update this guide the day any of the three goes live.
Other
A few more, while we're being thorough
Square, Tyro & Zeller — as an alternative to Stripe
Coming soon
Where: Billing → Guest payments
Honest status
These three sit alongside Stripe on Billing as processors we might support later. None has an adapter today — the tiles link out to each provider's own site so clicking does something honest instead of nothing. Stripe is the one that's real and self-serve right now (see the Payments section above).
Browser push notifications
Self-serve now
Where: POS Integrations → Push notifications
Tick Notify this restaurant's staff.
Choose which events you want alerts for: New booking request, New self-service order, Item auto-86'd (sold out), Low stock warning, and/or the daily Overdue bills digest. Click Save event choices.
Click Enable notifications on this device and accept the browser's own permission prompt. This step is per device, per browser — repeat it on every staff phone, tablet, or till you want alerts on.
If this card shows a setup note instead of the toggles
Push notifications need a one-time setup step on DineHopper's side for the whole account. Ask us to switch it on — nothing you can do from this page fixes that on your own.