Question 1

Do guests need to download an app?

Accepted Answer

No. The whole ordering flow runs in the browser. Guests open the camera, scan, and the menu opens.

Question 2

Which payment providers are supported?

Accepted Answer

Viva Wallet and Stripe. You choose in your dashboard settings. The guest does not see the difference.

Question 3

Does TabbPay work with my existing POS?

Accepted Answer

Yes. TabbPay connects to the POS you already run, with no new hardware and no change to your kitchen workflow. We currently integrate with symPOSium and HIT POS, the systems most common in Greek hospitality, and we partner with your POS vendor during onboarding when you are on a different one. The kitchen ticket keeps printing the way it does today.

Question 4

What happens after the sixty-day trial?

Accepted Answer

Your card is charged €49 a month (Basic) or €99 a month (Pro). We email you seven days before the trial ends. You can cancel from the dashboard at any point.

Question 5

How is the data handled?

Accepted Answer

TabbPay does not store payment card data. Viva Wallet and Stripe handle that, both at PCI-DSS Level 1. We collect the minimum personal data we need to operate the service, under GDPR. You can request a full data export or deletion at any time by writing to privacy@tabbpay.com.

Question 6

How does QR table ordering work, step by step?

Accepted Answer

Each table has a printed QR code. The guest opens their phone camera, scans it, and the menu opens instantly in the browser — no app download, no account needed. They browse, add items, and place the order. The kitchen receives it immediately. At the end of the meal the guest pays from the same screen with a card or digital wallet.

Question 7

What is the transaction fee?

Accepted Answer

TabbPay charges a 0.50% platform fee per transaction. The bank interchange fee and the Viva Wallet or Stripe processing fee are separate and depend on card type. The combined cost is typically lower than a handheld POS terminal, which usually adds 1% or more on top of interchange.

Question 8

Can guests split the bill between them?

Accepted Answer

Yes. Guests can split equally across the number of people at the table, or each person pays for the exact items they ordered. No calculator, no awkward cash rounding.

Question 9

How long does it take to get set up?

Accepted Answer

Most venues finish onboarding in under an hour. You upload your menu, connect Viva Wallet or Stripe, and print QR codes for each table. The dashboard walks you through every step.

Identifier	Type	Surface	Purpose	Duration
`__session`	Cookie (`httpOnly`, `Secure`)	Dashboard, Staff	Clerk authentication session token	End of browser session
`__client_uat`	Cookie	Dashboard, Staff	Clerk client-side authentication timestamp	End of browser session
`__tabbpay_dt`	Cookie (`httpOnly`, `Secure`, `SameSite=Strict`)	Guest ordering app	HMAC-signed device-binding token; enables the Platform to associate a returning device with its open table session and to enforce per-table device limits	3 hours
`tabbpay_locale`	Cookie	Landing site	Persists the user's language preference (Greek or English)	1 year
`tabbpay_cookie_consent`	`localStorage`	All surfaces	Records the user's consent decision (`accepted` or `rejected`) so the banner is not re-displayed on each visit	Until cleared by the user
`tabbpay_session`	`localStorage`	Guest ordering app	Active table-session reference (session identifier, venue identifier, table identifier, expiry timestamp)	Until session expiry (typically 3 hours)
`tabbpay_device_id`	`localStorage`	Guest ordering app	Random UUID identifying the browser device; allows session continuity if the tab is closed and reopened	Persistent for the device
`tabbpay_device_token`	`localStorage`	Guest ordering app	Mirror of `__tabbpay_dt` for use by client-side fetch logic	Until session expiry
`tabbpay_cart`	`localStorage`	Guest ordering app	Items currently in the Guest's basket	Until checkout or session expiry
`tabbpay_locale`	`localStorage`	Guest ordering app	Language preference for the ordering interface	Persistent for the device
`tabbpay_split_claims_<splitId>`	`localStorage`	Guest ordering app	Portions of a split bill claimed by the present device	Until bill is settled
`tabbpay_last_venue_id`	Cookie	Dashboard	Restores the most recently used venue when a Business Customer signs in again	400 days
`tabbpay_dash_rt`	`sessionStorage`	Dashboard	Short-lived refresh token used to recover from Clerk-handshake errors	End of browser tab
`tabbpay_dash_org_sync_v1`	`sessionStorage`	Dashboard	Organisation-sync retry counter (internal state)	End of browser tab
`tabbpay_selected_plan`	`localStorage`	Sign-up flow	Plan selected by the prospective Business Customer prior to completing sign-up	Until sign-up completes
`tabbpay_business_shape`	`localStorage`	Sign-up flow	Business legal form selected by the Business Customer during the onboarding wizard	Until onboarding completes
Service Worker registration	Browser cache	Staff	Service worker that enables push notifications on the Staff app	Until the Staff member uninstalls or the worker is unregistered

Identifier	Type	Surface	Purpose	Provider
Vercel Web Analytics	Cookieless first-party measurement (no persistent identifiers; hashed daily)	Landing site	Aggregate page-view counts and referrer attribution	Vercel Inc.
Sentry session replay	Cookie and in-memory buffer	Landing site, Dashboard, Staff	Records replay of the user interaction immediately preceding an unhandled error, with form inputs and text content masked at source by the replay SDK	Functional Software, Inc. (Sentry)

Cookie Policy

1. Classification

2. Strictly Necessary Cookies and Storage

3. Optional Cookies and Storage

4. How to Manage or Withdraw Consent

5. Contact