Recurring revenue
The share is paid for as long as the merchant runs the programme, not once at signature.
Software
Rules, accrual, expiry, referrals, wallet passes, anti-fraud and reporting already exist and already run in four markets. You add a distribution channel, not an engineering programme.
Popular POS systems are supported out of the box, and additional systems are integrated on request.
Updated
Four things that change for you, and what each one rests on.
A single integration covers accrual, redemption, balances and the customer profile across every identification method.
Loyalty stops being a line in the backlog that never reaches the top and becomes a line in the price list.
The same engine serves a single cafe and a chain with a coalition of brands beneath it.
Fiscal receipt verification through the SmartKasa API is running in Ukraine today.
In practice
Whatever the commercial track, the counter experience is the same: the shopper is recognised, the balance is offered, and one confirmation closes it.
The share is paid for as long as the merchant runs the programme, not once at signature.
The engine is maintained on our side, including anti-fraud and reporting.
What you own of the sales and support cycle is what sets the share.
Nothing. Rules, accrual, expiry, referrals, wallet passes, anti-fraud and reporting already exist and already run. A partner adds a distribution channel, not an engineering programme.
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.
Slovakia, Ukraine, Kazakhstan and Uzbekistan. All four have state fiscalisation, which makes the scenario where a shopper scans the fiscal QR on their receipt possible with no POS integration and no staff action.
Next step
Describe your volume and how much of the cycle you want to own, and we will come back with commercial terms.