EST · MMXXVI
Home/Jurisdictions/Digital Asset Issuance and Trading in the AIFC
Licensing & Registration

Digital Asset Issuance and Trading in the AIFC

Digital Asset Issuance and Trading in the AIFC. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-fee engagements. Talk

An exchange expanding into Central Asia discovers that a simple registration in its home jurisdiction does not cover digital-asset trading in Kazakhstan. The operator needs authorisation under a regime that treats digital assets as a regulated activity – but applying in Almaty or Astana under the national framework means navigating a civil-law system with limited crypto-specific guidance. The alternative is the Astana International Financial Centre, where English common law applies and the Financial Services Regulatory Authority operates a dedicated framework for digital-asset trading facilities, custody and issuance. The legal question turns on the scope of activity the business intends to conduct and the regulatory perimeter that captures it.

Digital asset issuance and trading in the AIFC fall under the supervision of the Astana Financial Services Authority. The AIFC is a special economic zone within Kazakhstan that applies common-law principles, uses English as the language of business and law, and maintains a court system separate from the Kazakhstani judiciary. For a business issuing tokens or operating an exchange, the AIFC offers a regulatory environment built on familiar common-law concepts – market conduct, custody safeguards, client-asset segregation – in a jurisdiction that sits between Europe and Asia. This page sets out the regulated perimeter, the authorisation process, the cross-border reality and the practical considerations a digital-asset business faces when it considers the AIFC route.

The AIFC regulatory framework for digital assets

The Astana Financial Services Authority governs financial services inside the AIFC under a framework modelled on English regulatory principles. Digital assets are treated as a regulated activity category alongside securities, banking and fund management. The regime distinguishes between operating a digital asset trading facility (the platform that matches orders or arranges trades), providing custody services (holding or safeguarding client assets) and issuing tokens to the public. Each function may require a separate authorisation or may be combined in a single application where the applicant demonstrates it will conduct all three.

The AFSA applies substance tests to determine whether a token constitutes a security, an e-money instrument or a pure digital asset. The classification turns on the rights attached to the token – a promise of profit from the efforts of others, voting rights in a legal entity or a claim on the issuer's balance sheet all trigger heightened scrutiny and may bring the token inside the securities perimeter. A utility token that grants access to a service or a native blockchain token used for transaction fees generally falls outside the securities definition but remains within the digital-asset perimeter if it is marketed or traded in the AIFC. Where the line lies matters for capital requirements, disclosure obligations and the range of permissible activities under the licence.

In our cross-border practice we see operators drawn to the AIFC because the rulebooks are written in English, the legal system is predictable for counsel trained in common-law jurisdictions and the regime offers a path to serve clients across the Central Asian Economic Union and the wider region. The framework is not a registration tick-box; the AFSA expects detailed business plans, robust compliance systems and evidence that the applicant understands the risks inherent in digital-asset activity. Where an applicant imports a model that worked in a low-threshold jurisdiction elsewhere and assumes the AIFC will rubber-stamp it, the application stalls.

Who needs AIFC authorisation for digital-asset activities?

An entity needs AFSA authorisation if it conducts regulated financial services from inside the AIFC or markets those services to AIFC participants. Operating a trading platform that accepts orders from retail or institutional clients, holding client funds or tokens in custody and issuing tokens with an investment character all require prior authorisation. The territorial trigger is not physical presence alone; a platform operated from servers outside Kazakhstan that actively solicits AIFC-resident clients or markets itself as an AIFC-regulated exchange falls within scope.

A business model that splits functions across multiple jurisdictions – a Cayman holding company, a Dubai marketing arm and an AIFC trading facility – must ensure each piece holds the right licence in its own jurisdiction and that the cross-border flow of instructions, client assets and data complies with the relevant rulebooks. In practice this means coordinating VASP registration in the operating hub, custody authorisation where client assets sit and a marketing passport or exemption in the jurisdiction where clients are onboarded. An AIFC licence alone does not authorise activity in mainland Kazakhstan; for national reach the business applies separately to the National Bank or the relevant ministry under domestic law.

The common mistake is treating the AIFC as a pure offshore booking centre. The AFSA supervises on the basis that the licensed activity genuinely occurs in the AIFC – systems must be managed from Astana, compliance officers must be present or accessible on short notice and the substance test expects staff, decisions and technology to reside inside the zone. A shell structure with one employee and outsourced operations does not meet the test. Where substance is thin the regulator either refuses the application or imposes conditions that force the business to relocate real operations into the AIFC.

The application process and indicative timeline

The authorisation process begins with a pre-application consultation. The AFSA encourages applicants to submit a draft business plan and a summary of the proposed activities before filing the formal application. This consultation identifies gaps in the compliance framework, clarifies which activities fall inside the regulated perimeter and surfaces conflicts with existing AIFC rules early. Where the business model is novel – a decentralised exchange with an AIFC booking entity, a token that embeds derivative exposure or a custody model that relies on multi-signature wallets distributed across jurisdictions – the pre-application stage prevents a costly formal submission that the regulator cannot approve without structural changes.

The formal application includes a detailed business plan, financial projections for three years, a description of the technology stack, evidence of capital adequacy, policies and procedures for AML and client onboarding, and information on directors and controllers. The AFSA vets each director and significant shareholder; the vetting covers regulatory history, criminal records, bankruptcy filings and prior involvement in failed financial-services ventures. A director who left a previous regulated entity under adverse circumstances or who held a senior role in a business that collapsed with client losses will face detailed questions; in some cases the AFSA requires that individual to step back from the AIFC application.

The timeline from formal submission to authorisation varies with the complexity of the business model and the completeness of the application. A straightforward custody-only application from a team that has already obtained a similar licence in another common-law jurisdiction may progress in a matter of months. A multi-activity application covering issuance, trading and custody from a new team with no prior regulatory track record typically takes longer, as the AFSA works through each layer of the compliance framework and requests additional evidence of systems readiness. Where the applicant is slow to respond to queries or submits incomplete documentation, the timeline extends. A well-prepared application with experienced advisers and a team that has run similar businesses elsewhere shortens the process materially.

The process above describes the AFSA path. Your facts – the entity structure, the client base, the token characteristics – change the analysis. If a prior application stalled or an approach was declined elsewhere, a second read can surface the structural reason and the route forward. For a scoped assessment of the AIFC authorisation for your business model, contact OBOLUS at info@oboluslaw.com.

Capital requirements and ongoing compliance expectations

The AFSA sets minimum capital requirements that vary by the scope of regulated activity. A custody-only licence carries one capital floor; a trading facility another; a combined licence that includes issuance, trading and custody requires the applicant to meet the highest applicable threshold or a composite figure the regulator deems appropriate for the risk profile. The capital must be held in liquid form and available to meet client claims or operational losses; the regulator will not accept illiquid assets, related-party loans or token holdings issued by the applicant itself as qualifying capital.

Once authorised, the licensee files periodic returns that cover financial position, client-asset reconciliation, transaction volumes and material incidents. The AFSA expects monthly or quarterly reporting depending on the activity; a delay in filing or a material discrepancy between the reported client-asset balance and the actual holdings on-chain triggers supervisory scrutiny. In our practice we regularly advise operators on the reconciliation logic required to keep reported balances in line with blockchain state – where client assets move across multiple chains and wallets, the compliance officer must demonstrate a real-time view of holdings and an audit trail that links each on-chain address to a client account.

The ongoing compliance burden includes annual audits, cybersecurity assessments and AML reviews. The AFSA may conduct on-site inspections where it identifies concerns about systems adequacy or client-asset safeguarding. A licensee that experiences a security incident – a wallet compromise, a phishing attack or unauthorised access to client funds – must notify the regulator immediately and submit a root-cause report within a defined period. A failure to notify or an attempt to resolve the incident quietly without disclosure is grounds for enforcement, including suspension or revocation of the licence.

The cross-border reality: banking, tax and regional access

An AIFC licence does not solve the banking question. The licensed entity needs a bank account to receive client fiat deposits, pay operating expenses and settle transactions; obtaining that account requires a separate process with a bank willing to serve a digital-asset business. Some international banks operating in Kazakhstan or the AIFC offer accounts to licensed entities, but many impose transaction limits, require enhanced due diligence on every large transaction and reserve the right to close the account on short notice where they perceive regulatory or reputational risk.

Operators we advise routinely use a multi-banking model: one account for fiat settlement inside the AIFC, a second account in a major hub for correspondent banking and a third account in a jurisdiction with established crypto-banking infrastructure. This model spreads risk but creates complexity – each bank has its own AML expectations, transaction-monitoring system and definition of high-risk activity. A single large withdrawal flagged by one bank's automated system can freeze operations for days while the compliance team provides documentation. The strategy is to map the banking stack before applying for the licence and to maintain alternative accounts as a fallback.

Tax treatment inside the AIFC is governed by the zone's preferential regime. Corporate income tax is generally set at a concessionary rate for a defined period, and there is no value-added tax on services provided inside the zone. The tax advantage applies to income derived from AIFC activities; where the business also operates outside the zone or serves clients in mainland Kazakhstan, the ordinary Kazakhstani tax rules apply to that portion of the revenue. The interaction between AIFC tax treatment and the home jurisdiction of the ultimate shareholders requires careful structuring – a holding company resident in a jurisdiction with controlled-foreign-corporation rules may face immediate taxation on AIFC profits regardless of distribution.

The AIFC is used by businesses seeking access to the Central Asian market and to clients in neighbouring jurisdictions where no local digital-asset regime exists. A licensed AIFC entity can market its services across the region, provided it complies with each target jurisdiction's rules on cross-border financial services. Some countries permit AIFC-regulated firms to operate on a notification basis; others require local registration or impose restrictions on retail marketing. The expectation that an AIFC licence functions as a regional passport is overstated – in practice the operator conducts a jurisdiction-by-jurisdiction analysis and often limits cross-border marketing to institutional clients or high-net-worth individuals to avoid retail-conduct scrutiny.

Token issuance in the AIFC: disclosure and ongoing obligations

Issuing a token to the public from the AIFC requires the issuer to file a disclosure document with the AFSA if the token meets the definition of a security or falls within the regulated digital-asset perimeter. The disclosure document must describe the rights attached to the token, the use of proceeds, the risks to holders, the technical architecture of the underlying platform and the background of the issuer team. The AFSA reviews the document for completeness and accuracy but does not endorse the merits of the offering; the review is a gatekeeper function, not an investment recommendation.

Where the token constitutes a security under the AFSA's substance test, the issuer must comply with prospectus-equivalent requirements and ongoing reporting obligations similar to those applied to listed equity. The issuer files periodic updates on financial performance, material events and changes to the governance structure. Token holders acquire rights to information and, depending on the token design, may acquire voting rights or claims on the issuer's assets. The legal characterisation drives the regulatory treatment; a token marketed as a pure utility instrument but structured with profit-sharing or buyback rights will be reclassified as a security, bringing the full securities-law apparatus into play.

A stablecoin issuance requires additional scrutiny. The AFSA expects the issuer to demonstrate that reserves backing the stablecoin are held in segregated accounts, are audited regularly and are sufficient to meet redemption requests at all times. The reserve composition – fiat currency, government bonds, money-market instruments – must be disclosed, and the issuer must publish regular attestations from an independent auditor. Where the reserves include digital assets, those assets must themselves be held in custody by a regulated entity and valued using a transparent methodology. An issuer that fails to maintain the peg or that diverts reserves to other purposes faces enforcement, including orders to cease issuance and potential criminal referral where fraud is suspected.

Common mistakes and how to avoid them

The most common mistake is applying for the wrong licence category. An operator that intends to custody client assets but applies only for a trading-facility licence finds itself unable to hold client tokens legally once authorised. The correct approach is to list every function the business will perform – order matching, custody, settlement, staking, lending – and to apply for authorisation that covers all of them. Where the business model will evolve over time, the application should state the intended future activities and seek a phased authorisation that allows the operator to add functions without a full re-application.

A second mistake is underestimating the substance requirement. The AFSA will not authorise a business that exists only on paper. The applicant must demonstrate that key personnel will be based in the AIFC, that technology systems are managed from within the zone and that compliance decisions are made locally. A business that attempts to run AIFC operations remotely from another jurisdiction with only a nominee resident director will not pass the substance test. Where genuine substance is not feasible, the operator should consider whether the AIFC is the right jurisdiction or whether an alternative regulatory route – registration in the operating hub, passporting under a reciprocal regime – better fits the business reality.

A third mistake is ignoring the cross-border AML obligations. The AIFC applies the FATF standards, including the Travel Rule. A licensed entity that facilitates transfers above the applicable threshold must collect and pass originator and beneficiary information with each transaction. Where the business serves clients in multiple jurisdictions, it must comply with the stricter of the AIFC requirement or the client's home-jurisdiction requirement. A failure to implement Travel Rule compliance before going live results in supervisory action; the regulator will impose conditions, suspend onboarding or, in serious cases, revoke the licence.

If a prior application stalled or an account was closed, a second read can surface the structural reason and the route back. For a scoped assessment of the AIFC route for your business model, including the interaction with your operating and banking jurisdictions, write to OBOLUS at info@oboluslaw.com.

How the AIFC compares for an inbound operator

The AIFC sits between the European licensing regimes – MiCA, Lithuania, Malta – and the Gulf hubs of Dubai and Abu Dhabi. It offers a common-law framework without the capital intensity of a full MiCA authorisation and without the market-access constraints of a single-emirate licence. For a business seeking regional positioning in Central Asia or access to clients in Russia, the former Soviet republics and parts of the Middle East, the AIFC provides a regulatory flag that carries credibility and a legal system that sophisticated counterparties recognise.

Compared to Dubai's VARA regime, the AIFC framework is less prescriptive on technology requirements but expects a higher level of English-law drafting in policies and procedures. Compared to Lithuania under MiCA, the AIFC authorisation does not include a European passport, so cross-border access to EU clients requires separate registration or reliance on a reverse-solicitation exemption. Compared to Singapore, the AIFC capital requirements are generally lower and the application timeline shorter, but Singapore offers deeper banking infrastructure and a larger pool of institutional clients.

The decision matrix for an operator considering the AIFC turns on client geography, banking feasibility and the team's ability to establish real substance in Astana. A business primarily serving European clients is better off applying under MiCA or in a member state with an established crypto-banking sector. A business targeting Central Asia, the Caucasus and the wider CIS region, with a team prepared to relocate key personnel to Kazakhstan, should prioritise the AIFC. A business that requires immediate access to deep liquidity and established banking rails should consider Singapore or Hong Kong first, with the AIFC as a secondary licence for regional expansion.

Related at OBOLUS

FAQ

How long does a crypto licence take to obtain?

The timeline from formal application to authorisation in the AIFC varies with the complexity of the business model and the completeness of the submission. A straightforward custody application from an experienced team may progress in a matter of months. A multi-activity application covering issuance, trading and custody typically takes longer, as the AFSA works through each layer of the compliance framework. Pre-application consultation shortens the formal process by identifying gaps early. A well-prepared submission with experienced advisers materially reduces the timeline.

Which jurisdiction suits my crypto business?

The right jurisdiction depends on your client geography, your banking needs and your team's ability to establish substance. A business serving European clients should prioritise MiCA authorisation or a member state with established crypto banking. A business targeting Central Asia and the CIS region with personnel prepared to relocate to Kazakhstan should consider the AIFC. A business requiring deep liquidity and banking infrastructure should evaluate Singapore or Hong Kong first. The decision turns on a multi-factor analysis, not on a single ranking of jurisdictions.

Do I need a separate custody licence?

Custody is a separately regulated activity under the AFSA framework. If your business will hold or safeguard client digital assets, you need custody authorisation in addition to or as part of your trading-facility licence. The AFSA permits combined applications that cover multiple activities; the applicant must demonstrate adequate capital, systems and compliance controls for each function. A trading platform that attempts to custody client assets without the right authorisation exposes itself to enforcement and to claims from clients if assets are lost or misappropriated.

About OBOLUS

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, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. We map the licence stack across operating, custody and payment layers before you commit, and we coordinate freezing relief and on-chain tracing across leading common-law forums when recovery is needed. To discuss your AIFC authorisation or to compare the AIFC route against other hubs for your business model, contact info@oboluslaw.com.

By Aisha Tan, Licensing & Jurisdictions Analyst – specialising in digital-asset authorisation processes across common-law and civil-law regimes, with a focus on Central Asian and Gulf jurisdictions.

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