Wallet card and staff scanner
- Who identifies
- Staff scan the card
- Staff involved
- Yes
- POS integration
- Not needed
Connection scenarios
Loyalty fails at the counter, not in the database. These are the six identification methods the platform supports, ordered from most staff involvement to none at all.
They combine: one merchant can run a wallet card in store and receipt scanning for delivery orders.
Updated
Who does the identifying, how much the staff are involved, and whether the till has to change.
Four of the six in detail. The two remaining — the in-POS screen and the chat bot — follow the same shape with a different front end.
The baseline. Nothing is integrated, nothing is installed on the till, and a merchant can be live the same day. Joining takes about ten seconds at the counter.
Payment and loyalty on one device, in one gesture. In standalone mode the scanner installs as an APK on the smart terminal; in card-linked mode the terminal recognises the shopper from the card token.
Zero staff involvement, at the cost of one change to the receipt template. The POS prints a unique single-use QR code on every receipt.
Available where the state runs fiscalisation: Slovakia, Ukraine, Kazakhstan and Uzbekistan. No POS integration, no seller involvement, nothing installed at the counter.
Start from the constraint you cannot move: the queue, the till, or the hardware.
Print the QR code on the receipt, or use the fiscal receipt in the bot. Staff say nothing and do nothing.
Integrate with the POS so loyalty appears in the screen the cashier already uses, with no second login.
Use card-linked recognition or install the scanner as an APK. Nothing new appears at the counter.
Only if you want to. Four of the six identification methods need no POS integration at all: a wallet card with a staff scanner, a bank payment terminal, a QR code printed on the receipt, and a fiscal receipt scanned by the shopper.
Yes, in two modes. The scanner installs as an APK on a smart terminal, or the terminal recognises the shopper from the bank card token and offers to spend their balance in the same tap.
Yes. Fiscal receipt verification through the SmartKasa API is live in Ukraine, and three products from the family are listed in the SmartKasa integration catalogue.
No. The shopper scans a QR code, signs in with Apple ID or Google ID, and the card lands in their wallet. In markets where messengers dominate, the same card lives inside a chat bot instead.
Next step
Tell us what is already installed and we will name the shortest route to a working pilot.