Token issuers expanding into Central Asia frequently discover that the Astana International Financial Centre (AIFC) in Kazakhstan operates an English-language common-law regime that is structurally different from anything else in the region – and meaningfully different from the EU's MiCA framework that dominates conversation in Western markets. The AIFC's financial regulator, the Astana Financial Services Authority (AFSA), applies a substance-first classification test: the rights a token confers determine its regulatory status, not the label a project team places on a whitepaper. Getting that classification wrong at the design stage can convert a product launch into an unregistered securities offering – a problem that is far harder to unwind after the fact than before it.
This page sets out the regulated basis for token issuance and offerings inside the AIFC, the classification framework AFSA applies, the process an inbound business must work through, the cross-border interactions that typically complicate a Kazakhstan-rooted structure, and the decision point at which early legal engagement makes a measurable difference.
The AIFC, AFSA and the regulatory basis for token activity
The AIFC operates as an independent jurisdiction within Kazakhstan, governed by its own body of English-language law and overseen by the Astana Financial Services Authority (AFSA). The centre applies common-law principles drawn from English law, and its dispute-resolution body – the AIFC Court – sits outside the national judicial system. For digital-asset businesses, this matters: the legal environment is readable by common-law counsel and internationally recognisable to institutional counterparts.
AFSA's remit over digital assets rests on a dedicated framework for digital-asset trading facilities, custody of digital assets, and the issuance and offering of digital assets to investors within or from the AIFC. The regime distinguishes between activity that engages financial-services regulation and activity that does not. A project that issues tokens purely as access credentials to a functioning software product sits in a different position from one that issues tokens conferring investment rights, profit participation, or governance over treasury assets.
In our cross-border practice, we regularly advise issuers who assume the AIFC is simply a registration convenience. It is not. AFSA conducts substantive review of proposed token structures, and the classification determination it makes at the gateway stage constrains every downstream decision: marketing, eligible investors, secondary-market access, custody arrangements, and banking.
How does AFSA classify tokens for regulatory purposes?
AFSA's classification logic is substance-over-form: the rights a token confers at the moment of issuance – not the name chosen for it – determine which regulatory box it occupies. The primary distinction runs between an investment token (a digital asset representing rights in the nature of equity, debt, profit participation or similar financial interests) and a utility token (a digital asset conferring access to a specific product or service already operational or in near-term development, with no financial-return expectation as the primary driver).
A token that sits in the investment category engages the full securities-offering regime: authorisation, disclosure obligations, investor-eligibility rules, and post-issuance reporting. A utility token may fall outside that regime entirely – but the burden of demonstrating its utility character rests with the issuer, and AFSA applies a functional test rather than accepting a label.
Several design features push a token toward investment classification regardless of how a whitepaper describes it. Revenue-sharing mechanisms, buyback commitments, governance rights over capital allocation, and representations about secondary-market appreciation all raise the probability of an investment-token determination. A common assumption among issuers is that a utility label on a whitepaper settles the legal classification. It does not. We assess classification against the substance of rights, and experience shows that AFSA does the same.
There is a third category worth noting: exchange tokens (tokens used as a medium of exchange or unit of account, not linked to a single product ecosystem). These attract their own set of considerations under the AFSA framework, particularly where a project intends secondary-market trading on an AIFC-regulated digital-asset trading facility.
What does the offering process look like for an inbound business?
An inbound issuer seeking to make a token offering within or from the AIFC must engage AFSA before distribution begins. The process follows a defined sequence, though timelines are not stated as fixed periods in publicly available guidance and vary with the complexity of the structure presented.
The first step is a pre-application engagement with AFSA, at which the issuer presents the token's technical design, the rights it confers, the intended investor profile, and the proposed distribution mechanics. This is not a formality. AFSA uses the pre-application stage to identify classification issues early – and to signal whether a proposed structure requires material redesign before a formal application will be accepted.
Where AFSA determines that a token constitutes an investment token, the issuer must prepare a compliant disclosure document – equivalent in function to a prospectus or offering memorandum – that meets AFSA's content standards. The document must cover the issuer's governance structure, the rights attached to the token, the use of proceeds, material risk factors, and the mechanics of any secondary-market access. AFSA reviews and must approve the disclosure document before the offering commences.
The issuer also needs to determine whether it requires an AFSA licence for the activity it is conducting. An entity that issues investment tokens and also facilitates secondary trading is likely to require both an issuance authorisation and a separate digital-asset trading-facility licence, or it must engage an already-licensed platform to handle that function. Custody of investor tokens raises a further licensing question.
For utility-token offerings that fall outside the investment regime, the process is lighter – but it is not unregulated. Anti-money laundering obligations under the AFSA framework, aligned with FATF Recommendation 15 on virtual assets, apply regardless of token classification. The Travel Rule (the obligation to pass originator and beneficiary data with a transfer above the applicable threshold) engages wherever the issuer or its service providers are processing value transfers. Issuers often underestimate the compliance build required even for a utility offering.
CTA #1 — The classification and pre-application stages are where structure is set. Getting both right before AFSA's first review reduces the risk of mid-process redesign and delays that affect your launch window. Map your options with our team before you file.
How do cross-border tax and banking considerations interact with an AIFC token structure?
An AIFC-domiciled issuer does not operate in isolation. The cross-border dimensions of a token structure – where the issuer entity sits, where its treasury banks, where its investors are resident, and where secondary trading occurs – each carry their own regulatory and tax implications that the AIFC filing does not resolve.
On banking: AIFC entities can access Kazakhstani banking infrastructure, but international token issuers typically require USD or EUR accounts with institutions that have appetite for digital-asset counterparts. Banking access for crypto-adjacent businesses remains commercially constrained across most of Central Asia's correspondent-banking network. In our practice, we regularly see issuers who have secured their AIFC authorisation but have not mapped their banking stack – a sequencing error that delays treasury operations by weeks or months. A parallel process running the banking origination alongside the regulatory application is the more efficient approach.
On tax: Kazakhstan offers a favourable tax environment within the AIFC, including exemptions from income tax and VAT on qualifying activities for entities operating inside the centre. The specific conditions, eligibility periods, and interaction with the issuer's home-country tax obligations require jurisdiction-by-jurisdiction analysis; we describe them qualitatively here because the applicable rates and exemption periods are subject to legislative change and must be verified against current legislation before reliance. What is consistent is that an issuer structured outside Kazakhstan but offering into the AIFC may face a different tax analysis than an AIFC-domiciled entity – a distinction that affects where the issuer entity itself should be incorporated.
On investor jurisdiction: if a token is offered to EU residents, MiCA's whitepaper and marketing-communication requirements engage regardless of where the issuer is domiciled. The same logic applies to US-resident investors under SEC and CFTC frameworks, and to investors in Singapore under the Payment Services Act administered by MAS. An AIFC authorisation does not create a passport into those regimes. Issuers must map their investor base and restrict or separately authorise distribution into each regulated jurisdiction.
In a recent matter, a technology-sector issuer based between two jurisdictions sought to run a token distribution from the AIFC while also marketing to investors in EU member states. The interaction between the AFSA disclosure requirements and the MiCA whitepaper regime required a dual-track compliance build; we coordinated with allied counsel in the relevant EU jurisdiction to align the two documents, preserving the AIFC as the primary domicile while managing the EU marketing channel separately. The offering reached its target investor base without regulatory interruption.
What is the AML and Travel Rule posture inside the AIFC?
AFSA's anti-money laundering regime is built on FATF's international standards, including the FATF Recommendation 15 obligations that apply specifically to virtual assets and virtual asset service providers. Any entity operating as a VASP – broadly, any business providing digital-asset exchange, transfer, custody, or issuance services to third parties – within or from the AIFC must implement a full AML/CFT programme that covers customer due diligence, transaction monitoring, and suspicious-activity reporting.
The Travel Rule obligation – requiring the originator's VASP to transmit identifying information about the originator and beneficiary to the beneficiary's VASP for transfers above the applicable threshold – applies within the AIFC framework. The precise threshold is set by AFSA regulation and should be verified against current AFSA guidance; it is not reproduced here as a fixed figure because regulatory updates can affect it. In practice, the Travel Rule creates an interoperability requirement: an AIFC-licensed VASP must be able to send and receive Travel Rule data with counterpart institutions, which means integrating a compliant Travel Rule solution into the technical stack before operations commence.
Issuers sometimes treat AML/CFT as a post-launch compliance item. AFSA does not. The regulator's pre-application review assesses whether the proposed AML programme is adequate for the activity described. A deficient AML design is a gateway issue, not a remediation item.
How does the AIFC compare with other token-offering jurisdictions for an inbound operator?
For an issuer evaluating where to domicile a token offering, the AIFC offers a distinctive combination: English common-law legal infrastructure, a dedicated digital-asset regulatory regime administered by AFSA, and a favourable tax environment – all within a Central Asian jurisdiction that does not require the issuer to navigate a civil-law framework or a translating intermediary.
Against MiCA-member-state options such as Lithuania or Malta, the AIFC does not offer an EU passport. For issuers whose primary investor base is in the EU, that absence is significant: the AIFC authorisation must be supplemented by a MiCA-compliant structure if EU distribution is intended. Operators targeting the broader CIS region, the Middle East, or Asian markets outside Hong Kong and Singapore may find the AIFC's positioning more directly aligned with their investor geography.
Against VARA (Dubai) and the ADGM/FSRA regime in Abu Dhabi, the AIFC offers broadly comparable English-law infrastructure at a generally lower cost base. VARA's activity-based licence menu is more granular; AFSA's framework is somewhat more consolidated. Neither is objectively superior: the right answer turns on the issuer's specific activity profile, investor base, and banking requirements. Operators we advise who are considering both a Gulf hub and the AIFC typically run the comparison on three axes: the distribution geography that matters most, the banking relationships already in place, and the regulatory timeline their product roadmap can absorb.
Against Singapore's MAS Payment Services Act regime, the AIFC offers a more direct path for issuers whose tokens are not payment tokens in the Singapore sense; but Singapore's position as a global financial centre carries network effects – secondary-market access, institutional counterpart comfort, and banking relationships – that the AIFC cannot yet match at scale.
CTA #2 — If you have already assessed one or two jurisdictions and the structure has not resolved, a second comparative read often surfaces the issue. Our team maps the licence, banking and investor-distribution stack across jurisdictions. Map your options or write to us at info@oboluslaw.com.
When is legal engagement most valuable in an AIFC token issuance?
Legal engagement before AFSA's first contact with a project is consistently more valuable than engagement after a classification determination or a pre-application query has been issued. The reason is structural: once AFSA has characterised a token as an investment token on the basis of a submitted design, the issuer is working against that characterisation. Redesigning the token's rights structure at that stage – even if technically possible – requires reopening the pre-application dialogue and in some cases restarting the clock.
The highest-leverage intervention points are, in order: the token design stage (before the whitepaper is drafted), the pre-application preparation stage (before any document is submitted to AFSA), and the disclosure-document drafting stage (before the investor-facing document is finalised). Each subsequent stage is more expensive to revisit.
For issuers coming from jurisdictions with less developed token-offering regimes, the AIFC process can feel procedurally unfamiliar. The pre-application meeting is substantive, not administrative. AFSA staff are technically informed and will probe the economic logic of a token structure. An issuer who arrives at that meeting without a clear classification analysis and a defensible whitepaper position is at a disadvantage relative to one who has stress-tested the structure with counsel beforehand.
Decision matrix by profile:
Profile A – Pre-launch issuer, token design not finalised: engage at the design stage; counsel-led classification analysis shapes the rights structure before the whitepaper locks in; indicative timeline to AFSA pre-application meeting depends on complexity of the rights structure; key risk is building an investor expectation into the token design that forces an investment-token determination.
Profile B – Issuer with an existing whitepaper, no AFSA contact yet: engage before the pre-application meeting; the whitepaper should be reviewed for classification signals before AFSA sees it; the core risk is a mismatch between the whitepaper's economic description and the utility classification the issuer is seeking; a remediation pass on the whitepaper is typically faster than a full redesign.
Profile C – Issuer who has had a pre-application query from AFSA and needs to respond: engage immediately; the response window is limited; counsel should review the query, identify the classification concern driving it, and prepare a response that either accepts the classification and adjusts accordingly, or marshals the factual and legal case for a different determination.
Related at OBOLUS
- Token offerings and securities law for digital-asset businesses – the full regulatory framework for structuring and launching token offerings across jurisdictions
- Airdrop legal structuring in Ireland – how airdrop mechanics interact with EU token-offering rules and Irish regulatory requirements
- Malta vs. Switzerland: where to license a crypto business – a comparative analysis of two leading European licensing options for digital-asset operators
FAQ
Is my token a security?
Whether a token constitutes a security – or its functional equivalent under the AIFC framework, an investment token – depends on the rights it confers, not what it is called. Rights in the nature of equity, debt, profit participation, or discretionary governance over treasury funds typically produce an investment-token determination. Utility tokens conferring access to an operational product, with no financial-return mechanic, may fall outside that category. The analysis is fact-specific and should be conducted against the actual rights structure before any document is filed or investor communication is made.
Do I need a MiCA whitepaper?
An AIFC-domiciled issuer does not automatically require a MiCA whitepaper. MiCA's whitepaper obligations are triggered by distribution to EU residents or marketing into the EU, regardless of the issuer's domicile. If your offering is restricted to non-EU investors, MiCA does not apply directly – though individual EU member states may have transitional rules. If any EU distribution is intended, a MiCA-compliant whitepaper is required in addition to any AFSA disclosure document, and the two documents must be aligned in their description of the token's rights and mechanics.
How should an airdrop be structured legally?
An airdrop distributes tokens without direct monetary consideration, but that does not place it outside regulation. AFSA and most leading regulators assess an airdrop against the same classification criteria as a sale: if the distributed token is an investment token, the distribution engages the applicable offering regime regardless of price. Structuring an airdrop requires a prior classification analysis, a defined recipient eligibility framework (including jurisdictional restrictions), AML screening of recipients above applicable thresholds, and documentation of the distribution's legal basis. Airdrops structured as marketing distributions of already-operational utility tokens carry the lightest regulatory burden.
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 entirety of our practice, and we act only for businesses. Our team assesses token classification against the substance of rights, not the marketing label – the same standard regulators apply. To discuss your token structure or an AIFC filing, contact info@oboluslaw.com or reach us at t.me/oboluslaw.
By Roman Levitt, Technology & DeFi Counsel – specialist in token design, smart-contract legal analysis, and the regulatory treatment of novel digital-asset structures across common-law 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.