Short answer: India’s current public VDA framework treats crypto assets and NFTs as virtual digital assets for the purposes described in official tax guidance, while specific categories such as Indian currency, CBDCs, foreign currency, and notified assets are excluded from that definition. At a high level, the published tax guidance describes a distinct treatment for income from VDA transfers, and the compliance landscape separately includes FIU-IND rules for in-scope VDA service providers. The details matter: a label, role, date, record, and the status of a rule can change the meaning of a statement.

Education-only limitation — as of 20 September 2026: This is an educational reader guide, not tax, legal, investment, trading, security, or other professional advice. It does not determine anyone’s tax position, regulatory status, or reporting obligation, and it does not provide transaction instructions. The discussion is confined to the approved research dossier and is designed to help readers recognise concepts, terminology, and source limits.

Table of contents

  1. Why terms and scope come first
  2. What the VDA definition includes and excludes
  3. High-level tax treatment and the role of acquisition cost
  4. TDS as a reporting and information context
  5. Recordkeeping as an evidence and reconciliation concept
  6. FIU-IND reporting-entity scope
  7. AML/CFT concepts in the VDA setting
  8. Timing, status, and source-of-truth limits
  9. Reading examples without turning them into advice
  10. Frequently asked questions

Why terms and scope come first

Crypto regulation is often discussed as though one label answers every question. It does not. The phrase virtual digital asset, or VDA, is a defined term used in India’s public tax guidance. A separate question is whether an organisation is carrying on a service that falls within FIU-IND’s reporting-entity framework. A third question is what a particular document actually says on a given date. Treating those questions as interchangeable can produce an inaccurate conclusion.

A single technical system can involve different roles: a reader, an intermediary providing exchange, transfer, or safekeeping-related services, or an issuer-side activity connected to token issuance. The dossier treats these as different contexts, not a universal regulatory label. Education therefore begins with scope before tax or AML/CFT terminology.

Technical facts do not settle tax classification, service-provider scope, ownership evidence, or the status of a rule. Global technical context can clarify an India-focused explanation, but it cannot replace Indian source material. For a wider topic index, see Regulation.

What the VDA definition includes and excludes

The Income Tax Department guidance identified in the approved dossier states that virtual digital assets include crypto assets and NFTs. It also describes exclusions from the definition: Indian currency, central bank digital currencies, foreign currency, and notified assets. This inclusion-and-exclusion structure is more useful than relying on casual descriptions such as coin, token, digital money, or crypto.

Two reading cautions follow. First, an everyday label is not a substitute for the official definition. Calling something a token does not, by itself, explain whether it is within a stated category. Second, an exclusion in the definition is not a broad statement about every other legal or economic question. Definitions operate within an identified framework. A reader should avoid carrying an answer from one framework into another simply because the words sound similar.

Consider an illustrative classification exercise with no assumption about a real person or product. A reader encounters three descriptions: a crypto asset, an NFT, and a CBDC. The official summary in the dossier places the first two within the VDA description and identifies CBDCs as excluded. That comparison teaches how a defined boundary works. It does not establish the treatment of a specific arrangement, decide whether a particular item meets a definition, or address a transaction’s consequences.

Definition boundaries also explain why status-preserving language matters. An asset may be technically described in a certain way while questions about taxation, service provision, custody, or financial crime controls involve different documents and facts. Clear writing says what source is being discussed and resists expanding a narrow definition into a general conclusion.

High-level tax treatment: transfer income and acquisition cost

The approved dossier summarises the Income Tax Department’s current public guidance this way: income from transfers of VDAs is computed without deductions other than acquisition cost and is taxed at 30%, plus surcharge and cess. This is a high-level description, not a calculation tool. It signals that the published VDA treatment is distinct in its treatment of deductions and that acquisition cost has a specifically identified place in the official summary.

A rule summary is different from applying it to facts. The phrases income from transfer and acquisition cost identify concepts in the public guidance; neither gives a reader-specific outcome. Dates, asset identity, event sequence, documentation, other provisions, and changes in law or notification status can matter. This guide does not turn those variables into instructions or tax advice.

Imagine a record with an acquisition-side amount, a later transfer-side amount, and unrelated costs. The public guidance is notable because it names acquisition cost rather than giving an open-ended list of deductions. This is not a formula or a decision on qualifying items; it explains why preserving a cost’s source description can matter conceptually.

For a companion overview of the topic boundary, read India’s VDA tax framework reader map. The linked article is internal reading, not a substitute for the primary materials or professional judgment.

TDS: an information and reporting context

TDS is frequently discussed beside VDA taxation, but it should not be collapsed into the whole tax framework. In a reader guide, it is best understood first as a context in which information, timing, and records can matter. A reference to TDS does not automatically answer the separate questions of how a VDA is defined, what constitutes income from a transfer, what acquisition cost means in a particular set of facts, or whether a service provider falls within an AML/CFT regime.

A tax-related entry or statement does not settle every aspect of an underlying event. It may help describe the event, but its meaning depends on source documents and the framework under review. An absence or delay in one information source is not proof that no rule or recordkeeping issue exists.

Because this article provides no transaction instructions, it does not explain how to make a deduction, file a return, reconcile an account, or decide a tax position. Its educational point is narrower: TDS belongs in the vocabulary of VDA tax discussions, and it must be read with dates, event descriptions, and source limits rather than as a stand-alone verdict.

Recordkeeping: from scattered data to an intelligible event trail

Recordkeeping is not merely an administrative afterthought. In a VDA context, information may be dispersed across a service interface, a blockchain record, a statement, a communication, and a contemporaneous note. These sources may use different timestamps, identifiers, currencies, labels, and display conventions. A durable educational model is to view the records together as an event trail: what was described, when it was described, which asset identifier appeared, what amounts were shown, which fees or costs were separately labelled, and what the source was.

The dossier notes that blockchain records may be public and payments commonly irreversible. Public visibility does not mean an on-chain entry supplies every fact needed for a tax or compliance interpretation. It may show that a network recorded data, without explaining the off-chain identity relationship, service-provider context, purpose, or accounting label. A platform display can be informative without being the sole source of truth.

Consider a source record dated in one time zone and a network record marked in another. A date mismatch need not show an error or a result: it may reflect timestamp conventions, processing time, or different stages of an event. The educational point is that time markers differ and source metadata is evidence.

For a focused explanation of this topic, see Recordkeeping for India VDA users. That internal guide can be read alongside the tax framework rather than as a complete determination of any reader’s circumstances.

FIU-IND reporting-entity scope: activity matters

The approved dossier identifies FIU-IND guidelines, updated on 8 January 2026, that describe VDA service providers engaged in certain activities as reporting entities. The listed activities are fiat-to-VDA exchange, VDA-to-VDA exchange, transfers, safekeeping or administration, and financial services connected to token issuance. This is an activity-based scope description. It is not a statement that every person who holds, reads about, develops, or uses a VDA is a reporting entity.

That boundary is central to accurate regulatory literacy. A reader should distinguish an individual’s personal context from the operation of a service, and distinguish a general technology description from a specified business activity. A provider may perform more than one listed service; alternatively, a discussion may involve an activity outside the listed categories. The approved source summary supports the importance of the listed functions but does not license an article to classify a real organisation without a full factual and legal assessment.

The term reporting entity also points to a governance framework rather than a simple registration label. The dossier summarises coverage of registration, governance, customer due diligence, ongoing monitoring, travel-rule controls, sanctions screening, suspicious transaction reports, recordkeeping, unhosted-wallet risk, and heightened concerns around anonymity-enhancing products. These are connected elements of an AML/CFT system. They should be understood as concepts in a regulated-service context, not as a checklist for readers to implement or a conclusion about any named entity.

For the service-provider framework in more detail, continue with FIU-IND’s VDA service-provider framework.

AML/CFT concepts in plain language

AML/CFT refers to anti-money laundering and countering the financing of terrorism. In the VDA service-provider context described by FIU-IND, the framework connects organisational governance and customer information with monitoring, screening, reporting, and records. The broad aim is not to predict wrongdoing from a single technical feature. It is to organise how an in-scope reporting entity identifies, evaluates, documents, and responds to risk within its regulatory framework.

Customer due diligence is an example of a term that needs context. At a high level, it concerns understanding a customer relationship and relevant information. Ongoing monitoring concerns continued attention to that relationship and activity rather than treating an initial check as the only moment that matters. Sanctions screening concerns checks against applicable sanctions-related information. Suspicious transaction reports are reports within the framework when the relevant standard is met; they are not synonymous with proof of wrongdoing.

The travel rule is another specialised term in the dossier’s summary. It refers here to a regulatory control associated with VDA service-provider activity. It should not be confused with the technical act of sending a blockchain transaction, nor should its mention be read as a universal instruction for every reader. The same caution applies to unhosted-wallet risk and anonymity-enhancing products: the guidelines’ inclusion of these subjects highlights risk considerations for reporting entities, not an automatic conclusion about every user, address, or product.

Plain-language reading discourages false certainty. A control may apply in a regulated setting, a risk factor may merit attention, and a report may be procedural. None alone establishes a crime, a legal finding, or a person’s or organisation’s status.

Timing, status, and source-of-truth limits

This guide is current only as of 20 September 2026. The approved dossier cites Income Tax Department VDA guidance updated on 27 May 2026 and FIU-IND VDA AML/CFT guidelines updated on 8 January 2026. Those dates describe the source materials identified by the dossier; they are not a promise that no later clarification, notification, amendment, interpretation, or implementation development exists. Regulatory information is time-sensitive, and an evergreen explainer must preserve that limitation rather than present a snapshot as permanent.

Source hierarchy also matters. The dossier permits a summary of two named official documents, not a complete corpus of legislation, notifications, forms, case law, guidance, or individual facts. This article therefore uses constrained language and does not claim to exhaust India’s framework or treat an omitted detail as irrelevant.

Readers can apply the same method when evaluating any regulation article. Ask which authority issued the document, what activity or definition it addresses, whether it is a rule, guidance, or summary, what date it carries, and what facts it does not resolve. The distinction between an enacted rule and a proposal, or between an investigation and a finding, is not editorial nicety; it changes the meaning of a claim.

How to read concrete examples without turning them into advice

Examples make technical language easier to inspect, but they must retain their limits. Take a hypothetical service that provides both conversion between fiat and VDA and safekeeping of VDA. The FIU-IND scope summary in the dossier lists both exchange-related and safekeeping or administration activities. That tells a reader why an activity-based analysis may be relevant. It does not establish the service’s legal status, registration outcome, customer process, or compliance conclusion.

Take a second hypothetical: an event record identifies an NFT, an acquisition-side amount, a transfer-side amount, and unrelated expenses. The Income Tax Department summary says NFTs are included in the VDA description and identifies acquisition cost in its high-level treatment of transfer income. The example teaches how two terms can appear in the same fact pattern. It does not compute tax, allocate costs, identify deductions, or instruct someone what to report.

Finally, a difference between a network timestamp and a provider display is a cue to examine context, not manufacture certainty. A timestamp may refer to a request, internal record, network confirmation, or display refresh. Its significance depends on facts and applicable sources beyond this article.

Frequently asked questions

Does the VDA definition mean every digital item receives the same treatment?

No. The approved public guidance describes what is included and excluded for its VDA definition, but a definition does not answer every tax, regulatory, or factual question. The relevant framework, activity, document, and date remain important.

Is FIU-IND reporting-entity scope the same as being interested in or using crypto?

No. The dossier describes reporting-entity scope around specified VDA service activities, including exchange, transfers, safekeeping or administration, and financial services connected to token issuance. This is not a universal label for every person connected with a VDA.

Can one record or timestamp settle a VDA tax or compliance question?

Not necessarily. A blockchain entry, service record, or display may each capture different parts of an event. The guide explains why timing and source context matter; it does not decide the legal or tax effect of any record.

Continue reading internally

Use the internal reading below to move from this overview to narrower, status-aware explainers:

Source note: The factual boundary for this guide is the approved research dossier, drawing on the Income Tax Department, Government of India, Taxation of Virtual Digital Asset, and the Financial Intelligence Unit – India, AML & CFT Guidelines for Reporting Entities Providing Services Related to Virtual Digital Assets. These source labels are intentionally non-clickable. The guide should be reviewed when its cited source materials or the surrounding regulatory context change.