India's crypto tax: A legal shield for token launchpads?

India’s crypto tax: A legal shield for token launchpads?

None of that converts an IDO into an approved financial product.

That is the compliance fiction I keep seeing dressed up as strategy: “India taxes crypto, therefore India has regulated it.” No. India has built mechanisms to identify activity, collect tax, and trace suspicious flows. That is not the same thing as licensing a public token sale. It is not a securities-law exemption. It is not a safe harbor for a launchpad that lets retail users wire money into a token with a 95% FDV discount to the next funding round.

I ran the logic from the participant’s side, not the launchpad’s marketing deck. The result is blunt: crypto regulation in India is becoming more visible, more data-heavy, and more enforceable at the activity level. But token issuers and launchpads still sit in a legal gap. The tax bill arrives. The AML obligations arrive. Clear product authorization does not.

Tax collection is not regulatory approval. A 30% rate does not turn a token sale into a licensed market.

The myth of the tax-based safe harbor

The phrase “legalized crypto” has done a lot of damage in India. It usually appears in a pitch deck right before a founder explains why Indian user acquisition will be their next “revolutionary” growth engine. Then comes the supporting argument: Virtual Digital Assets are defined for tax purposes, VDA income is taxed, exchanges operate, therefore an IDO can accept Indian participants with manageable risk.

That chain breaks at every important link.

India’s tax framework defines a broad category of Virtual Digital Assets. It covers cryptographically generated tokens, notified NFTs, and crypto-assets relying on distributed-ledger technology or similar technology. But a tax definition is not a product classification. It tells the tax authority what it can tax. It does not tell a launchpad whether its token is a security, an investment product, a consumer-risk product, a foreign-exchange concern, or something that triggers another body of law.

A token does not become harmless because someone labelled it “utility.” That word has become crypto’s cheapest legal costume. A governance token with no current use, a high FDV, thin liquidity, a twelve-month VC cliff, and a marketing campaign built around future appreciation is not transformed by putting “utility” on page 18 of a litepaper.

Nor does FIU-IND registration cleanse the product itself. Registration is a prerequisite for covered VDA service activity under India’s anti-money-laundering regime. It means a business must perform customer due diligence, retain records, maintain internal controls, train staff, and report suspicious transactions. That is compliance infrastructure. It is not a merit badge issued to a token issuer.

The distinction matters because launchpads distribute risk asymmetrically. Retail gets TGE volatility, fragmented liquidity, and tax friction. Seed funds get low entry prices, vesting protection, side-letter rights, and often an exit path through public-market demand. A launchpad that says “we are compliant in India” while refusing to disclose allocation concentration and unlock schedules is not being conservative. It is using compliance vocabulary as camouflage.

Here is the split investors need to keep in their heads:

Follow the money, not the vocabulary. If a launchpad earns fees from token-sale execution, custody, VDA transfers, or financial services linked to an issuer’s offer and sale, its exposure is not reduced because it calls itself a decentralized interface. The actual service flow matters.

The 30% VDA tax is harsh. It is not a licensing regime.

India’s VDA tax rules are unusually punitive for active token-market participants. Income from the transfer of a VDA is taxed at 30%, plus applicable surcharge and cess. Only the cost of acquisition is allowed as a deduction. Other expenditures are not deductible. Losses cannot be set off against other income, and VDA-transfer losses cannot be carried forward.

For an IDO participant, that means the mechanics can become ugly very quickly.

Suppose a buyer receives an allocation, later sells one token position at a profit, and exits another at a loss. The profitable disposal can generate tax exposure. The loss position does not necessarily soften that result. Fees, gas, research costs, launchpad charges, and the usual debris of participating in an early-stage sale do not simply reduce taxable income under the VDA rule.

That is not merely an investor inconvenience. It changes the launchpad’s market structure.

A launchpad that promotes frequent claim-and-sell behavior to Indian users may be pushing them into a tax profile that bears little resemblance to the cheerful P&L shown in a token-sale calculator. The dashboard says gross gain. The tax framework looks at transfer income under a constrained deduction regime. Those are very different pictures.

Then comes Section 194S. For qualifying payments to Indian residents for the transfer of VDAs, the rule imposes 1% tax deducted at source. The published thresholds are INR 50,000 for certain individual or HUF payers meeting specified conditions, and INR 10,000 for other payers. Payments to non-residents fall under a different provision, Section 195.

The trap is obvious: founders and users want a universal answer to whether every primary token allocation is automatically a taxable transfer or subject to TDS. There is no responsible universal answer. The result can depend on the deal architecture, consideration, timing, residency, intermediary role, and who is legally paying whom.

That uncertainty does not give a launchpad permission to ignore the issue. It means the platform has to map the cash and token flows before opening access.

I would expect a serious India-facing launchpad to be able to answer, in plain language:

1. Who contracts with the buyer? The issuer, a foundation, a Cayman entity, an aggregator, or the launchpad itself? If the answer is buried in an unsigned terms page, the risk has not been managed.

2. Who receives the purchase consideration? The wallet address is not enough. The legal recipient, payment path, and settlement mechanics determine where withholding and reporting questions start.

3. What exactly is being delivered at allocation? A transferable token, a claim right, a SAFT-like contractual entitlement, or a locked allocation with future conditions? These are not interchangeable for tax analysis.

4. Who controls the unlock and distribution contract? If the launchpad or its affiliate administers the asset flow, it may have a harder time pretending it is merely a neutral software layer.

5. What records does the user receive? A transaction hash is not a tax statement. Investors need dates, quantities, rupee values where relevant, fees, counterparties where available, and a clean record of vesting and claims.

A launchpad that cannot produce this operational map is not “borderless.” It is just undocumented.

FIU-IND supervision follows the activity, not the incorporation certificate

The March 2023 anti-money-laundering notification pulled several VDA-related activities into the PMLA perimeter when they are conducted for or on behalf of another person in the course of business. The list matters for launchpads:

• Exchange between VDA and fiat currencies.
• Exchange between one VDA and another.
• Transfer of VDAs.
• Safekeeping or administration of VDAs or instruments enabling control over VDAs.
• Participation in, or provision of, financial services related to an issuer’s offer and sale of a VDA.

That last category should make every token-sale operator sit up. It is not obscure wording. It directly reaches toward the machinery around an issuer’s offer and sale.

FIU-IND has stated that relevant VDA service providers must register as reporting entities and meet PMLA obligations. The framework includes customer due diligence, suspicious-transaction reporting, recordkeeping, employee training, and internal controls. Failure to register is non-compliance and may draw action under the applicable enforcement provisions.

The Ministry of Finance has also made the key point that offshore teams prefer to ignore: these obligations are activity-based, not dependent on physical presence in India.

So no, putting a foundation in the British Virgin Islands, hosting a front end elsewhere, and using a non-custodial wallet flow does not automatically remove Indian exposure where services are being offered to Indian users. “Decentralized” is a technical description. It is not a magic anti-jurisdiction field.

This is where I become especially skeptical of launchpads that boast about sybil resistance while treating identity verification as an optional inconvenience. Sybil resistance protects allocation mechanics. AML verification addresses a different problem: identifying customers, beneficial owners where relevant, suspicious patterns, sanctions concerns, and transaction trails. One does not substitute for the other.

A credible operating model separates them:

The practical question is not whether a launchpad has a KYC widget. Anyone can rent one. The question is whether the compliance process connects to the actual token-sale mechanics: wallet ownership, beneficial ownership, restricted jurisdictions, source-of-funds escalation, rejected-user handling, suspicious-activity workflow, and record retrieval after a dispute.

If the platform’s identity vendor collects a passport but the allocation smart contract can be transferred to an unverified wallet before TGE, the system is ornamental. If the issuer can manually whitelist wallets outside the documented process, the controls are porous. If the platform cannot explain who files a suspicious-transaction report and under what escalation standard, then “FIU-ready” is just another phrase engineered to impress people who do not read operating manuals.

Reporting is turning token launches into data liabilities

India’s reporting direction is clear even where operational details remain unfinished.

Section 285BAA, introduced by the Finance Act 2025 and effective from April 1, 2026, requires prescribed reporting entities to furnish information about crypto-asset transactions. The provision also allows for rules involving registration, retention of information, and due diligence procedures to identify crypto-asset users or owners. A discovered inaccuracy in a submitted statement must be corrected within 10 days.

Ten days is not a casual deadline when your data is split across a KYC provider, an on-chain indexer, an allocation database, a multisig operator, and a third-party market maker. This is the part founders miss while obsessing over tokenomics visuals.

A launchpad’s reporting stack needs reconciliation. Not vibes. Reconciliation.

At minimum, the platform should be able to reconcile:

• the verified customer identity with the wallet used for participation;
• the source transaction and the allocation entitlement;
• the token amount committed, allocated, refunded, vested, claimed, and transferred;
• the issuer-side sale ledger with smart-contract events;
• jurisdiction flags and restriction decisions;
• corrections to previously recorded customer or transaction data.

The five-year retention rules under PMLA make this more than a temporary launch exercise. Transaction records must generally be retained for five years from the transaction date. Client and beneficial-owner identity records, account files, and business correspondence must generally remain available for five years after the business relationship ends or the account closes, whichever occurs later.

That changes the cost structure of operating a serious launchpad. You are not just building liquidity bootstrapping contracts and a glossy allocation page. You are building a data-retention and retrieval machine that must survive team turnover, vendor churn, wallet migrations, smart-contract upgrades, and a regulator asking questions years after the token’s initial hype cycle expired.

The sloppy operators will treat this as an annoyance. The competent ones will treat it as a core product requirement.

A launchpad that cannot reconstruct a sale five years later did not build compliance. It built a temporary front end.

One small but revealing test: ask a launchpad how it handles a corrected user record after a token claim has already occurred. If the answer is a support-ticket shrug, do not assume they can handle formal reporting corrections on a 10-day clock.

And while we are discussing information quality: a compliance hub that mixes jurisdiction guidance with links to unrelated material, such as Premier League transfer analysis, is telling you something about its editorial discipline. Not every bad signal is on-chain.

The RBI point is routinely abused

The Reserve Bank of India’s April 2018 banking restriction on virtual currencies was set aside by the Supreme Court on March 4, 2020. Crypto promoters often stop the story there. They should not.

The invalidation of that banking restriction was not an approval of ICOs, IDOs, or retail token offerings. RBI-regulated entities still need to perform KYC, AML, and counter-terrorist-financing due diligence. They must also comply with FEMA requirements governing overseas remittances.

This matters for token launches because an Indian resident participating in an offshore sale may face more than a token-allocation question. Payment routing, outward remittance treatment, banking controls, and the facts surrounding the counterparty can all matter. A launchpad’s cheerful “international users welcome” banner does not resolve any of that.

Do not confuse the absence of a blanket banking prohibition with a positive regulatory endorsement. Those are opposite legal concepts.

The same caution applies to imported legal language. I see people borrow U.S. securities terminology, mention SEC actions, then declare that an Indian token sale is safe because it uses an accredited-investor screen or a utility-token disclaimer. That is legal cosplay. U.S. categories do not automatically decide Indian treatment, and India’s accredited-investor framework is not a general crypto-sale exemption.

What a launchpad can honestly say—and what it cannot

There is a narrow, defensible compliance message for a platform serving Indian users. It is not glamorous, which is probably why it is rare.

A launchpad may be able to say that it applies jurisdiction controls, screens users, conducts customer due diligence where required, retains records, maintains an AML program, considers tax and withholding flows, and responds to applicable reporting obligations. That is operational compliance language. It describes what the platform does.

It should not say or imply any of the following:

• “India has approved this IDO because crypto is taxed.”
• “FIU-IND registration means the launch is legal.”
• “Utility token status removes all regulatory risk.”
• “Offshore incorporation prevents Indian compliance obligations.”
• “KYC means Indian retail users are protected.”
• “No TDS applies” without a fact-specific analysis of the payment and transfer structure.
• “The RBI allows token sales” because the old banking restriction was struck down.

The marketing distinction is not academic. It goes directly to investor harm.

A retail buyer who hears “regulated” may assume there is a review of disclosures, use of proceeds, issuer solvency, vesting integrity, market-manipulation controls, custody arrangements, or recourse after loss. The available framework does not produce that package merely because a platform collects PAN details and deducts TDS.

The Ministry of Finance has itself warned that crypto products and NFTs remain unregulated, may be highly risky, and may offer no regulatory recourse for losses. That is the sentence token launchpads would rather keep off the landing page.

The real compliance test: can the platform survive its own paper trail?

My position is uncomplicated. India is not a compliance-free zone for token launches. It is becoming a jurisdiction where sloppy operators create a more visible trail of their own failures.

Tax rules can create reporting and withholding pressure. FIU-IND supervision can impose AML obligations on covered service activity. Recordkeeping rules can preserve evidence. Transaction-reporting provisions can make that evidence easier for authorities to demand and compare.

But none of this fills the central void: there is no dedicated Indian safe harbor, license, prospectus regime, or statutory exemption specifically built for ICOs, IDOs, public token sales, or launchpads.

That void should not be mistaken for freedom. It is uncertainty, and uncertainty has a cost. For founders, it means designing a launch with restrictions, documentation, audit trails, and enough liquidity discipline to withstand scrutiny. For investors, it means refusing to treat a tax deduction or a KYC badge as proof that the deal is legitimate.

The cold conclusion is this: India’s crypto tax regime is a collection mechanism. FIU-IND registration is an AML obligation. Neither is a legal shield.

If a launchpad insists otherwise, do not debate its slogans. Ask for the allocation ledger, the vesting schedule, the counterparty map, the KYC escalation policy, the reporting workflow, and the exact legal basis for accepting Indian users. Then follow the money.

That is where the truth usually survives.