All notes
Fintech

Salary on any card: Uzbekistan's central bank launches a Funds Distribution Center — registries, digital signatures and engineering questions

Since 18 November, private-sector employees can receive pay on a card or e-wallet of their choice. How the system works, what is still unclear, and what payment-system developers should prepare for.

What happened

On 18 November the Central Bank of Uzbekistan (CBU) announced the launch of its Funds Distribution Center. According to the regulator's press release, employees can now receive salaries, bonuses and other payments on a bank card or e-wallet of their choice, regardless of which bank serves their employer.

The flow works like this (CBU, Gazeta.uz):

  1. The employee gives the chosen card or wallet details to the employer's accounting department. No separate registration with the Center is required.
  2. The employer compiles a single payment registry covering all employees and sends it to its servicing bank.
  3. The bank signs the registry with an electronic digital signature and submits it to the Distribution Center.
  4. The system validates the data and splits the payments by the banks employees selected.
  5. Receiving banks credit the funds to the cards or wallets.

The card or wallet must be registered in the employee's own name, and employees can later switch cards or update details. The Center runs inside the CBU's protected infrastructure over a closed banking network; recipients' card and identification data are checked against CBU databases, and registries with errors are returned for correction (press release).

The first stage covers private-sector organisations and their employees. Gazeta.uz reports that budget-funded organisations are planned for a second stage, with no timeline given. The CBU cites Presidential Resolution PQ–359 of 27 November 2025 as the legal basis. Some media have described the document as a decree; I rely on the regulator's official wording.

Context

Until now the practice was simple: a company signs a payroll agreement with one bank, and employees effectively have to open a card there. Spot.uz called this "salary slavery". Many people then moved the money to the card they actually use, every month.

The idea isn't new. As Gazeta.uz reported in November 2025, the fintech roadmap tasked the CBU with building a mechanism to choose the salary bank or wallet by December 2025, and with adding a bulk-payment function to state payment systems by June 2026. In July, Spot.uz reported that the "Taqsim" system had been scheduled to launch on 30 June but was delayed by technical complexity and because some commercial banks weren't ready to integrate. So the project went live several months behind plan.

It's part of a bigger picture. The same roadmap includes P2P transfers by phone number and a national payment switch (Gazeta.uz). The switch regulation was registered by the Ministry of Justice on 23 October and takes effect on 25 January 2027, with the CBU's subsidiary Axborotlashtirish bosh markazi LLC as operator (Spot.uz). The Distribution Center follows the same logic: the regulator is taking on the role of central router for interbank flows.

What it means

For users: the employee, not the employer, now decides where salary lands. There is less reason to open a card just for payroll and shuffle money between cards every month.

For businesses and banks: per the press release, one registry can pay staff at different banks, with no need for separate payroll agreements with each. For banks, a payroll contract no longer locks the customer in — they will have to keep them with better service. As Gazeta.uz notes, the regulator hasn't said which banks are connected, how many organisations already use the system, or whether banks may charge a fee for switching salary banks.

For engineers, the interesting part:

  • The registry is a batch API. One file holds many lines, each potentially routed to a different bank, so partial success is inevitable — say, three lines out of a hundred carry a bad card. The official text says erroneous registries are returned, but whether that means the whole registry or only the failed lines isn't clear yet. Payroll software should handle both.
  • Idempotency. Resubmitting a registry must never mean paying salary twice. You need a stable identifier per registry and per line (for example, company + period + employee) and duplicate detection.
  • A state machine. Each line moves through at least "created → signed by bank → accepted by Center → routed to bank → credited or rejected". Statuses should come back via callback or polling and be reconciled regularly against your internal ledger.
  • Digital signatures and key management. The bank signs, so its back office must keep signing keys in an HSM or equivalent and keep an audit log of who signed what and when.
  • Personal data. The registry contains card numbers and employee names. HR and accounting systems should stop storing PANs in clear text and adopt masking and tokenisation.
  • The "own name" check. The Center matches the cardholder against CBU data. Good against fraud, but name spelling differences (Latin vs Cyrillic, apostrophes, transliteration) may cause false rejections. Design clear error handling for that up front.

My take

I think this is one of the most practical payment reforms of recent years. It touches everyone who receives a salary and shifts bank competition from "who signed the contract with the employer" to "whose app and service are better". That's the right direction.

Two things give me pause, though. The first is transparency. The launch has been announced, but the list of connected banks, the technical specification and the fees are not public. Without an openly documented format and a sandbox for integrators and accounting-software vendors, adoption will be slow. The second is centralisation. The Distribution Center, the payment switch, fast payments — all of it is concentrating in the regulator's infrastructure. That helps standardisation, but it also raises single-point-of-failure risk. If the system goes down on payday, many companies are hit at once, so I'd like to see public information on SLAs and fallback procedures.

My advice to developers: if you build HR, accounting or bank back-office systems, start rethinking payroll now — not as "one bank, one file", but as "many banks, each line with its own status". When the official spec arrives, that will save you a major rewrite.

Sources: Central Bank of Uzbekistan, 18 Nov 2026; Gazeta.uz, 18 Nov 2026; Spot.uz, 2 Jul 2026; Gazeta.uz, 28 Nov 2025; Spot.uz, 29 Oct 2026. This is personal opinion, not investment advice.

// comments

Loading comments...

    // next step

    Let's build something together.

    Message me on Telegram
    aslbek@asldev: ~
    ❯