Kazakhstan Crypto Regulation: Court Restricts Six Platforms
Kazakhstan’s court has restricted six unlicensed crypto platforms and app-store access. See what the ruling means for users, exchanges and local crypto rules.

Kazakhstan's Court Takes Aim at Unlicensed Crypto Platforms
Kazakhstan is moving to restrict access to six crypto platforms that its financial regulator says were offering digital-asset services without authorization. The Astana International Financial Centre (AIFC) court order doesn't stop with the platforms themselves - it also targets Apple and Google as app-store operators.
The platforms named in the order are Coinbase, BingX, Bitcoin.com, HTX, BitMart and WEEX. LBank was initially included, but it was later removed after its operator blocked access in Kazakhstan. Meanwhile, nine other platforms voluntarily restricted app access in the country, and the regulator withdrew its claims against them.
This case is a good example of how crypto regulation plays out across borders. A site can be reachable online without having the local permission regulators say it needs. And even when a court order limits access, that doesn't automatically tell you what happened - if anything - to existing customer accounts or assets.
What did the Kazakhstan court order?
The AIFC court issued injunctions after the Astana Financial Services Authority (AFSA) filed claims against operators it said were offering digital-asset services without authorization. The order is dated September 15, and three days later an amendment removed LBank after its operator blocked access in Kazakhstan.
The six platforms covered by the injunctions are:
- BingX
- Bitcoin.com
- Huobi Global, now known as HTX
- BitMart
- Coinbase
- WEEX
Apple and Google are also covered, but in their role as app-store operators. AFSA said the order requires geographic restrictions on access to the remaining platforms. In practice, that means enforcement isn't limited to blocking a website - it extends to the app distribution layer that helps users reach the service.
Why LBank was removed
LBank was named in the original order, but the court amended it after the operator blocked access in Kazakhstan. That matters because it suggests the enforcement wasn't handled the same way for every company. AFSA pursued injunction-based restrictions for the remaining platforms, while a change in access by LBank was enough to remove it from the order.
AFSA also said nine other crypto platforms took a different route: they restricted app access voluntarily. The regulator withdrew its claims against those nine. AFSA further said seven platforms indicated they intended to apply for licenses. The available information doesn't identify those seven, and it doesn't say whether any applications were approved - so "intending to apply" shouldn't be treated as proof of authorization.
What the order does - and does not - establish
Based on the reporting, the case concerns platforms AFSA says offered services without the permission it requires. What it does not establish is that every product offered by each company was independently assessed in a way that reaches all users, or that customers have been found to have broken the law.
It also doesn't explain how things like existing balances, pending withdrawals, or customer support requests will be handled. Those are the practical questions people naturally worry about, but answering them depends on company-specific details.
The most conservative takeaway is narrower: the court ordered access restrictions on specified services, and AFSA says the platforms lacked authorization in the jurisdiction relevant to that activity.
For the court's decision and AFSA's statements, see Cointelegraph's report.
Why the case matters to Kazakhstan's crypto market
The central issue here is straightforward: being online doesn't automatically mean a crypto service is authorized everywhere users can reach it. Regulators may treat promotion or delivery of digital-asset services to local residents as an activity that requires local permission - even if the company operates from elsewhere.
AFSA said the platforms were advertising without authorization and providing digital-asset-related services in Kazakhstan without the required permission. AFSA CEO Evgeniya Bogdanova described the court decision as the result of enforcement targeting unlicensed platforms. AFSA also said it warned more than 20 platforms about AIFC rules in 2025.
Look at the sequence, though. AFSA presented this not as a one-off technical block, but as a process: warnings first, some voluntary restrictions from firms, licensing intentions from others, and then injunctions against the six platforms still covered by the order.
Kazakhstan has more than one regulatory lane
The reporting points to two different authorities. AFSA supervises companies operating under the AIFC framework, while Kazakhstan's National Bank oversees digital-asset service providers outside the AIFC. That distinction matters because "Kazakhstan's crypto rules" aren't necessarily run through a single regulator or one licensing path.
For a company, the real question isn't just whether it holds a license somewhere. It has to figure out which legal entity is providing the service, where the relevant activity is considered to occur, which regulator has jurisdiction, and what permissions apply to that specific product. An authorization in one country or zone doesn't automatically transfer to another.
For users, the reminder is similar: don't assume a familiar global brand tells you which legal entity actually holds your account or what protections apply to that entity. The brand can be global; the contract and regulator might not be.
The consumer-protection argument
AFSA argued that users of unlicensed platforms may miss out on safeguards it expects from licensed firms. It specifically mentioned asset protection, disclosures, complaints handling, and dispute resolution. Those aren't abstract boxes on a compliance checklist - they affect what information users get, how complaints can be escalated, and what recourse exists if something goes wrong.
A license doesn't eliminate market risk or guarantee returns, and it doesn't magically make any crypto asset "safe." What it can do is create enforceable obligations and oversight that may be absent - or at least different - when a provider operates outside the relevant authorization framework. The comparison isn't "regulated equals safe" versus "unregulated equals unsafe." It's about accountability under rules that actually apply to the service, and whether users can identify what remedies exist.
Kazakhstan has used access restrictions before. Cointelegraph previously reported that the Financial Monitoring Agency blocked access in 2023 to nearly 1,000 crypto exchanges serving citizens without proper registration. This new case appears to fit into that broader pattern of restricting access to services authorities consider unauthorized.
What the restrictions mean for users and platforms
For people in Kazakhstan, the immediate impact is probably access - whether a platform can be downloaded through an app store and whether geographic restrictions prevent logins from inside the country. The order's inclusion of Apple and Google makes distribution part of the enforcement picture. Still, it doesn't answer every question about existing accounts or services accessed through other channels.
If you use one of the named platforms, it helps to separate issues instead of assuming one announcement settles everything:
- Access: Can you download the app or log in from Kazakhstan through permitted channels?
- Account status: Did the provider send any notice about your account or location?
- Assets and transactions: What does the provider say about balances, withdrawals, and any open transactions?
- Support and recourse: Which legal entity holds the account, and what dispute/complaint process applies?
- Local rules: What guidance has the relevant Kazakhstan authority published for residents and customers?
The safest move is to rely on official communications from the platform and the regulator. Don't treat social posts or third-party claims as confirmation that withdrawals will work or that a workaround is allowed. The order, as reported, doesn't provide account-by-account guidance.
A restriction is not a substitute for account planning
This case is also a reminder to understand custody and access before you're locked out. If a service controls private keys or holds assets on a customer's behalf, then your ability to transact depends partly on the provider's systems and policies. If assets are held in a self-custody wallet, access can depend on your own key management - but that doesn't remove legal, technical, or market risk.
Neither setup is automatically better for every scenario. Custodial services can be easier to use and may offer support, but they also create dependence on the platform. Self-custody gives you direct control over keys, but it also puts the burden on you for backups and transaction security. And if a jurisdiction blocks access, it can disrupt your ability to reach a service without changing those underlying trade-offs.
Avoid panic decisions based on an assumption that funds are frozen unless the platform or regulator says so. At the same time, don't assume "normal access" will necessarily continue. Keep records of account activity and official messages, and get qualified local advice for legal or tax questions if you're unsure.
Why app stores matter
App-store restrictions are operationally important because mobile apps are a major entry point for many customers. If access is blocked, users may not be able to download the app in the region, and discoverability drops. It can also make updates and support harder, depending on how the service is configured.
But an app-store restriction isn't automatically the same thing as a full shutdown of a company or every service it offers. As reported, the order focuses on geographic access restrictions. The reporting doesn't spell out the exact technical implementation or how it affects existing installs. That difference is worth keeping in mind - don't stretch a legal access order into claims the reporting doesn't support.
What exchanges should learn from the case
For exchanges and other platforms, the takeaway is practical: market access is a compliance issue, not just a product-growth question. Being able to onboard a user technically doesn't mean the service is authorized to do so in that jurisdiction. If a company waits until after warnings or court action to decide how to handle a market, it leaves a basic business risk unresolved.
AFSA said it warned more than 20 platforms about AIFC rules in 2025. Nine then restricted app access voluntarily, and seven said they intended to seek licenses. The remaining six faced injunctions. That pattern suggests regulators may accept different compliance responses in different situations - but it doesn't prove that voluntary geoblocking is always enough, or that a stated intent to apply for a license keeps a service running without risk.
Build a market-by-market decision process
A workable compliance process should force clarity before a service launches in a new jurisdiction. For example, answer these four questions:
- What activity are we providing? Trading, custody, payments, staking, and other digital-asset services can be treated differently. Define the product precisely, rather than treating "crypto" as one undifferentiated thing.
- Which entity provides it? Map the customer relationship, the contracting entity, custody arrangements, and who supports the customer. The brand name alone isn't a compliance analysis.
- Which permissions apply? Identify the relevant regulator and the licensing route for the activity and location. Confirm whether an existing authorization covers the specific service and customer group.
- What happens if we are not authorized? Decide whether to pause onboarding, restrict access, apply for permission, or exit the market. Document how existing customers are handled and how the decision will be communicated.
This isn't about adding paperwork for its own sake. A clear decision helps avoid inconsistent geoblocking, confusing customer messaging, and internal scrambling about who owns the problem once enforcement begins. It also gives product, legal, support, and engineering teams a shared rule to operate from.
Treat geofencing as an operational control
Geographic restrictions can be part of a compliance response, and the voluntary actions in this case show that this is often an option. But a geofence only works if the policy and implementation match the real-world problem. Teams need to decide what signals determine user location, how exceptions work, how changes are tested, and how customer support explains outcomes.
There's a trade-off. Strict controls can reduce exposure to unauthorized activity, but they can also block legitimate users, create false positives, or make travel and account access harder. Loose controls might feel more convenient, but they may fail to meet regulatory expectations. The right setup depends on legal advice, product design, and the regulator's requirements - it can't be reduced to a universal "turn this setting on" approach.
The bigger point is that compliance has to connect to product execution. If legal defines a restriction but engineering doesn't implement it consistently, the policy doesn't do much. If engineering blocks access without a clear customer plan, you can end up with operational problems even when the technical control "works."
Conclusion
Kazakhstan's court ordered access restrictions against six crypto platforms that AFSA says operated without the required authorization, with app-store operators covered as well. The outcome reflects a wider enforcement approach: warnings, voluntary restrictions, and licensing discussions for some firms, plus injunctions for others.
For users, the key is to separate an access restriction from claims about individual accounts or any blanket prohibition on crypto. For exchanges, the message is operational: make sure your service is authorized in a market before you offer it, and build market-access controls into product and compliance planning.
If you use a platform affected by the order, check the provider's official guidance and the regulator's updates before acting. For companies, treat local licensing as a market-entry requirement - not something to deal with after the launch.