Key barriers: Complex language and opaque statuses
Barrier 1: Bureaucratic UX and fear of making a mistake
Most forms for paying taxes or obtaining certificates use complex abbreviations and multi-stage classifiers. A user trying to pay property tax faces dozens of incomprehensible fields (region codes, payment types), which causes a fear of sending money to the “wrong place” or the wrong tax office. Any mistake in government services is perceived much more painfully than a mistake when buying in an online store.
Product insight: The bank should act as a “translator” between the client and the state. Forms should be 90% pre-filled from the client’s profile (pulling in TIN, PINFL, registration addresses). Instead of the field “Internal Affairs Department Subdivision Code”, the interface should simply ask: “What district do you live in?”, and then map the answer to the required system code. Each complex field should be accompanied by a visual hint (for example, a picture of a vehicle registration certificate with a red oval highlighting the number to be entered).
Barrier 2: Lack of status tracking (Black Box)
When a client applies for a benefit or registers an individual entrepreneurship through a superapp, the application often goes “nowhere”. The application only displays the status “Accepted for processing”, without specifying deadlines or specific stages. This makes users nervous and causes them to call the bank’s call center, overloading the support service with questions that the bank cannot answer, as it is waiting for a response from government agencies.
Product insight: A transparent status tracker in the style of a pizzeria is needed: “Application sent”, “Being checked at the tax office”, “Approved. Document is being generated”. Even if the process takes several days, a detailed visualization of the progress bar reduces the client’s anxiety level to zero and creates a feeling of complete control over the situation.
Behavioral models: Responsible citizens and involuntary debtors
-
Responsible archivists: Carefully monitor the payment of all taxes and fees. For them, the ability to download official receipts with a blue stamp (digital signature) for presentation to government agencies in paper form is important. They actively use the “Document Folder” function, storing digital copies of passports and driver’s licenses of the whole family inside the bank.
-
Involuntary debtors: Forget about taxes or camera fines until they are blocked from traveling abroad or money is forcibly debited from their card. A preventive push service is critically important for them: “You have a new camera fine at the Amir Temur intersection. Pay today with a 50% discount”. The presence of such an instant payment button is their favorite feature.
How it looks in practice
A young father registers his child for kindergarten. Everything works out from the banking app: data is pulled from the profile, the fee is paid in two taps, the receipt is saved in “Documents”. The finale ruins the impression: after sending, the application hangs in the “Accepted for processing” status for a week, and every two days he opens the app to look at the same inscription.
His neighbor is a typical “involuntary debtor”: he learned about a camera fine from a bank push notification and paid it with a 50% discount without leaving his car. Now this is his main argument in favor of the superapp: “the bank monitors fines instead of me”. Proactivity works stronger than cashback here — the user stays not for bonuses, but for being relieved of the obligation to remember.
Why it matters
Government services increase switching costs. If a user has once linked their car, apartment, and TIN data in a superapp and pays all taxes in a couple of taps, the probability that they will switch to another bank because of a slightly more profitable cashback tends to zero. This is a powerful retention tool (Lock-in effect).
FAQ
Is it safe to store passport and car data in a banking app?
This is the main question of new users. Banks need to broadcast the reliability of data encryption at the interface level and use biometrics when entering the government services section.
Why do some fines not appear in the app immediately?
The problem is on the side of the synchronization speed of government agency databases (API). It is important for banks to honestly write in the interface: “Data updated 2 hours ago” to manage expectations.
Why pay for government services through a bank if there is a government portal?
The bank wins with the combination of “found out — paid — saved the receipt” in one window and data that is already in the profile. The government portal remains the source of services, but the payment and notification layer of banks is more convenient.
Original research source: How Uzbekistanis use government services in banking ecosystems