Connecting Central Asia with UK and EU Finance

Before discussing how quickly money can move between Central Asia and the UK or EU, I would start with a more basic question: which payment routes can the customer actually use?

The answer depends on the country, the customer and the purpose of the payment. A service available to an individual sending money home may not support a company paying an overseas supplier. A technically possible transfer may sit outside a provider's permissions or a banking partner's risk appetite.

Understanding those differences should come before the product promise.

Start with the route available to the customer

Uzbekistan illustrates why this matters. Its currency law treats individuals and companies differently. A company paying for imported goods or services can do so without restriction, but through one regulated route: a bank transfer under currency control. An individual sending or receiving money falls under separate rules for non-trade transfers, and has several routes to choose from. Currency Regulation Law

That difference shapes the market. For individuals, providers compete on the route. For a business, the route is set, and the work is in making it run. Before quoting a delivery time to an importer paying a European supplier, I would want to know which banks will handle the payment and what documents they need, how currency conversion will work, how the supplier receives the funds and who will answer a query from the receiving bank.

The bank's own options are narrow too. Uzbek banks move foreign currency through nostro accounts held with correspondent banks. Much of the newer cross-border infrastructure is being built by EMIs, payment API providers and stablecoin providers. They are not banks, so they do not fit that arrangement. For the bank, and for the company that banks with it, the newest routes are often out of reach.

So a personal transfer service cannot simply be repackaged as a corporate payment solution. The routes open to an individual are not open to an importer.

Regulation is opening new possibilities

Uzbekistan's stable-token (stablecoin) framework, in force since April 2026, provides for controlled pilots involving international transfers and settlements, alongside blockchain-based payment systems. This creates room to test different ways of moving money. For businesses that have only one route today, this is the part worth watching. Participation remains subject to the special regime, and a project creating a blockchain-based payment system requires a payment-system operator licence. These are conditional permissions, rather than unrestricted access for every business. Stable-token framework

The distinction is important. An announcement may describe an opportunity that still requires an approved participant, suitable partners and a workable route into and out of the token. A business needs to understand what is operational today, what is being tested and what remains a future possibility.

The same assessment must be made separately in each Central Asian country. Kazakhstan, for example, brought in a national digital-asset law on 1 May 2026, while the AIFC keeps its own regime. Its approach cannot simply be applied to Uzbekistan or another neighbouring market. National Bank of Kazakhstan

Are financial institutions ready?

Regulatory sandboxes give institutions a way to test new services under supervision. I see their value in allowing regulators and providers to identify practical problems before a wider rollout.

But a change in regulation does not automatically update a bank's onboarding policy, transaction-monitoring systems, treasury arrangements or correspondent relationships. A local institution may be willing to support a new model while a partner in the UK or EU still needs to assess it.

I would test readiness across four areas.

First, can compliance explain the legal basis, eligible customers and permitted transactions clearly enough for the business to operate within them?

Second, can treasury fund the route, manage conversion and provide sufficient liquidity? Faster movement on one part of the journey is of limited use if the customer cannot convert or receive funds at the other end.

Third, can operations reconcile the payment and manage an exception? Someone must own a delayed transfer, an information request or a failed payout.

Finally, do the institutions on both sides accept the arrangement? Local approval alone cannot answer that question.

Build around what can be delivered

My approach would be to select a defined customer need and build a route that can be explained, funded and supported from beginning to end. Then expand when the evidence supports it.

Customers should know which service they are using, what restrictions apply and what happens when a payment needs attention. If a service is operating under a pilot, that should be clear too.

Before launching a new route, I would ask the team to demonstrate one complete payment journey, including an exception. Show who can use it, how the funds reach the supplier and who takes responsibility when something goes wrong. That is where I would judge whether we are ready.