Licensed virtual-asset businesses operating inside the Astana International Financial Centre (AIFC) face a question that surfaces well before go-live: what physical and operational presence does Kazakhstan actually require? The answer turns on the Astana Financial Services Authority (AFSA) regulatory regime, which applies common-law principles within the AIFC perimeter and expects demonstrable substance – not merely a registered address and a board resolution signed abroad. For any business that has licensed or is licensing a digital-asset activity through the AFSA, getting substance wrong is the fastest route to a licence review, a banking relationship that never opens, or an enforcement notice that arrives before the first trade settles.
Economic substance for licensed VASPs (virtual asset service providers) in Kazakhstan's AIFC means maintaining a genuine operational presence within the AIFC perimeter: qualified personnel on the ground, a functioning compliance infrastructure, decision-making that occurs locally, and financial records that reflect real business activity in the jurisdiction. The AFSA regime does not accept shell structuring, and AIFC banks – which are the gateway to USD, EUR and tenge settlement – apply their own substance assessments independently of the regulator. For a business sitting between a European parent and an Asian user base, the substance question in Astana is both a regulatory requirement and a banking precondition.
The sections below map the substance requirement in detail: what AFSA expects, how it interacts with the cross-border tax and banking stack, where inbound operators typically miscalculate, and what the decision point looks like for different operator profiles.
What economic substance means under the AFSA regime
The AFSA regime defines authorised activities for digital-asset businesses – including digital-asset trading facility operations, custody, and related advisory functions – and ties each authorisation to the expectation that the regulated entity is genuinely managed and controlled within the AIFC. This is not a new concept in financial regulation. What is distinctive here is that the AIFC operates as a common-law enclave inside Kazakhstan, governed by its own body of AIFC acts and AFSA rules, entirely separate from the Republic of Kazakhstan's civil-law framework. That dual legal reality matters: substance inside the AIFC perimeter satisfies AFSA; activities outside the perimeter, even within Kazakhstan, fall under a different legal order.
In our practice, AFSA-regulated firms are expected to maintain a registered office within the AIFC, hold board or senior management meetings locally at a meaningful frequency, employ or appoint qualified key function holders – including a compliance officer and a money laundering reporting officer – who are physically accessible, and ensure that the core risk and compliance decisions are made within the jurisdiction. A purely nominee structure, where all decisions are taken by a parent entity abroad and the AIFC entity receives only formal ratification duties, consistently draws scrutiny during AFSA supervisory reviews.
The AFSA regime applies to digital-asset trading facility operators and custodians through its framework of recognised virtual assets and regulated activities within the AIFC. Operators who treat the AIFC licence as a flag-of-convenience arrangement, rather than as the home of a functioning regulated business, expose themselves to supervisory action and – critically – to the loss of access to the AIFC banking infrastructure that makes the licence commercially viable in the first place.
CTA #1 – For the reader encountering the substance requirement for the first time
The substance analysis above describes the standard expectation. Your specific facts – the entity structure, the jurisdictions where your users sit, where your directors are resident, and how your treasury is managed – change the assessment materially. For a scoped review of your AIFC substance position, map your options with OBOLUS.
Who needs to satisfy substance requirements in the AIFC?
Any entity that holds or is seeking an AFSA authorisation to carry on digital-asset activities within the AIFC is subject to the substance expectation – but the practical intensity varies by licence category and business model. A digital-asset trading facility operator with a large user base in Central Asia and the CIS region faces a more demanding substance analysis than a custody-only entity that services a handful of institutional counterparties. Size of operation, volume of regulated activity, and the degree of cross-border interconnection all influence what AFSA considers adequate.
Inbound operators should also note a point that is frequently underestimated: the AFSA substance expectation is not discharged simply by incorporating in the AIFC and appointing a local compliance officer on a retainer basis. Regulators in the leading hubs increasingly expect the compliance function to be integrated into the business – attending deal and product decisions in real time, not reviewing them retrospectively. We have seen applications stall at the final authorisation stage because the proposed compliance resourcing was clearly insufficient for the volume and complexity of the business described in the application.
Non-AIFC entities – businesses that operate digital-asset services from outside the AIFC into Kazakhstan or into the AIFC perimeter without authorisation – are a separate category. They do not satisfy the substance requirement by definition, and they face the additional exposure of operating without the regulatory authorisation that the AFSA regime requires for the relevant activity.
What does the AFSA authorisation process assess?
The AFSA authorisation process for digital-asset businesses follows a structured pathway: pre-application engagement with AFSA, submission of the formal application with supporting documentation, a fitness-and-propriety assessment of key individuals, and a review of the proposed business plan, compliance arrangements and financial projections. Timeline from submission to authorisation varies by licence category and the completeness of the application; in our experience, operators who engage AFSA early in a pre-application dialogue and arrive with a well-prepared file move materially faster than those who submit cold.
The substance documentation that accompanies the application is a significant portion of the file. AFSA expects to see: an organisation chart showing where key functions sit and who holds them; CVs and background checks for proposed key function holders; a compliance manual and AML/CFT programme tailored to the AIFC's AML obligations (which align to FATF Recommendation 15 on virtual assets and incorporate the Travel Rule – the obligation to pass originator and beneficiary data with a transfer); a business continuity plan; and evidence of the physical office within the AIFC.
Key function holders who are proposed at the application stage are assessed individually. AFSA applies a fit-and-proper standard that considers professional experience, regulatory history and criminal background. A proposed compliance officer who has never operated in a digital-asset environment will draw questions. So will a proposed MLRO who is simultaneously performing that function for multiple unrelated entities. We regularly advise clients on structuring the proposed key function team before the application is submitted, because changes forced during the review process add weeks to the timeline.
For businesses structured across multiple jurisdictions – a holding company in the BVI or Cayman Islands, an operating entity in the AIFC, and a technology entity elsewhere – the AFSA review will also consider the group structure and the flow of funds and instructions between entities. A holding structure that effectively strips the AIFC entity of decision-making authority is a substance risk at the application stage, not merely a post-authorisation supervisory concern.
How does substance interact with cross-border tax and banking?
The AIFC's tax regime is a significant part of its commercial proposition: entities authorised within the AIFC benefit from a defined tax environment that differs materially from the standard Kazakhstani tax position. However, the tax benefit is tied to the substance of the AIFC entity. A company that claims AIFC tax treatment while its real management and control sit in another jurisdiction – whether that is the UAE, the UK or a European hub – faces exposure under the tax residency rules of that other jurisdiction. The effective management and control test applied in most leading jurisdictions is not satisfied by the AIFC entity holding a formal licence if all decisions are taken by directors resident abroad.
In our cross-border practice, we frequently see operators who have structured correctly for AFSA purposes but have not addressed the permanent establishment risk in the jurisdiction where their senior management physically sits. Where a key executive in Dubai or London is making binding commercial decisions for the AIFC entity on a daily basis, the tax analysis in those jurisdictions becomes relevant – and the interaction between UAE corporate tax (effective from June 2023 for most businesses), UK corporation tax rules on overseas management and control, and the AIFC tax position requires careful mapping before the structure goes live.
AIFC banking access – through banks that are themselves authorised within the AIFC perimeter – is a separate gating requirement. AIFC banks conduct their own customer due diligence and substance assessments. A business with a live AFSA authorisation but no AIFC bank account is operationally non-functional. We have seen situations where an entity obtained authorisation but could not open an account because the bank's internal standards required a longer operational track record or a higher level of capitalization than the AFSA minimum. The practical lesson is that the banking application should run in parallel with, not sequentially after, the regulatory authorisation process.
For operators whose user base spans the CIS region, stablecoin settlement may be part of the business model. In that context, the Travel Rule obligations apply to transfers above the applicable threshold, and the AIFC entity must have the technical infrastructure to capture and transmit the required originator and beneficiary data. The compliance programme submitted to AFSA should address this explicitly.
What are the most common substance mistakes inbound operators make?
Operators entering the AIFC from a European or Middle Eastern base tend to make a predictable set of miscalculations. First, they underestimate the staffing requirement. The AIFC is not a mail-drop regime. AFSA expects real people performing real functions in Astana. Outsourcing the compliance function entirely to a third-party provider, while technically possible for some sub-functions, does not satisfy the requirement for an accountable, accessible compliance officer and MLRO who are integrated into the regulated business.
Second, they conflate the AIFC's common-law environment with more permissive offshore regimes. The AIFC courts and the AFSA supervisory framework are genuinely sophisticated. The AIFC has its own court system, with English-language proceedings conducted under English common-law principles. This is a real regulatory environment, not a light-touch offshore registration. Operators who have previously managed a BVI or Cayman registration with minimal local presence are sometimes surprised by the rigour of the AFSA review process.
Third, they delay the banking application. We have outlined above why this matters. A concrete deadline to add: AIFC banks typically require a period of documented operational activity before they are comfortable with a new digital-asset client. Starting the banking conversation on the day of AFSA authorisation is too late.
Fourth – and this applies specifically to groups with a parent entity in a FATF-monitored jurisdiction – the group AML/CFT policy must be adapted for the AIFC context. A boilerplate global AML policy that does not address the AIFC's specific virtual-asset obligations, including Travel Rule implementation, will not satisfy the AFSA compliance documentation review.
In a recent licensing matter, a digital-asset trading business from Eastern Europe engaged us after an initial AFSA application had been returned with substantive comments. The primary issue was that the proposed key function holders were all resident outside Kazakhstan and had proposed to perform their roles remotely. We restructured the staffing plan, engaged a qualified local compliance officer, revised the AML programme to address AIFC-specific obligations, and resubmitted the application. The authorisation followed within a matter of months. The entity is now operational with a live banking relationship within the AIFC.
Which operator profile is best suited to the AIFC?
Not every digital-asset business belongs in the AIFC. The right structure depends on where the users are, where the business is managed, and what regulatory recognition the licence will carry in the markets the business actually wants to serve. The AIFC is a strong fit for certain profiles; for others, it is a secondary or supporting jurisdiction rather than the primary hub.
Profile A – CIS-focused exchange or trading platform operator. A business whose primary market is Kazakhstan, Uzbekistan, Russia or other CIS markets, whose management is willing to maintain meaningful presence in Astana, and that values the AIFC's common-law environment and banking access. This profile derives full commercial value from the AIFC licence. The timeline to authorisation is driven by document readiness; the substance investment is real but proportionate to the market opportunity.
Profile B – European or UAE operator seeking a regional hub for CIS distribution. A business that already holds a MiCA-aligned or VARA authorisation and wants to serve CIS clients from a recognised common-law jurisdiction. The AIFC can function as a regional licence for this purpose, but the operator must genuinely staff the Astana entity rather than treating it as a pass-through. The cross-border tax analysis – particularly the interaction between the UAE corporate tax regime, any European group entities, and the AIFC tax position – requires specific attention before the structure is committed.
Profile C – Custody or infrastructure provider serving institutional counterparties. A business that provides custody or settlement infrastructure to institutional clients in the CIS and Central Asian markets. This profile may be able to operate with a leaner physical footprint than a retail-facing exchange, but the substance requirement remains: qualified key function holders, a functioning compliance programme, and an operational office within the AIFC perimeter. A pure nominee arrangement is not sufficient.
For any of these profiles, the decision to license in the AIFC is best made after mapping the full stack: the regulatory authorisation, the banking access, the tax position, and the substance investment required. A common assumption is that the AIFC licence is interchangeable with a VARA or MiCA authorisation for global distribution purposes. It is not. The AIFC licence gives AFSA recognition and AIFC banking access; it does not confer regulatory equivalence in the EU, the UK or the UAE. A business that needs to serve clients in those markets will need separate authorisations for each regulated perimeter.
CTA #2 – For the reader who has already attempted and hit a barrier
If an AFSA application has stalled, an AIFC bank account application has been declined, or a prior structure has drawn regulatory comment, the root cause is almost always a substance or compliance documentation issue that can be identified and addressed. To pressure-test your structure before you commit further, message our licensing desk via our contact page.
Related at OBOLUS
- Licensing and registration for digital-asset businesses – the full licence stack across operating, custody and payment layers.
- Reverse solicitation: a legal guide for digital-asset businesses – when cross-border service delivery is permissible without a local licence.
- Stablecoin issuance authorisation in the United Kingdom – how the FCA regime applies to stablecoin issuers with cross-border exposure.
FAQ
How long does a crypto licence take to obtain?
Timeline within the AIFC depends on licence category and application readiness. Operators who engage AFSA in pre-application dialogue and submit a complete, well-structured file move materially faster than those who submit cold. In our experience, a thorough preparation period before submission – covering key function appointments, AML programme drafting and substance documentation – is the primary timeline driver. Expect the process to take a number of months from first engagement to authorisation.
Which jurisdiction is best for licensing my crypto business?
There is no single answer. The right jurisdiction turns on where your users are, where your management sits, what regulated activities you will perform, and what banking access you need. The AIFC suits operators focused on CIS markets who can commit genuine substance in Astana. Operators targeting the EU need a MiCA-aligned CASP authorisation. Those serving the Middle East should assess VARA or ADGM/FSRA. We map the full licence stack across operating, custody and payment layers before recommending a structure.
Do I need a separate custody licence?
Within the AIFC, custody of digital assets is treated as a distinct regulated activity under the AFSA regime. An entity authorised to operate a digital-asset trading facility is not automatically authorised to provide custody services. Operators who intend to hold client assets must obtain the relevant custody authorisation separately. The substance requirements for a custody entity – including key function appointments, safeguarding arrangements and the compliance programme – are assessed by AFSA on their own terms, not as an extension of the trading facility authorisation.
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. We map the licence stack across operating, custody and payment layers before you commit – so that regulatory, banking and tax questions are answered as a single structure, not as sequential surprises. We advise crypto exchanges, custodians, token issuers and funds across more than seventy licensing jurisdictions. Digital assets are the whole of our practice. To discuss your situation, contact info@oboluslaw.com.
By Aisha Tan, Licensing & Jurisdictions Analyst – specialising in AFSA and multi-hub digital-asset licensing across the AIFC, ADGM and Central Asian markets.
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.