● Lokus — a card-operations data platform for banks
The customer paid at Korzinka. The app showed IP OOO ANGLESEY FOOD
Lokus parses raw processing strings and returns a feed people can read: brand, logo, category and a point on the map. Humo and Uzcard from day one; any other source runs through the same engine.
We looked for the same Korzinka purchase in 29 apps in Uzbekistan. In 14 of them the history was unavailable; of the remaining 15, only one recognised the brand.
Before and after — on real strings
This is how payments arrive from the processor — and this is how Lokus returns them.
Why a bank needs this data
Understand real spending
Lokus separates purchases from transfers, withdrawals, top-ups and loan repayments — so spending analytics are not distorted.
Know the customer better
Operations reveal loans and deposits at other banks, instalment plans, spending categories, merchants and payment channels. This data can feed scoring and segmentation.
See behaviour over time
Accumulated history shows recurring payments, subscriptions, a geo profile, changes in habits and the share of the customer's spending that runs on your cards.
Understand demand across the whole customer base
Once hundreds of terminals and legal entities are resolved to real brands, the bank sees where and on what its customers spend — and can use that for analytics, CRM and partnerships.
Products
The recognition engine as a standalone API — and a platform for the whole bank.
You only need the strings parsed
In goes a string from processing; out come the merchant, category, action, class, direction, app and channel. REST, SaaS or inside the bank's perimeter.
You want the whole bank to use this data
It collects operations from Humo, Uzcard and clearing files, accumulates them into a single history, merges them across all of the customer's cards and serves every consumer from one place. The data no longer sits scattered across mobile banking, scoring, CRM and other systems, and the Humo and Uzcard history is bought once and then reused inside the bank.
One purchase, 29 apps in Uzbekistan. In 14 of them the operation history was unavailable. Of the remaining 15, one showed the shop name — and that is Korzinka, the country's largest chain: the restaurant in the same feed it did not recognise either.
We send the research on request — write to us on Telegram or, for a formal request, to m@tarifik.uz.
Parsing is the entry point. Beyond it — the Lokus platform.
Everything a bank needs to turn the transaction feed into a product rather than a log.
Repeat requests served from storage, not bought again
A history request for a single card costs the bank from 1,030 UZS, and the processor keeps that history for no more than 365 days. Lokus retains everything that has once passed through the gateway: repeat requests are served from storage instead of being purchased again, and history stops getting lost.
How much is that in money? We'll measure on your data Calculator
One place for the bank's transaction data
Lokus sits as a single gateway between the bank's systems and the processors. Responses are byte-for-byte identical to Humo and Uzcard: the contract for the consumer does not change, and in the typical case it is enough to switch the endpoint and the network settings. All consumers, limits, tokens and a full access log — on one screen.
30,000+ merchants in Uzbekistan
Brands, chains and legal entities with logos, categories, coordinates and a branch hierarchy. The dictionary is maintained and extended daily.
All of a customer's cards in one profile
Humo and Uzcard in a single feed: one customer profile, normalised data, a complete picture of spending.
Categories, income/expense, recurring payments
Ready-made PFM widgets: spending breakdown, recurring charges, filters by category and merchant.
Lokus API, mobile SDK, on-prem
Lokus API (REST) and an embeddable SDK for the bank's app. Deployed inside the bank's infrastructure — data never leaves the perimeter.
See your spending through the eyes of Lokus
The bot shows your own feed the way it should look: with brands, categories and monthly totals.
For banks and fintechs: send us your statement — we return it readable. Write to m@tarifik.uz or t.me/lokusuz.
Contact
Banks and fintechs — a pilot on your own data. Customers — the @pulchek_bot bot.