An invoice can carry its own payment path.
A link moves amount, currency, and order reference into a payment session.
What happens, and what does it mean?
The customer needs to know what is being paid and whether it succeeded.
How does the capability work inside operations?
FoodTech accepts status only through an enabled, trusted provider integration.
QR Code & Payment Link
What it adds
QR or link tied to the supported order or amount context
Browser payment where the provider supports it
Payment state returned through the provider integration
Use with Customer Display or digital channels when enabled
How it appears in operations
How does this appear in daily work?
QR on Customer Display
Payment link from a digital channel
Digital receipt after confirmation where supported
Available in
Compatible plans
- FoodTech Free
- Growth Flex
- Pro Branch
- Scale
- Enterprise
Connects with
Products it connects with
- LuxPay
- Customer Display
- Self Ordering
- FoodTech POS
FAQ
What you need to know
Does QR Code & Payment Link require an app on the customer phone?
No. The secure payment link can open in the browser, while app and NFC paths are used only when supported and enabled.
Does the customer display expose internal data?
No. It shows only customer-safe invoice context such as items, total, and payment status, never internal permissions or sensitive operating data.
How is payment confirmed?
FoodTech does not close the invoice from the customer screen alone. It waits for a trusted provider result, then updates the order and receipt.
Does the operation need a permanent internet connection to keep moving?
Connectivity should add capability, not become the operation’s power switch. Where Offline mode is supported, core work continues locally, events are retained, and synchronization resumes when connectivity returns. Operations that require live verification, including some payment or sensitive actions, remain Online by design. Offline scope varies by product, device, and activation; the goal is to keep work moving even when the network does not.
What if the internet is available — but slower than the operation?
FoodTech does not assume a perfect network. Where supported, every action does not wait for a full server round trip: local state, asynchronous (Async) synchronization, and safe retries keep work moving without duplicating operations. The team can continue what is safe to continue while the system catches up with the network; payments and other sensitive actions still require explicit verification when needed.
Before you start
What must a payment link preserve?
Order reference, amount, currency, and verifiable state.
QR Code & Payment Link
See how this product takes shape inside your operation.
A link moves amount, currency, and order reference into a payment session.