EST · MMXXVI
Home/Jurisdictions/Kazakhstan Aifc/Tax treatment of tokens in Kazakhstan (AIFC)
Tax & Cross-border Structuring

Tax treatment of tokens in Kazakhstan (AIFC)

Tax treatment of tokens in Kazakhstan (AIFC). Cross-border digital-asset legal counsel for business – licensing, disputes and structuring. Talk to OBOLUS.

For a token-issuing business weighing its holding structure, the AIFC (Astana International Financial Centre) offers a genuinely distinct tax environment – one that diverges from the general Kazakhstani tax code and operates under its own legal regime. Entities incorporated within the AIFC and conducting digital-asset activities there benefit from a dedicated regulatory perimeter administered by the AFSA (Astana Financial Services Authority), and from tax arrangements that are set out in the AIFC's founding constitutional act rather than the national Tax Code. That distinction is consequential for any operator sizing up Kazakhstan as a structuring jurisdiction. This page sets out the tax treatment of tokens in Kazakhstan's AIFC, the interaction between corporate structure and personal tax residency, and the decision points that operators most commonly miss.

Token taxation inside the AIFC is governed by a bespoke constitutional framework that grants the centre a degree of regulatory autonomy absent from the rest of Kazakhstan. The AIFC operates under English common-law principles with its own courts and arbitration centre; the AFSA is the financial regulator. Tax treatment flows from the AIFC's founding act and associated regulations rather than from the general provisions of the Kazakhstani Tax Code that apply to standard resident entities. That separation is the first material fact any operator must understand.

Within this perimeter, digital-asset activities are recognised as regulated activities. The AFSA administers a digital-asset framework that includes trading-facility and custody concepts. Entities seeking to issue or deal in tokens therefore face a dual question: regulatory authorisation under the AFSA regime, and tax treatment under the AIFC's own fiscal rules.

The AIFC's tax incentives – which include exemptions on corporate income tax and certain other imposts for qualifying participants – are among the centre's signature competitive features. Operators should understand, however, that the scope of those exemptions, the conditions attaching to them, and the interaction with Kazakhstan's domestic withholding tax regime require careful mapping. The specific rates, thresholds and qualifying conditions are set by AIFC instruments that are updated periodically; any operator should work from current official AIFC publications rather than secondary sources.

In our cross-border practice, we regularly see operators assume that AIFC incorporation is sufficient to secure all available tax concessions. It is not. The entity must be a genuine participant conducting regulated activities within the AIFC's scope, and it must maintain adequate substance. An entity that incorporates inside the AIFC but directs its operations from outside – or that holds tokens purely passively without meeting the relevant activity thresholds – may find that the expected exemptions do not apply.

The AFSA is the principal regulator for financial-services activities within the AIFC, and AFSA authorisation status is closely linked to tax-incentive eligibility in practice. This connection between regulatory standing and tax treatment is a cross-cutting theme that operators frequently underestimate at the structuring stage.

How Does Token Classification Drive Tax Outcomes in the AIFC?

Token classification within the AIFC follows a substance-over-label principle: the rights conferred by a token determine its legal and tax character, not the issuer's chosen marketing term. Payment tokens, utility tokens, and investment tokens each attract different regulatory treatment under the AFSA framework, and those distinctions flow through to the tax analysis.

An investment token – one that confers equity-like or debt-like rights, or that tracks an underlying asset – is more likely to be treated as a financial instrument for both regulatory and tax purposes. Gains on such tokens, income distributions, and transfer-event proceeds are each analysed differently from those arising on a payment or utility token. For token issuers, this means the whitepaper, the token-rights documentation, and the internal classification memo are not merely regulatory compliance artefacts; they are tax-positioning documents.

Stablecoin issuers face a further layer. Reserve composition and redemption mechanics interact with AIFC regulatory expectations and with the question of whether the token constitutes an e-money analogue or an asset-referenced instrument. The answer affects both AFSA authorisation obligations and the income-characterisation question for the issuer – whether receipts on the reserve portfolio constitute trading income, investment income, or something else entirely.

For operators issuing tokens cross-border – with the AIFC entity as the issuer but token-holders located in the EU, the UK, or elsewhere – the characterisation question multiplies. A token that the AIFC treats as a utility instrument may be characterised as a security by the FCA or by ESMA's guidance under MiCA. Each such characterisation carries its own withholding and reporting implications in the holders' jurisdiction. Managing that divergence requires a coordinated position across the relevant regimes, not a separate memo for each.

The principle that substance governs form – not the marketing label – is one that AIFC regulators and tax administrators apply with increasing rigour, in line with the broader international direction set by FATF and the OECD. Operators that build classification logic early, in a structured taxonomy tied to the token-rights documentation, place themselves materially ahead of those that reclassify reactively after a regulator queries the whitepaper.

How Should a Token-Issuing Group Structure Its AIFC Holding Company?

The optimal AIFC holding structure for a token-issuing group depends on three converging variables: where the operating activity occurs, where the founders are personally resident, and where an eventual liquidity event will be recognised. Getting those three elements into alignment at incorporation is considerably less costly than restructuring after the fact – a point we make to every founder group we advise in this jurisdiction.

A common architecture places the AIFC entity as the issuing vehicle or the treasury entity for token reserves, with operating subsidiaries in one or more other jurisdictions handling exchange relations, customer onboarding, or protocol development. The AIFC entity benefits from the centre's tax perimeter; the subsidiaries carry the operational risk and the local regulatory footprint. This structure works when the AIFC entity genuinely manages the group's intellectual property, token issuance decisions, and treasury functions from within the AIFC.

It does not work when the AIFC entity is a brass-plate holding company with no genuine personnel or decision-making capacity. The AFSA's substance expectations – and the AIFC's own tax-incentive conditions – require that the entity carries out real activity. Personnel, physical presence, and records kept within the AIFC are not optional refinements; they are substantive requirements that regulators and tax administrators examine.

The cross-border angle introduces additional complexity. A group with a Cayman or BVI feeder fund, an AIFC treasury entity, and an EU-regulated operating subsidiary under MiCA must map the intercompany flows – management fees, royalties on protocol IP, treasury returns – against the transfer-pricing expectations of each jurisdiction involved. The AIFC does not operate in isolation; it is one node in a multi-jurisdiction structure, and the overall structure is only as clean as its weakest link.

To map the licence, banking and tax stack for your build, write to info@oboluslaw.com.

The process above describes the standard path. Your facts – the entity type, the token classification, the founder's existing residency, the banking relationships – change the analysis significantly.

Why Personal Tax Residency Cannot Be Separated From Corporate Structure

A common assumption among founders entering the AIFC environment is that relocating personally to Kazakhstan – or to any third jurisdiction – is sufficient to separate their personal tax exposure from the group's corporate structure. That assumption is incorrect, and it is among the most expensive mistakes we see in cross-border digital-asset practice.

Personal tax residency is determined by domestic rules in the founder's home jurisdiction, the relevant tax treaty (where one exists), and the actual pattern of days and economic ties. Kazakhstan has a network of tax treaties; the AIFC's own regime adds a further layer. But none of that insulates a founder who retains a primary residence in a high-tax jurisdiction, who continues to exercise management control from that jurisdiction, or whose former home country applies a look-through or deemed-residency rule.

The interaction between founder residency and corporate residence is particularly acute for token issuers. Where the founder is the key decision-maker for token issuance, protocol upgrades, and treasury management, tax authorities in high-tax jurisdictions may argue that the AIFC entity's place of effective management is wherever the founder is sitting. That argument – familiar from traditional offshore structures – applies with equal force to digital-asset holding companies.

Effective structuring therefore requires a joined-up analysis: the entity's registered office, its substance within the AIFC, the location of key management decisions, and the founders' own residency positions must all be mapped together. Exit planning is part of that analysis from day one. A liquidity event that triggers a capital gain will be taxed according to the residency position that exists at the time of realisation, not the position the founder intended to reach by then.

We align founder residency with the holding structure and exit plan as a single integrated exercise – not as two separate instructions to two separate advisers.

AML Obligations, Banking Relationships, and Substance Requirements in Practice

Regulatory compliance under the AFSA regime is the gateway to the AIFC's tax environment, not a separate track. An entity that loses or fails to obtain AFSA authorisation also loses the basis for claiming the AIFC's tax concessions. That linkage is not theoretical; it surfaces in practice whenever an operator's AML programme or substance documentation falls short of AFSA expectations.

The AFSA applies FATF standards to AIFC-regulated entities, including the Travel Rule (the obligation to pass originator and beneficiary data with a transfer) for qualifying virtual-asset transfers. Token issuers and custody providers operating from the AIFC must build Travel Rule compliance into their operational architecture before launch, not after. The cost of retrofitting a compliant data-transfer mechanism into a live protocol is materially higher than building it in from the outset.

Banking is a perennial pressure point. Correspondent banks serving Kazakhstani financial institutions apply their own due-diligence overlays to digital-asset businesses, regardless of AIFC status. In our practice, we regularly advise operators that AIFC regulatory authorisation improves the banking conversation but does not end it. A well-prepared banking application for an AIFC digital-asset entity includes the AFSA authorisation, a clear articulation of the business model and token classification, the AML/KYC programme documentation, and – where the entity is part of a multi-jurisdiction group – a group structure chart that explains the intercompany flows.

Substance documentation for the AIFC entity itself runs parallel to the banking file. Lease agreements or licensed office use within the AIFC, employment or service contracts for personnel physically present in Astana, and board-meeting records showing decisions taken within the AIFC are the core artefacts. These are the same documents that a tax authority will request if it challenges the entity's right to AIFC tax treatment, so building them correctly from inception serves both purposes.

If a prior application stalled or an account was closed, a second read of the structure can surface the underlying reason and the route forward. Write to info@oboluslaw.com to discuss.

How Are Staking Rewards, DeFi Yields, and Secondary Token Income Treated?

Novel income streams – staking rewards, liquidity-provision yields, protocol fees, and secondary market gains on treasury holdings – do not fit neatly into traditional income-tax categories, and the AIFC's evolving framework does not yet provide bright-line answers for every scenario. The analysis proceeds by analogy with the established categories: trading income, investment income, or capital gain, depending on the nature of the activity and the entity's overall business characterisation.

For an entity characterised as a trading business – for instance, a token-issuing entity that actively manages its treasury and participates in protocol governance – staking rewards and DeFi yields are more likely to be characterised as income receipts than as capital events. The frequency of activity, the nature of the protocol relationship, and the entity's stated business purpose in its AFSA application all contribute to that characterisation.

For a holding entity whose primary function is to hold and administer a token reserve, the same receipts may be more readily characterised as passive investment returns. The distinction matters because the applicable tax treatment – and the interaction with any AIFC tax concession – follows the characterisation.

Cross-border DeFi participation introduces additional questions. An AIFC entity that participates in a protocol governed by a DAO (decentralised autonomous organisation) may have difficulty demonstrating that its decision-making occurs within the AIFC, particularly where voting and governance activity is conducted via on-chain mechanisms from wherever the founders happen to be. That is not an insurmountable problem, but it requires deliberate operational design.

Operators we advise routinely document their staking and DeFi activity in a way that maps each receipt to a business-purpose rationale and a jurisdiction of decision-making. That discipline is low-cost at outset and high-value in a later audit or regulatory review.

Practical Illustration: Restructuring a Token Treasury Into the AIFC

In a recent cross-border structuring matter, a blockchain-infrastructure business headquartered in a high-tax European jurisdiction sought to migrate its token treasury function into the AIFC. The founders had previously assumed that an entity-level migration was sufficient; in fact, two of the three founders remained tax-resident in their home jurisdiction and continued to exercise day-to-day treasury decisions from there. We identified that the AIFC entity, as structured, had an arguable place of effective management outside Kazakhstan and did not meet the AIFC's substance thresholds for its claimed tax treatment. Working with allied counsel in the relevant European jurisdiction, we redesigned the management-meeting cadence, the delegation of authority, and the founders' personal residency timelines in parallel. The AIFC entity's operations were contemporaneously documented with the substance requirements in mind. The restructured group entered the AIFC's regulatory authorisation process on a defensible footing, with a banking file that reflected the group's corrected structure from day one.

Which Operator Profile Benefits Most From the AIFC Tax Environment?

Not every digital-asset business is optimally served by an AIFC structure. The decision turns on a handful of key variables, and being honest about those variables at the outset saves significant cost later.

Profile A: early-stage token issuer, founders mobile, no existing high-tax domicile. This profile benefits most from the AIFC. The founders can establish genuine residency within or near Astana, the AIFC entity can carry real substance, and the regulatory authorisation process under the AFSA can proceed in parallel with the tax structuring. The timeline from entity incorporation to AFSA authorisation to operational launch is typically a matter of months, though it varies with the complexity of the business model and the completeness of the application.

Profile B: established group with existing EU-regulated operating subsidiary and a founder base across multiple jurisdictions. This profile requires more care. The AIFC can serve as a treasury or holding entity in the group structure, but the interaction with MiCA's passporting rules, the transfer-pricing implications of intercompany flows, and the personal residency positions of the founders must all be mapped before the AIFC entity is incorporated. Rushing to incorporate without that analysis typically produces a structure that cannot withstand a tax-authority challenge in any of the jurisdictions involved.

Profile C: DeFi protocol operator seeking a regulated domicile for governance and treasury. The AIFC is a credible option for this profile, but the on-chain governance question – where decisions are effectively made – requires careful operational design. The AFSA's framework for decentralised structures is still developing, and operators in this profile should engage counsel before making representations in regulatory applications about the nature of their governance model.

For a scoped assessment of your structure, contact OBOLUS at info@oboluslaw.com.

Self-Assessment: Is Your AIFC Token Structure Tax-Defensible?

Before committing to an AIFC token structure, operators should be able to answer affirmatively to each of the following questions. Where the answer is uncertain, that uncertainty is the scope of the legal work required.

  • Has the entity been incorporated as a genuine AIFC participant with a clear scope of regulated activity under the AFSA framework?
  • Is the token classification documented in a taxonomy memo that maps each token type to its rights, its regulatory category, and its tax characterisation?
  • Do the founders' personal residency positions align with the entity's claimed place of effective management?
  • Is there a contemporaneous substance file – lease or licensed office, personnel records, board-meeting minutes – that demonstrates real activity within the AIFC?
  • Have the intercompany flows between the AIFC entity and any non-AIFC group members been mapped against transfer-pricing expectations in each relevant jurisdiction?
  • Is the AML/CFT programme – including Travel Rule compliance – built into the operational architecture rather than deferred to a post-launch phase?
  • Has the banking strategy been prepared with a complete group-structure disclosure and a clear articulation of the token classification and business model?
  • Is the exit plan – including the anticipated form of any liquidity event – reflected in the current structure, so that the residency and holding-period positions are correct at the time of realisation?

Operators who work through this checklist before incorporation consistently face fewer structural corrections later. We have seen the alternative: a group that incorporates first and answers these questions under pressure from a regulator or bank is working at a significant disadvantage.

Cross-Border Interaction: The AIFC in a Multi-Jurisdiction Group

The AIFC does not exist in regulatory isolation, and neither does a digital-asset business structured around it. An AIFC-domiciled token issuer serving users in the EU, the UK, or Singapore is also within the reach of MiCA's extraterritorial marketing rules, the FCA's financial-promotion regime, and MAS's Payment Services Act – depending on where the users are located and how the service is offered. Regulatory authorisation in the AIFC does not substitute for compliance obligations in the jurisdictions where users are onboarded.

Tax treaty networks provide partial relief from double taxation, but treaty access requires that the AIFC entity meets the treaty's residency and beneficial-ownership conditions. Not every treaty Kazakhstan has concluded will apply straightforwardly to an AIFC-incorporated entity; some treaties were concluded before the AIFC's constitutional framework existed, and their application to AIFC participants involves an interpretive question that should be resolved with reference to current treaty practice and AIFC guidance.

VAT and indirect tax treatment of token transactions is a further cross-border consideration. Different jurisdictions take different positions on whether the issuance of a token, the transfer of a token, or the exchange of a token for fiat or another asset constitutes a taxable supply for VAT or GST purposes. An AIFC entity operating in a cross-border context will need to map those positions for each jurisdiction where it has a taxable nexus, and ensure that its invoicing and reporting architecture reflects the correct characterisation in each place.

In our practice, the multi-jurisdiction tax mapping exercise – which addresses the AIFC position, the treaty network, the EU VAT/MiCA interaction, and the founders' personal positions in a single integrated document – is the most reliable predictor of whether a structure will hold up to scrutiny across the group's lifetime.

Related at OBOLUS

FAQ

Where should a token-issuing entity be domiciled?

There is no universal answer. The AIFC suits mobile founders who can establish genuine substance in Astana and who need a common-law framework with digital-asset-specific regulation. The EU (under MiCA) suits businesses that need passporting access across the EEA. Singapore, the ADGM, and the Cayman Islands each suit different operator profiles. The decision turns on where users are located, where founders can be genuinely resident, what the exit plan looks like, and where banking relationships can realistically be maintained. A structured comparison across three to five options is the correct starting point.

How are staking rewards taxed?

The AIFC does not provide a bright-line published rule for staking rewards. The analysis proceeds by characterisation: if the entity is a trading business, staking rewards are likely treated as income; if it is a passive holding entity, they may be characterised as investment returns. The applicable AIFC tax concession – and its conditions – must then be overlaid. The answer varies by entity type, activity level, and the specific AIFC instrument in force at the time. Operators should obtain a written analysis tied to their entity's characterisation before reporting staking income.

Does remote working create tax residency risk?

Yes, and the risk is frequently underestimated. A founder or key executive who works remotely from a high-tax jurisdiction while nominally resident in the AIFC environment may be treated by that jurisdiction as continuing to exercise effective management from within its borders. The result can be that the corporate entity is also treated as resident – or as having a permanent establishment – in the high-tax jurisdiction. Preventing that outcome requires deliberate management of the founder's physical location, decision-making records, and the delegation-of-authority structure within the group.

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 align founder residency with the holding structure and exit plan as a single integrated exercise – because the two cannot be decided independently. To discuss your situation, contact info@oboluslaw.com.

By Lydia Brennan, Tax & Structuring Analyst – specialist in cross-border digital-asset holding structures, token classification, and founder residency planning for AIFC and multi-jurisdiction groups.

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