Several tills at once
Several devices can work on the same data at once, even offline. As soon as they reconnect, the changes merge on their own, and no central server has to decide which one wins.
What makes us different
Typical payment apps run on the provider's server. Your data lives there, you sign in through it, and payment information flows through it. Payky has no such server. We do run a few — for the encrypted backup and some optional extras — but you can sell and take payments without them.
Start PaykyComparison
| What we compare | A typical cloud app | Payky |
|---|---|---|
| Where the data is | On the provider's server | On your device |
| Sign-up | Email, password, often ID documents | None |
| Who stands between the customer and you | The provider's server | Nobody of ours |
| When the server goes down | You can't sell | You keep selling |
| Who can read your sales | The provider, and anyone who gets into their database | Only you |
| When the company shuts down | Will you manage to download an export in time? | You keep the app and the data |
| Source code | Closed | Open (MIT) |
A typical cloud app
Payky
A typical cloud app
Payky
A typical cloud appThe app sends everything to the provider's server, and only that server talks to your bank. Meanwhile it holds every merchant's data.
PaykyThe money goes straight to your account, and your phone asks your bank about the payment directly.
Local-first
Your catalog, bills, payments and settings are stored on your own device. The app works with them directly, so it responds instantly and doesn't need the internet to sell. Sync is a handy extra, not a requirement.
EET never keeps a customer waiting: the sale goes to the Financial Administration in the background.
Several devices can work on the same data at once, even offline. As soon as they reconnect, the changes merge on their own, and no central server has to decide which one wins.
Every tap is saved on the device straight away. Nothing waits for a server to answer.
No sign-up
On first launch, the app creates a cryptographic key, and that key is your account. Think of it as the key to a safe with no locksmith: whoever has it can open the data, and if you lose it, nobody can open it for you.
Sign-up is mostly for the provider's benefit. They need to know whose data sits on their server and let only you in. Payky keeps none of your data on a server, so there's no account to create. What lets you in isn't our server, it's your key.
You can write the key down as a recovery phrase — a list of words. Whoever has it has the account: they can open the data and the bitcoin wallet. To move the account to a new device, you scan a QR code from the current one and confirm a six-digit code. The phrase never leaves the device.
Payky never holds or forwards your money. A bank transfer goes from the customer's bank straight to your account, which your bank has already verified. Bitcoin lands in a wallet only you hold the keys to. So the app has no money of yours that would require verifying you.
This is what a recovery phrase looks like. It's only a sample; yours will be different.
| What happens | Business data | Bitcoin in the wallet | Money in the bank account |
|---|---|---|---|
| I lose my phoneI enter the phrase on a new device, and the data downloads from the relays. | Safe | Safe | Safe |
| I lose the recovery phraseAs long as I have the phone, I can copy the phrase again in the settings. | Safe | Safe | Safe |
| I lose both the phone and the phraseAnd the account is on no other device. | Lost | Lost | Safe |
There's no password reset by email, and we can't give you back the data or the bitcoin, because we don't have them. So write the phrase down and keep it somewhere safe, away from your computer.
Backup and sync
Data is encrypted right on your device, and only unreadable noise ever leaves it. Only someone with the key can read it.
A typical cloud app
Payky
Espresso 2× · CZK 130 · 14:32 · table 3 · QR payment9f3a e71c 04bd c2a8 5e19 b7f0 1d6e 83c4 …With a cloud app, the provider holds the key to your data. So they can read it, and so can anyone who gets to the server: support, engineers, sales, or an attacker in a breach. With Payky, the relay sees only encrypted noise, and only you have the key. Not even our support can see your data — they only know what you tell them.
Payments
Money goes straight to your account or your wallet. No Payky server stands in its way.
QR bank transfer
Bitcoin (Lightning)
Card
Automatic payment matching only works with Fio banka for now. With other banks, you confirm the payment by hand.
Lightning is a network for instant bitcoin payments. Payky issues an invoice from your Spark wallet, which runs right inside the app. The payment lands in your wallet, and only your device holds its keys. Transactions are processed by Spark network operators and a Lightning gateway provider — they see the amount and the time. The app gets the exchange rate for your currency from the public Yadio service.
On a device with a Switchio terminal, Payky only hands the amount to the Switchio app. Switchio and the merchant's bank then process the card, just as with any other terminal. Card details never reach Payky.
Cash: just you and the customer.
Security
There's no single place holding every merchant's data, so there's nothing to steal in one go.
A typical cloud app
One database with every merchant's data: a single breach is enough.
Payky
Each device on its own, and locked: nothing to attack all at once.
A server holding the data of thousands of merchants is an ideal target: one breach and the attacker has everything. And most breaches don't come from cracked encryption, but from a misconfigured database, a stolen admin password or an employee with access to everything. Payky has no such server. An attacker would have to break into each device separately, and on the relays they'd find only encrypted data.
Whoever holds your data can analyse it, sell it, hand it over on request or lose it. With Payky, only you can read it, and nobody can make us hand it over, because we don't have it.
The recovery phrase, the bank token and the EET certificate are stored in the account data, which only ever syncs encrypted. Your device signs EET sales and sends them itself, with no one in between.
A PIN can lock the settings, refunds and other sensitive actions, so staff can only sell. To be clear: the PIN keeps out the curious at the counter, not an attacker with full access to the device. Real protection comes from the recovery phrase and the phone's own lock.
Payky uses no analytics and no tracking services. Error reporting stays off until you turn it on yourself. And when you do, recovery phrases and account numbers are stripped from the report before it's sent.
Transparency
A good lock is secure even when everyone knows how it works. Only the key has to stay secret. Cryptographers call this Kerckhoffs's principle, and Payky is built on it: anyone can read the code, but the key — your recovery phrase — is yours alone.
A typical cloud app
Secure. Trust us.
You can't see inside, so all you can do is trust.
Payky
You can see how the lock works, and you still can't open it. Only you have the key.
The whole app is on GitHub under the MIT license. Anyone can look through it — you, your IT person, even your competitors.
Source code on GitHubHow the app should behave is written down right in the repository. Each rule says which test guards it, or why it has none. If the code breaks a rule, a test fails.
The PIN won't stop an attacker, relays see metadata, and Spark network operators see amounts. We say it openly, because security that keeps quiet about its weak spots isn't security — it's advertising.
We can't yet prove that the app on payky.me or on your phone was built from exactly the code on GitHub — that would take so-called reproducible builds, which we don't have. But you don't have to take our word for it: you can build the app yourself from the code on GitHub and run your own copy.
The full list
Every service Payky talks to: what it sends, when, and for our own servers, why. Sorted by when the connection happens.
Until you turn something on or use it, the app talks at most to the payky.me website and two relays — and it sends the relays only encrypted data.
None of these services ever gets hold of your money or readable data about your business. The only exception is what you yourself write to the AI assistant or to support.
Looking ahead
Neither selling nor payments depend on our servers. Here's what happens when they go down — and what would happen if Payky shut down.
| Feature | What happens |
|---|---|
| Selling, bills and cash | Keep working |
| QR payments, bitcoin and cards | Keep working |
| EET | Keeps working; sales go straight to the Financial Administration |
| Backup and sync | Keeps going through the Linky relay, if you have it on |
| Web version | Opens from the browser's storage if you've opened it before. The Android app keeps working. |
| AI assistant, support, contact form and donations | Don't work until the servers are back |
The app on your phone keeps working.
Through any available relay, even your own.
The bank account is yours, and you can open the bitcoin wallet with the recovery phrase in another app that supports Spark too.
Anyone can take it, change it and keep it running.
Source code on GitHubNo sign-up, done in a minute. Just open the app.
Try this: open the app, switch on airplane mode and ring up an espresso. The bill opens, the items add up and the cash goes through.