Card data
Card payments are taken on the processor's terminal. We do not ask you to send card numbers to us. Payments are handled by certified processors and terminals.
Here is what we do to protect your data and keep service running, and what we do not claim. If a statement here is not true for your setup, we want to hear it.
Updated 2026-11-19
Card payments are taken on the processor's terminal. We do not ask you to send card numbers to us. Payments are handled by certified processors and terminals.
Your restaurant data lives in your Syrve server environment. Our own services (ordering sites, portals, digests, MCP) run on our servers. Connections are encrypted.
Code is kept in git. Data that cannot be rebuilt from the POS, such as Telegram bindings, consents, coupons, referrals and settings, is copied every night to a second server. Restore is tested monthly. A failed copy alerts our tech chat.
The MCP server uses OAuth sign-in, reader and writer roles, an audit log and tenant isolation, and has 69 automated tests. Secrets are kept in an encrypted password store or in files with restricted permissions, and never in git.
The POS stores the menu, shift and orders locally and queues operations when the internet drops. The licence is checked daily. Offline card payment depends on the terminal and is confirmed on the demo.
Support is business-hours response by default, in English and Russian. We have no public status page yet; ask us for the current status.
Not everything needs a copy of ours. Sales, menu and stock live in Syrve and can be read again from it. What we copy is what nobody else has: guest bindings to our messaging bots, consents, coupons, referrals and settings. Those go to a second server nightly, and the most critical tables more often.
A backup nobody has restored is a hope. We run a restore test once a month. If a copy fails, an alert goes to our technical chat the same day.
The MCP connection is private to your restaurant. Reader roles can look; writer roles can change prices or other records, and only if you grant them. Every action is recorded in an audit log, and one restaurant's data is isolated from another's.
Passwords and API keys are never put in code repositories or shared drives.
Card payments are taken on the processor's terminal; we do not ask you to send card numbers to us.
No. We hold neither certification ourselves. Card payments are handled by certified processors and terminals.
The POS keeps menu, shift and orders locally and queues operations. Offline card payment depends on the terminal, confirmed on the demo.
Code is in git. Data that cannot be rebuilt from the POS is copied nightly to a second server, with a monthly restore test and alerts on failure.
Only the people you authorize, through OAuth sign-in with reader or writer roles. Every action is in an audit log.
Not yet. Ask us for the current status.
We run a private MCP server on top of the restaurant's own Syrve. Claude or ChatGPT connect to it, read your numbers and, if you allow...
Read moreThe software is only part of a POS change. SmartyPOS does the migration, the menu build, the training and the custom work around Syrve, in English...
Read moreSeventy questions owners ask before they choose or change a POS, answered for Syrve as SmartyPOS sells and supports it in the United States. Where something...
Read moreSoftware is priced per month. Card processing is separate: we do not tie you to a processor, and we quote the rate on the demo.
Read more45 minutes, no pressure. We open Syrve around your concept, show what is live, and say plainly whether it is a fit.
Read moreA 45-minute call. We open Syrve with your concept in mind, show what is live today, and tell you straight whether it fits.