An exchange serving Indian users discovers that a 30 percent flat tax now applies to every transaction – not just at the point of cash-out, but on each trade. A custodian holding keys for Indian residents learns that its AML obligations extend beyond the platform to the underlying beneficial owner. A DeFi protocol routing liquidity through nodes in Mumbai finds that the tax net has widened to capture non-custodial activity. India has introduced one of the world's strictest digital-asset tax regimes without creating a corresponding licensing pathway for operators.
The Indian approach to virtual digital assets rests on two pillars: a comprehensive tax framework that treats crypto as a distinct asset class subject to flat-rate taxation and capital-gains rules, and an evolving AML posture that requires registration under the Prevention of Money Laundering Act for entities facilitating exchange or transfer services. The result is a compliance burden that falls heavily on foreign platforms serving Indian users, even where those platforms hold no Indian presence. For an operator assessing market entry or managing an existing user base, the question turns on whether the tax and reporting obligations can be met without a formal licensing regime – and whether the absence of that regime leaves room for regulatory reinterpretation.
This page sets out the Indian tax treatment of virtual digital assets, the AML registration obligations for exchanges and intermediaries, and the practical compliance steps for foreign platforms. It addresses the cross-border friction that arises when a user base sits in India but the operating entity, the custody and the banking sit elsewhere. The analysis is current as of the regime's introduction; every figure, threshold and effective date below is drawn from the legislative framework as enacted, with the caveat that further rule-making and enforcement guidance remain in development.
What is a virtual digital asset under Indian law?
Indian tax law defines a virtual digital asset (VDA) as any information, code, number or token generated through cryptographic means that provides a digital representation of value and is exchangeable or transferable for consideration. The definition extends to non-fungible tokens and any other token of similar nature, as specified by the Ministry of Finance. Expressly excluded are Indian currency, foreign currency and any security or commodity as defined under existing securities or commodities legislation.
The definition is deliberately broad. It captures bitcoin, ether and stablecoins pegged to fiat or commodities, as well as NFTs minted on any chain. A token issued as part of a loyalty programme, a governance token distributed by a DAO, or a representation of intellectual property on-chain all fall within the VDA perimeter if they meet the transferability and consideration tests. The exclusion for securities means that a token classified as a security under the Securities and Exchange Board of India framework escapes the VDA tax but becomes subject to securities regulation – a separate compliance path with its own licensing and disclosure obligations.
For an operator, the classification question matters twice: once at the point of user onboarding, to determine which tax and AML rules apply, and again at the point of product design, where a structure intended to avoid securities classification may inadvertently trigger VDA treatment. The boundary between a security token and a VDA is fact-specific, turning on whether the token confers rights in an underlying enterprise or asset. In our cross-border practice, we see operators layer their token architecture to separate governance rights from transferable value precisely to manage this classification risk across multiple regimes.
How are virtual digital assets taxed in India?
India imposes a flat tax on income from the transfer of a VDA. The rate and the mechanics of collection create a compliance burden distinct from capital-gains treatment in other jurisdictions. The tax applies at the point of transfer – not merely at the point of cash-out to fiat – so a trade of bitcoin for ether, or the disposal of an NFT for stablecoins, triggers the obligation. No deduction is allowed for expenses other than the cost of acquisition, and losses from one VDA transaction cannot be set off against gains from another or carried forward to future years.
The regime also introduces a withholding obligation on the payer. Any person responsible for paying consideration for a VDA transfer must withhold tax at a specified rate before making payment. This means that an exchange facilitating a sale, a custodian settling a peer-to-peer transaction, or a DeFi protocol routing a swap may all be treated as withholding agents. The obligation extends to non-resident payers where the VDA or the consideration has a sufficient connection to India – a nexus rule that captures foreign platforms serving Indian users.
For a foreign operator, the withholding requirement is the friction point. It requires the platform to identify the Indian tax residency of each user, calculate the withholding amount on each transaction, remit the tax to the Indian authorities within the prescribed timeline, and issue a certificate to the user. The platform becomes the tax collector without the benefit of a formal licensing or registration process that might clarify its obligations. In practice, many exchanges serving India have either geo-blocked Indian users or delisted certain trading pairs to avoid the administrative cost of compliance.
What are the AML registration obligations for VDA operators?
The Prevention of Money Laundering Act applies to entities engaged in the business of exchange or transfer of virtual digital assets. These entities are classified as reporting entities and must register with the Financial Intelligence Unit – India (FIU-IND), maintain records of transactions, verify customer identities in accordance with know-your-customer norms, and file suspicious transaction reports where activity suggests money laundering or terrorist financing.
The registration process requires the entity to submit details of its business model, its directors and beneficial owners, the jurisdictions in which it operates, and the systems it has in place for AML compliance. FIU-IND reviews the application and may request further information or impose conditions on the registration. The timeline for approval varies; applications submitted in the initial registration window experienced delays as the unit processed a backlog of both domestic and foreign platforms. An entity that commences operations before registration, or continues to operate after registration is refused or withdrawn, faces penalties under the Act.
For a foreign platform, the registration obligation arises if the platform provides exchange or transfer services to users in India, regardless of where the platform is incorporated or where its servers are hosted. The test is the location of the user and the nature of the service. A custodian that merely holds keys without facilitating transfers may fall outside the reporting-entity definition, but a wallet provider that enables peer-to-peer transfers, or an exchange that lists VDA trading pairs accessible to Indian residents, will generally be caught. The practical question is whether the platform can demonstrate that it has geo-restricted Indian access – and whether that restriction is effective given the prevalence of VPN use.
Is there a dedicated crypto licence in India?
India does not currently operate a formal licensing regime for virtual digital asset service providers equivalent to the CASP authorisation under MiCA or the VASP licensing regimes in Dubai, Hong Kong or Singapore. The regulatory framework consists of the tax treatment described above, the AML registration requirement under the Prevention of Money Laundering Act, and a set of sectoral restrictions – banks and payment-system participants are discouraged from facilitating VDA transactions, though no blanket prohibition is in force as of this writing.
The absence of a licensing regime creates uncertainty. An operator serving Indian users must comply with tax withholding and AML registration but has no clear authorisation framework that defines the permitted scope of activity, the capital or reserve requirements, or the consumer-protection obligations. The Reserve Bank of India has at various points signalled concern over VDA adoption and has issued advisories to regulated entities, but it has not introduced a licensing pathway for VDA businesses. The Securities and Exchange Board of India regulates instruments classified as securities; a token that falls within that definition requires issuer registration and disclosure, but again there is no dedicated crypto-exchange licence.
For a business deciding whether to enter the Indian market, the calculation turns on whether the compliance cost of tax withholding and AML registration – without the clarity of a licence – justifies the user base. Many operators conclude that the administrative burden outweighs the opportunity, particularly where the tax treatment eliminates the arbitrage that drives retail trading volume. Others structure their operations to avoid a taxable nexus by ensuring that trades settle outside India and that custody remains offshore, though the effectiveness of this structure depends on the regulator's interpretation of "transfer" and on the enforceability of geo-blocking in practice.
What is the cross-border tax and banking friction?
The Indian VDA tax applies where the transferor is a resident or where the asset itself has a connection to India – a test that is easier to state than to apply. A foreign exchange facilitating a trade between two non-resident users, settled in a wallet hosted outside India, may still face withholding obligations if one party is an Indian resident trading while abroad. The platform must determine residency on signup and on an ongoing basis, withhold on every transaction involving that user, and remit the tax through a mechanism that requires an Indian bank account or a registered agent.
Banking presents a parallel obstacle. Indian banks, acting under Reserve Bank guidance, have historically restricted accounts for entities engaged in VDA business. A foreign platform seeking to open a rupee account to facilitate tax remittance or user deposits finds that few banks will onboard a VDA-related customer, even where the customer is compliant with AML registration. The result is that an operator must route payments through a third-party payment processor or a non-bank correspondent, adding cost and introducing a chokepoint that the regulator or the payment network can close without notice.
The interplay between tax, AML and banking creates a structural impediment to market entry. An operator that commits to full compliance – registering with FIU-IND, implementing withholding, filing returns – still cannot secure the banking rail needed to operate efficiently. In our practice, we see clients either accept a higher cost base by routing through a compliant payment partner, or conclude that the India market remains effectively closed to direct operation and that any user base must be served from an offshore hub with explicit geo-restrictions. The cross-border stack – licensing in a permissive jurisdiction, custody in a stable legal environment, banking in a crypto-friendly centre, and tax compliance managed through a local agent – becomes the model, but it leaves the operator exposed to enforcement risk if the Indian authorities take the view that the substance of the business is Indian despite the offshore form.
What are the practical compliance steps for a foreign platform?
A foreign platform assessing whether to serve Indian users, or managing an existing Indian user base, should undertake a structured compliance review covering tax, AML, banking and enforcement risk. The first step is a residency audit: determine which users are Indian residents under the Income Tax Act, which transactions involve the transfer of a VDA, and whether the platform meets the threshold for reporting-entity status under the Prevention of Money Laundering Act. A platform with a material Indian user base – measured either by number of users or by transaction volume – will generally cross the threshold; the Act does not specify a de minimis, so any regular facilitation of transfers may trigger the obligation.
Second, implement the withholding mechanism. This requires system changes to calculate the withholding amount on each transfer, collect the tax before settlement, remit the funds to the Indian tax authority within the prescribed period, and issue withholding certificates to users. The platform must obtain a tax identification number and appoint an authorized representative in India to manage filings and correspondence. The cost of this infrastructure – both the technical build and the ongoing administrative burden – is the filter that drives many platforms to exit the India market or to restrict access at the KYC stage.
Third, register with FIU-IND. Prepare the application with details of the business model, governance, AML systems and transaction monitoring. Where the platform operates across multiple jurisdictions, the application should demonstrate how the India-specific obligations integrate with the global compliance framework. FIU-IND expects evidence of AML policies tailored to the Indian context, including screening against sanctions lists relevant to India and procedures for filing suspicious transaction reports. The registration, once granted, requires annual renewal and ongoing reporting.
Fourth, address the banking friction. Identify payment partners or correspondent banks willing to handle VDA-related flows. In practice, this means working with specialized fintechs or non-bank payment institutions that have clearance from their regulators to service VDA businesses. The payment partner typically charges a premium for the risk; factor this into the unit economics of the India operation. Where banking cannot be secured, the platform must decide whether to operate without rupee on-ramps – limiting the service to users who fund their accounts through international transfers – or to withdraw from the market entirely.
Fifth, document the geo-restriction measures. If the decision is to block Indian users, implement IP blocking, device fingerprinting, and KYC checks that flag Indian residency. Maintain logs that evidence the restriction, because the enforcement question will turn on whether the platform took reasonable steps to prevent access. A half-hearted geo-block that users bypass with a VPN will not shield the platform from liability if the regulator determines that the platform knowingly served a restricted market.
What proposed legislation and regulatory signals should operators monitor?
India has at various points considered legislation to ban private cryptocurrencies, to establish a central bank digital currency, or to regulate VDAs under a dedicated framework. As of this writing, no comprehensive VDA regulation has been enacted beyond the tax and AML provisions discussed above. The government has signalled that it views VDAs as high-risk and has called for international coordination on standards, but it has stopped short of a blanket prohibition. The policy position appears to be one of containment – impose tax and AML obligations heavy enough to discourage mass adoption – rather than outright ban or full licensing.
Operators should monitor announcements from the Ministry of Finance, the Reserve Bank of India, and the Securities and Exchange Board of India. Any indication that a licensing regime is under consideration, or that the existing tax rules will be amended, changes the market-entry calculus. A licensing pathway that provides clarity on permitted activities, capital requirements and consumer protection would make compliance feasible for well-capitalized platforms; conversely, a tightening of the AML rules or an expansion of the withholding obligation to cover non-custodial activity would push more operators offshore.
The central bank digital currency project – the digital rupee – is another variable. If the Reserve Bank launches a retail CBDC and restricts private VDA usage to protect CBDC adoption, the regulatory environment will shift again. In our practice, we advise clients to structure for flexibility: avoid fixed capital commitments in India until the licensing question is settled, maintain the ability to geo-block or pivot quickly, and ensure that the cross-border operating model does not depend on long-term access to Indian banking rails.
How OBOLUS advises on India VDA compliance
OBOLUS acts for exchanges, custodians and token issuers assessing the Indian market or managing compliance for an existing user base. We map the tax withholding, AML registration and banking stack as a single cross-border matter, not three disconnected workstreams. Where a platform operates across multiple jurisdictions, we integrate the India obligations into the global licensing structure, identifying the entity that will hold the FIU-IND registration, the flow of funds that will support tax remittance, and the contractual arrangements with payment partners.
A recent engagement involved a stablecoin issuer with a significant Indian holder base. The issuer sat offshore; the tokens circulated globally; a portion of redemptions came from Indian users. The question was whether the issuer was a reporting entity required to register with FIU-IND, and whether redemptions triggered withholding obligations. We analysed the transfer mechanics – the issuer did not facilitate peer-to-peer transfers but did redeem tokens for fiat – and concluded that the redemption service likely constituted "exchange" under the Act. The issuer registered, appointed a local agent to manage filings, and implemented a withholding mechanism for Indian redemptions. The compliance cost was material, but the registration provided a defensible position and preserved access to a user base the issuer was unwilling to block.
For a platform at the market-entry stage, the assessment turns on user economics. If the India market represents a small share of projected revenue and the compliance cost – tax withholding infrastructure, FIU-IND registration, payment-partner fees – exceeds the margin, the rational decision is to geo-block at launch and revisit if the regulatory landscape clarifies. If the market is strategic and the platform can absorb the cost, the path is registration and full compliance, with contingency plans for a regulatory shift that makes continued operation unviable. We deliver that analysis as a scoped memo – the market-entry options, the cost model, the enforcement risks – before the platform commits capital or commences operations.
To map the India compliance and tax position for your digital-asset business, contact OBOLUS at info@oboluslaw.com or through our contact page.
What are the common mistakes in India VDA structuring?
The first mistake is assuming that offshore incorporation alone shields the platform from Indian tax and AML obligations. The nexus rules look through entity structure to the location of users and the substance of the service. A platform that is incorporated in a favourable jurisdiction but actively markets to Indian users, processes rupee deposits, or facilitates trades among Indian residents will be treated as having an Indian nexus. The result is that the platform faces withholding and registration obligations without the benefit of a licensing regime that might limit liability or provide safe-harbour defences.
The second mistake is treating the FIU-IND registration as optional or deferrable. Some platforms take the view that they will wait for enforcement action before registering, gambling that the regulator lacks the resources to pursue foreign operators. This is a high-risk strategy: the penalties for operating without registration include fines and, in cases involving money laundering, criminal liability for directors. More practically, a platform that registers late may find that Indian banks and payment partners refuse to work with an entity that has a history of non-compliance, foreclosing the banking rail even after registration is secured.
The third mistake is under-investing in the technical infrastructure for withholding. The Indian tax rules require withholding at the point of transfer, which means the platform must intercept the transaction, calculate the tax in real time, collect it before settlement, and remit it on a prescribed schedule. A manual process or a bolt-on reporting tool will not suffice at scale. Platforms that launch with inadequate systems find that they cannot meet the remittance deadlines, triggering interest and penalties, or that they over-withhold and must process refund claims from users – an administrative cost that compounds the original compliance burden.
The fourth mistake is failing to document geo-restrictions. A platform that decides not to serve India must implement and log the measures it takes to block access. A terms-of-service clause stating that Indian residents are prohibited is not enough; the platform must show that it uses IP filtering, device checks, and KYC verification to enforce the restriction. In a dispute, the regulator will assess whether the restriction was genuine or merely cosmetic. A platform that collects rupee deposits, lists INR trading pairs, or employs India-focused marketing after stating that it blocks Indian users will find that the restriction is disregarded and that the platform is treated as having served the market knowingly.
What is the decision framework for India market entry?
An operator considering the Indian market should assess four variables: the projected user base and revenue, the compliance cost, the enforcement risk, and the availability of banking. If the user base is large and the platform can achieve unit economics that absorb the withholding and registration costs, the market may be viable despite the friction. If the projected revenue is modest and the compliance cost is high, the rational decision is to block Indian users at launch and allocate the compliance budget to jurisdictions with clearer licensing regimes.
The enforcement-risk assessment turns on the platform's visibility and the regulator's priorities. A high-volume exchange with a public brand and a large Indian user base will attract regulatory attention quickly; a smaller platform with a niche product may operate below the enforcement threshold for a period, though this is a timing bet rather than a legal defence. In our practice, we counsel clients to assume that any deliberate non-compliance – failing to register when the obligation is clear, or withholding inadequately – will eventually be detected, and to structure for a defensible compliance posture from day one.
Banking availability is the practical constraint. If the platform cannot secure a payment partner willing to handle VDA-related flows, the India operation cannot function regardless of the compliance posture. Before committing to registration and tax withholding, confirm that a banking or payment rail exists. The confirmation process typically involves parallel conversations with two or three payment institutions, each assessing the platform's AML systems, transaction volumes, and regulatory history. A platform with a clean record and robust controls will have options; a platform with prior enforcement actions or weak KYC will struggle to find a partner at any price.
The decision framework is iterative. An operator may initially block Indian users, then revisit the market if the regulatory environment improves or if the user demand justifies the compliance cost. Conversely, an operator may launch with full compliance, then exit if the cost base proves unsustainable or if the Reserve Bank tightens restrictions on VDA-related banking. The key is to structure for reversibility: avoid long-term commitments to Indian infrastructure, maintain the technical capability to geo-block quickly, and ensure that contracts with payment partners and local agents can be terminated without penalties if the market becomes unviable.
Related at OBOLUS
- Licensing & Registration for Digital-Asset Businesses – the licensing stack across operating, custody and payment layers
- Crypto Regulation and Licensing in the European Union (MiCA) – the CASP authorisation pathway and passporting across the EU/EEA
- Smart Contract Dispute Resolution in Poland – enforceability and recovery in a civil-law jurisdiction
FAQ
How long does a crypto licence take to obtain?
India does not operate a dedicated licensing regime for virtual digital asset service providers; the compliance framework consists of AML registration with the Financial Intelligence Unit – India and tax withholding under the Income Tax Act. FIU-IND registration timelines vary depending on application volume and the completeness of the submission. In the initial registration window, processing took several months as the unit managed a backlog. Operators should allow a minimum of three to four months from submission to approval, with the understanding that the timeline may extend if the unit requests further information or imposes conditions on the registration. The absence of a licensing regime means that approval does not confer authorization to operate; it is a compliance registration, not a permit.
Which jurisdiction suits my crypto business?
The choice of jurisdiction depends on the operator's business model, target markets and the need for passporting or cross-border recognition. For a platform serving European users, a CASP authorisation under MiCA in a member state such as Lithuania or Malta provides EU-wide passporting. For a platform focused on institutional clients in the Middle East, Dubai under VARA or Abu Dhabi under the ADGM regime offers a stable regulatory framework with proximity to banking and custody infrastructure. For a platform targeting Asia-Pacific retail, Singapore or Hong Kong provides regulatory clarity and access to deep liquidity pools. India itself is not typically chosen as a primary licensing jurisdiction due to the absence of a formal licence and the banking restrictions; operators serving Indian users generally structure the entity offshore and manage India-specific obligations – tax withholding and FIU-IND registration – through a local agent.
Do I need a separate custody licence?
Whether custody requires a separate licence depends on the jurisdiction and on the structure of the custody service. In regimes that treat custody as a distinct regulated activity – such as MiCA in the EU, VARA in Dubai, or the MAS framework in Singapore – a platform providing custody to third parties generally requires a custody-specific authorisation or must include custody in the scope of its primary licence. In India, there is no standalone custody licence; custody falls within the broader FIU-IND registration requirement if the custodian facilitates transfers or exchanges. A custodian that merely holds keys without enabling transactions may not meet the reporting-entity threshold, but the line is not bright. For multi-jurisdiction operations, the licensing stack often requires custody authorisation in the hub jurisdiction, with reliance or notification arrangements in secondary markets. The practical approach is to map the custody function to the applicable regulatory perimeter in each market before commencing operations.
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, banking and tax stack across operating, custody and payment layers before you commit, and we structure licensing, banking and tax as one mandate rather than three disconnected workstreams. Our clients include platforms assessing market entry into complex regimes, operators managing compliance for multi-jurisdiction user bases, and businesses requiring rapid coordination with allied counsel where enforcement or recovery demands cross-border action. To discuss your India compliance position or your broader licensing structure, contact info@oboluslaw.com.
By Aisha Tan, Licensing & Jurisdictions Analyst – specialising in the Asia-Pacific licensing landscape and the compliance pathways for platforms serving users across restrictive and permissive regimes.
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.