Stored value is a promise about a future visit.
Balance, customer, use, and settlement need one commercial policy.
What happens, and what does it mean?
The important question is how value was issued, used, and reconciled.
How does the capability work inside operations?
Wallet capabilities are enabled by market, provider, and approved policy.
FoodTech Wallet
What it adds
Deposit, balance, and movement history
Purchases, refunds, and policy rewards
Credit for approved customers
Limit, due term, and excess prevention
Notifications, approvals, and suspension
Loyalty and self-ordering links
How it appears in operations
How does this appear in daily work?
Prepaid in-app balance
Approved corporate customer limit
Suspend after overdue
Available in
Compatible plans
- By agreement on paid plans
- Enterprise
Connects with
Products it connects with
- FoodTech Loyalty
- FoodTech Online
- LuxPay
- Accounting
FAQ
What you need to know
Can FoodTech Wallet run on its own?
FoodTech Wallet has a clear role on its own, while its value expands when connected to the relevant FoodTech products under the selected plan and integrations.
Is every capability immediately available?
Availability depends on product state, plan, market, and enabled integrations. We label the current state and never present work in progress as generally available.
How do we begin?
We map the real operating flow first, then agree the starting point, configuration, integrations, and rollout scope.
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 governs stored value?
Published use terms, market scope, and financial integration.
FoodTech Wallet
See how this product takes shape inside your operation.
Balance, customer, use, and settlement need one commercial policy.