How to enable and configure the site’s payment methods so daily closures match the actual takings.
Payment methods configured in KlyraOS must exactly reflect what is actually accepted at the till, otherwise the daily closure and POS reconciliation become inaccurate. Configuration is done per site and should be updated whenever a payment provider changes.
KlyraOS ships with the most common restaurant methods, such as cash and cards, ready to use. Each site can enable or disable methods based on what it actually accepts at the counter.
Beyond the standard methods, you can add meal vouchers or other local payment instruments, giving each one a recognisable name that will show up in the cash closure and in reports.
If several sites share the same payment provider, keeping the same method names across sites makes it easier to read consolidated reports at organisation level.
The methods configured here are the ones shown in the cash closure and compared with the amount imported from the POS: a missing or duplicated method is one of the most common causes of reconciliation discrepancies.
Are payment methods the same across all sites?
No, each site configures its own methods, but using consistent names is recommended for consolidated reports.
Can I disable a method without losing history?
Yes, disabling prevents new use but does not delete past closures that already include it.
Do I need one method per card provider?
Usually a generic "cards" method is enough, unless you want to separate data by provider.
What happens if I add a method after months of activity?
The new method is available immediately for new closures, without affecting ones already recorded.
Was this guide helpful?
Still need help?
Describe the issue: page, location, organisation and role are attached automatically.
Contact support
