EST · MMXXVI
Home/Jurisdictions/Kazakhstan Aifc/Vara licence application in Kazakhstan (AIFC)
Licensing & Registration

Vara licence application in Kazakhstan (AIFC)

Vara licence application in Kazakhstan (AIFC). Cross-border digital-asset legal counsel for business – licensing, disputes and structuring. Talk to OBOLUS.

Operating a digital-asset business without proper regulatory authorisation in Kazakhstan's Astana International Financial Centre is not a planning oversight – it is an enforcement exposure. Businesses that approach the AIFC (Astana International Financial Centre) and its regulator, the Astana Financial Services Authority (AFSA), without a clear application strategy routinely face delayed launches, frozen correspondent banking and, in the worst cases, prohibition from the jurisdiction entirely. The question for any inbound operator is precise: which AFSA activity authorisation do you need, what does the application require, and how does that regime interact with your global structure?

Kazakhstan's AIFC offers regulatory authorisation for digital-asset businesses under a common-law regime that operates independently of the broader Kazakhstani legal system. AFSA supervises digital-asset trading facilities, custody, exchange and related services within the AIFC perimeter. The regime is broadly comparable to other Gulf-adjacent financial-centre models, but it carries its own activity taxonomy, rulebook and cross-border implications that distinguish it from both the UAE's VARA regime and the EU's MiCA architecture. This page maps the application process, the cross-border interaction and the decision points an operator must resolve before filing.

What Is the AIFC/AFSA Digital-Asset Regime?

The AIFC operates as a standalone financial free zone within Kazakhstan, governed by its own legal framework modelled on English common law and administered by AFSA. Digital-asset service providers seeking to operate within the AIFC must obtain a specific regulatory authorisation from AFSA before commencing regulated activities. This is not a light-touch registration – it is a full authorisation process that requires the applicant to demonstrate fitness, governance, financial soundness and operational competence.

The AIFC's digital-asset regime covers a defined set of activities. These include operating a digital-asset trading facility (a platform where buyers and sellers transact in digital assets), providing digital-asset custody, carrying on digital-asset exchange services, and related advisory and management functions. Each activity category sits under its own set of AFSA rules and, depending on the combination of services, an operator may need authorisation for more than one activity. The critical point at the outset is that the AIFC perimeter is drawn narrowly: the authorisation covers activity conducted within or from the AIFC, not Kazakhstan at large.

In our licensing practice, we have seen operators assume that an AIFC authorisation functions as a pan-Central-Asian licence. It does not. Activity directed at the wider Kazakhstani market – outside the AIFC free zone – falls under a different regulatory and legal environment entirely. Clarifying that boundary before you structure the entity is the first substantive task.

Who Needs an AFSA Digital-Asset Authorisation?

Any entity that carries on regulated digital-asset activities within or from the AIFC must hold the relevant AFSA authorisation, regardless of where its beneficial owners are domiciled or where its servers are located. The AFSA regulated-activity perimeter is activity-based rather than entity-based: the trigger is what the business does, not what it calls itself.

The profiles we advise most frequently in this jurisdiction fall into three categories. First, exchanges and trading platforms seeking a credible common-law jurisdiction for institutional counterparties in Central Asia and the broader CIS region. Second, custodians and wallet infrastructure providers that need a regulated wrapper for their services. Third, fund managers and investment vehicles with digital-asset strategies that require a regulated AIFC presence to access the AIFC's investor community and banking ecosystem.

A business operating purely as a technology vendor – providing software to a licensed AFSA entity rather than itself conducting regulated activities – may fall outside the authorisation perimeter. However, that distinction turns on the substance of what the vendor controls. If the vendor exercises discretion over client assets, order routing or custody decisions, AFSA is likely to treat the substance as a regulated activity. We regularly advise vendors on that boundary precisely because the consequences of misclassifying it are material.

How Does the AFSA Application Process Work?

The AFSA application process for digital-asset authorisation follows a structured sequence of pre-application engagement, formal submission and review. The process is not a box-filling exercise. AFSA expects substantive engagement on business model, governance, risk management and AML/CFT controls before it will advance a file.

The typical sequence runs as follows. The applicant first seeks a pre-application meeting with AFSA to present the business model and receive early feedback on the appropriate activity category and likely conditions. This step is practically important: operators who skip it and file directly tend to receive material information requests that add months to the process. Following that meeting, the applicant prepares and submits a formal application pack, which includes a detailed business plan, financial projections, a governance and ownership structure, AML/CFT policies aligned with FATF Recommendation 15 (the FATF standard addressing virtual-asset service providers), technology and security documentation, and key personnel profiles demonstrating fitness and propriety.

AFSA then conducts its review, which typically involves multiple rounds of supplementary questions and, in some cases, meetings with proposed key function holders. The timeline from formal submission to authorisation varies by complexity and application quality; operators should plan for a process measured in months rather than weeks. Applications that arrive with incomplete governance documentation or underspecified AML frameworks consistently take longer. In our experience, a well-prepared submission substantially reduces the cycle.

Once authorisation is granted, the entity must satisfy any conditions precedent before it can commence operations. These typically include proof of capital in the prescribed form, final technology sign-off and notification of key staff appointments. The authorisation is then subject to ongoing supervision obligations, including periodic reporting, compliance certification and AFSA inspections.

To map the specific activity categories and documentation requirements against your business model, contact OBOLUS at info@oboluslaw.com. The process above describes the standard path. Your facts – the entity structure, the user base, the banking arrangements – change the analysis at each step.

What Are the AML and Travel Rule Obligations Under AFSA?

AFSA-authorised digital-asset businesses must operate a full AML/CFT programme consistent with FATF standards, including the Travel Rule – the obligation, arising from FATF Recommendation 16 as applied to virtual assets, to pass originator and beneficiary data alongside a virtual-asset transfer. Compliance with the Travel Rule is not optional and is a live supervisory expectation at AFSA.

The AML/CFT obligations in the AIFC sit within a common-law regulatory architecture. AFSA has issued dedicated AML rules for digital-asset firms, and the standards applied are materially equivalent to those in Singapore, Hong Kong and the UAE. In practice this means that an operator entering the AIFC from one of those jurisdictions will find the compliance framework familiar in structure, even if certain procedural specifics differ.

The Travel Rule threshold – the transfer value at or above which originator and beneficiary data must travel with the transaction – varies and should be confirmed against the current AFSA rules at the time of application. Do not rely on thresholds from other jurisdictions: AFSA sets its own de-minimis. Operators we advise at this stage are typically already deploying Travel Rule solutions for their EU or Singapore businesses; the AIFC implementation is then a configuration and counterparty-identification exercise rather than a from-scratch build.

Customer due diligence, beneficial ownership verification, sanctions screening and suspicious-transaction reporting obligations apply on the same basis as in other FATF-compliant jurisdictions. AFSA expects the compliance function to be resourced in proportion to the business volume and complexity – a sole compliance officer managing a high-volume trading facility will attract supervisory scrutiny.

How Does the AIFC Interact with Cross-Border Licensing and Tax?

For an operator with an existing regulatory footprint – say, an EU MiCA CASP authorisation or a Singapore MAS DPT licence – the AIFC adds a Central Asian regulated hub rather than replacing the existing structure. The cross-border interaction is primarily structural: where the entity sits, where the revenue books and where the tax falls.

The AIFC is a financial free zone with its own tax regime. Entities incorporated in the AIFC benefit from a defined set of tax exemptions under Kazakhstani law, including exemptions from income tax and VAT on qualifying financial services for a period set by the AIFC founding instruments. The precise scope and duration of those exemptions should be verified against current AIFC documentation and your specific revenue mix. We do not state them as fixed figures here because the applicable terms can change and the exact treatment of digital-asset income warrants specialist analysis.

Banking is a material consideration. The AIFC has a developing banking ecosystem, and operators should expect to work with a limited set of banking partners relative to, say, Singapore or the UAE. Correspondent banking for digital-asset businesses globally remains constrained; the AIFC is no exception, and a realistic banking plan – ideally with a primary and a fallback institution – should be part of the pre-launch structure. We have seen operators obtain their AFSA authorisation and then spend additional months resolving the banking layer. Addressing both in parallel materially reduces that risk.

From a corporate structuring perspective, the AIFC entity is typically a holding company or an operating subsidiary within a wider group. The holding layer – often a BVI, Cayman or ADGM vehicle – interacts with the AIFC entity on the basis of a service agreement or a group-wide licensing arrangement. The transfer-pricing and substance implications of that structure require analysis under both AIFC tax rules and the law of the holding jurisdiction.

How Does AFSA Compare to VARA, MiCA and MAS for an Inbound Operator?

The AIFC/AFSA regime occupies a distinct position in the global licensing environment. It is neither as prescriptively activity-specific as VARA in Dubai, nor as passportable as a MiCA CASP authorisation from an EU member state, nor as institutionally deep as MAS licensing in Singapore. Its competitive advantage is geographic and structural: it provides a common-law regulated hub that is credible for institutional counterparties in Central Asia, Russia-adjacent markets and parts of the Middle East where the UAE presents political or business sensitivities.

Under MiCA, a CASP authorised in one EU member state can passport services across the entire EU and EEA – a structural advantage the AIFC cannot replicate. Under VARA, the activity-based rulebooks in Dubai are more granular and the supervisory engagement is intensive, but the brand carries significant institutional weight in the Gulf. MAS licensing under the Payment Services Act offers deep banking infrastructure and the reputational premium of Singapore, but at the cost of heightened compliance expectations and a scrutiny level that can extend the application timeline.

For the inbound operator, the AIFC is most compelling in two specific profiles. The first is an exchange or custodian that has a genuine commercial need to serve the Central Asian institutional market and wants a common-law jurisdiction for dispute resolution and counterparty comfort. The second is a group that already holds a Gulf or EU licence and is adding the AIFC as a strategic market licence rather than a primary hub. In neither case is the AIFC a substitute for a licence in the jurisdiction where the business's primary user base sits.

If you have already mapped a primary licensing hub and need to assess whether the AIFC fits as a second or third leg of the structure, write to OBOLUS at info@oboluslaw.com. If a prior application in another jurisdiction stalled or a banking relationship closed, a structural review can surface the reason and the route forward.

A Jurisdiction Decision Matrix for Digital-Asset Operators

The right licensing profile depends on operator type, geographic focus and the nature of the service being offered. The following decision branches reflect the profiles we encounter most frequently in this jurisdiction.

An exchange or trading platform primarily targeting Central Asian institutional clients should treat AIFC/AFSA as the primary hub, with a parallel assessment of whether a second licence in Singapore or the UAE is needed to service offshore counterparties. The timeline for AFSA authorisation, combined with the banking setup, suggests a build-out period measured in several months to roughly a year, depending on application quality and the completeness of the governance documentation at filing.

A custodian serving a global fund manager with a Kazakhstan-facing mandate will likely need both the AIFC custody authorisation and a primary custodian licence in a deeper jurisdiction – Singapore or the EU – for the broader fund structure. The AIFC authorisation handles the local regulatory requirement; the primary licence handles the fund's home jurisdiction obligations. The key risk at this profile is that the custody standards in both jurisdictions are reconciled at the technical level before launch.

A token issuer seeking to use the AIFC as the primary issuance jurisdiction faces a more complex analysis. Token classification under AFSA rules – which draws on principles broadly analogous to those used by MAS and FINMA – turns on the rights the token confers rather than the label applied by the issuer. An asset-referenced token, a utility token and an equity-like token carry materially different regulatory consequences. Getting the classification wrong at the design stage is a structural defect that is expensive to remedy post-issuance.

A fund manager already authorised in the Cayman Islands or BVI looking to add an AIFC presence for a digital-asset strategy should focus on the AFSA investment management or fund management authorisation. The key interaction risk is between the AIFC's substance expectations and the holding structure in the offshore vehicle. AFSA expects the AIFC entity to have real operational substance, not merely a registered address.

Micro-Matter: Exchange Operator Securing AIFC Authorisation

In a recent matter, a digital-asset exchange operator with an existing EU regulatory footprint engaged OBOLUS to manage the AIFC/AFSA authorisation process for a Central Asian expansion. The operator had initially attempted to use a local Kazakhstani entity outside the AIFC perimeter and had encountered enforcement correspondence that threatened its correspondent banking. We advised on the structural repositioning into the AIFC free zone, prepared the full application pack – including governance documentation, AML/CFT policies aligned with FATF Recommendation 15 and key personnel profiles – and managed the pre-application engagement with AFSA directly. Authorisation was granted within the standard supervisory cycle, and the operator launched without further enforcement risk. The banking relationship was secured in parallel through allied counsel in the relevant jurisdiction. The matter closed in the second quarter of last year.

Common Assumptions That Create Risk

A common assumption among operators entering the AIFC is that a single offshore authorisation – an existing BVI registration or a Cayman fund structure – is sufficient to serve clients in Central Asia without a local AFSA licence. That assumption is incorrect and, in our cross-border practice, is the most frequent structural error we are asked to remediate.

The AFSA authorisation requirement is triggered by the activity conducted within or from the AIFC, not by where the operator's holding company is registered. A BVI-incorporated entity actively soliciting clients within the AIFC perimeter, or holding itself out as an AIFC market participant, is conducting regulated activity within the AFSA perimeter without authorisation. The consequences range from supervisory prohibition to enforcement action that affects the operator's banking relationships across multiple jurisdictions.

The second common assumption is that the AIFC is a low-scrutiny regime relative to the Gulf or EU. AFSA has materially increased its supervisory intensity over recent years. Application quality expectations, governance documentation requirements and post-authorisation compliance obligations are now broadly comparable to those in Singapore and the UAE. Operators who approach the AIFC with a light-touch mentality and underspecified compliance documentation consistently experience delays and condition-heavy authorisations.

Third, operators sometimes assume that the AIFC tax exemption is comprehensive and permanent. It is neither. The exemption applies to qualifying income categories for a defined period and is subject to conditions. A digital-asset business with a complex revenue mix – trading, custody fees, staking income, DeFi yield – requires a specific tax analysis against the current AIFC exemption schedule, not a blanket assumption of zero tax.

Related at OBOLUS

FAQ

How long does a crypto licence take to obtain?

The timeline depends on jurisdiction, licence category and application quality. In the AIFC, a well-prepared AFSA application typically progresses over a period measured in several months. Complex applications with multi-activity scope or incomplete governance documentation take longer. Jurisdictions such as Lithuania and the BVI have historically offered faster pathways, though MiCA alignment is extending EU timelines. In every case, pre-application engagement with the regulator is the single most effective way to compress the cycle.

Which jurisdiction is best for licensing my crypto business?

There is no universal answer. The right jurisdiction depends on where your users are, what activities you are conducting, which banking infrastructure you need and what your institutional counterparties require. The AIFC is compelling for Central Asian market access under a common-law framework. Singapore, the UAE and the EU each offer different strengths on banking depth, passporting and brand. Most institutional operators end up with a two- or three-jurisdiction licence stack rather than a single licence. We map that stack before you commit.

Do I need a separate custody licence?

In most major jurisdictions, custody of client digital assets is a separately regulated activity that requires its own authorisation or a specific extension of an existing licence. Under the AFSA regime, digital-asset custody is a defined regulated activity. An exchange operator that holds client assets – even temporarily – is almost certainly conducting custody and must ensure its authorisation covers that activity. Operators who assume their trading or exchange authorisation automatically covers custody are routinely caught by this gap at the supervision stage.

OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions – including the AIFC, VARA, MiCA and MAS regimes – on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. We map the licence, banking and tax stack across operating, custody and payment layers before you commit. Our disputes team coordinates freezing relief and on-chain tracing across leading common-law forums. Digital assets are the whole of our practice. To discuss your situation, contact info@oboluslaw.com or email us at info@oboluslaw.com.

By Aisha Tan, Licensing and Jurisdictions Analyst – specialist in AFSA, VARA and MAS regulatory authorisation processes for inbound digital-asset operators.

This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.

Discuss your matter with OBOLUS

Tell us about the business, the jurisdictions in scope and the deadline. Every brief is confidential and we reply within two hours.

Or email info@oboluslaw.com. We treat your brief as confidential.

Tell us the task — we'll map your options in 30 minutes.

Fixed-fee packages with defined scope and SLAs. The first call is free and under NDA. Business clients only.

Map your optionsinfo@oboluslaw.com · reply < 2 hours