India Adds Crypto Transactions to Its Reporting Regime

If you signed up at an Indian crypto exchange this week and got hit with extra questions about your tax residency and a taxpayer ID, that wasn’t a glitch. It’s the new normal.

India just pulled crypto transactions into a formal reporting net. The compliance people have been waiting for this. Everyone else is about to feel it in onboarding flows and annual statements.

The kicker: from April 1, 2027, India plans to start sharing cross‑border crypto data automatically with other jurisdictions under the OECD’s crypto standard. That changes the privacy calculus for anyone trying to keep trading footprints off the grid.

On July 24, 2026, the Central Board of Direct Taxes (CBDT) dropped a 198‑page Guidance Note spelling out how “Reporting Crypto‑Asset Service Providers” (RCASPs) must capture and report crypto transaction data to the Income Tax Department. It plugs directly into Section 509 of the Income‑tax Act, 2025 and its implementing Rules 241–244, and it introduces a new reporting form: Form 167. That’s the operational backbone exchanges and other platforms will now have to use for annual filings. A2Z Taxcorp LLP; Business Standard.

India isn’t banning crypto; it’s hard‑wiring it into a tax and information system that mirrors traditional finance, with cross‑border data pipes built in from the start.

Practically, RCASPs must collect users’ tax‑residency information and taxpayer‑identification details, maintain records, and furnish annual reports of specified crypto transactions. The guidance also sets the stage for India to participate in the OECD Crypto‑Asset Reporting Framework (CARF) and to begin automatic exchange of cross‑border crypto data on April 1, 2027. The Economic Times; Informist Media.

Inside the new rules: Section 509, Rules 241–244, and Form 167

What actually changed

The Guidance Note operationalizes Section 509 of the Income‑tax Act, 2025 and the related Rules 241–244. It doesn’t invent the policy; it tells platforms how to comply. Central to that is Form 167, the template for furnishing crypto‑transaction information to the tax authority. Think of it like the crypto version of a traditional financial information return. Business Standard.

What data RCASPs must collect

Per the CBDT guidance, RCASPs are expected to collect and validate:

• User tax residency (country/territory)
• Taxpayer identification details (such as a local TIN or equivalent)
• Transaction‑level information for specified crypto events

The record‑keeping duty sits with the platform, not the user. Annual reports then flow to the Income Tax Department. The Economic Times.

Area Before the guidance With the new framework Legal anchor High‑level provisions; patchy interpretation Section 509 + Rules 241–244 clarified by CBDT Guidance Note Reporting form No standardized crypto return Form 167 prescribed for crypto‑transaction reporting User data Basic KYC per exchange policy Mandatory tax residency and TIN collection for reportable users Cross‑border Ad‑hoc information exchange OECD CARF alignment; automatic exchange from Apr 1, 2027

Who must report: RCASPs in plain terms

Typical entities covered

The guidance uses the term Reporting Crypto‑Asset Service Providers. In everyday terms, think centralized exchanges dealing with Indian users, broker‑dealers offering crypto, certain wallet or custody providers that intermediate transactions, and perhaps marketplace operators. If you touch user orders, pricing, custody, or settlement at scale, assume you’re in the blast radius until counsel tells you otherwise. A2Z Taxcorp LLP.

Edge cases to watch

Decentralized protocols, non‑custodial wallets, and pure software providers may argue they don’t qualify, but that’s where interpretive risk lives. The more a service facilitates a transaction and holds user info, the easier it is for it to be deemed an RCASP.

How reporting will work: data flows and timelines

The operational loop RCASPs will run

1. Collect user tax‑residency and TIN during onboarding or refresh existing users’ records.
2. Classify transactions that meet the “specified” criteria under the rules.
3. Structure the data according to the fields and logic of Form 167.
4. Maintain audit‑ready records across the year.
5. Furnish the annual report to the Income Tax Department within the prescribed window.

Dates worth pinning on your wall

Milestone Date What it means CBDT issues 198‑page Guidance Note July 24, 2026 Operational playbook for RCASPs released Public comments on draft guidance Until Aug 17, 2026 (reported) Stakeholders can flag implementation snags Form 167 framework live Following Guidance Note Reporting templates and processes kick in Automatic cross‑border data exchange under CARF From Apr 1, 2027 India begins sharing crypto‑transaction data with partner jurisdictions

Sources: A2Z Taxcorp LLP; Ricago; Informist Media.

The cross‑border shift: India signs on to OECD CARF

Why CARF matters

OECD’s Crypto‑Asset Reporting Framework is the global template many tax authorities are adopting to curb under‑reporting and cross‑border evasion. India’s Guidance Note explicitly aligns with CARF and states the country will participate in the automatic exchange of crypto data from April 1, 2027. That means an Indian resident trading on an offshore exchange that’s also in the CARF club may find their activity mirrored back to India via data pipes. Informist Media.

What users should expect

More jurisdictional visibility. Less room for arbitrage based on “they’ll never know.” Also, more paperwork: residency self‑certifications, TIN declarations, and occasional re‑verification if your status changes.

What this means for Indian users and global platforms

For Indian residents

Expect extra prompts on exchanges asking for tax residency and your taxpayer number. Annual statements may look more like brokerage composites, with standardized fields to help the platform complete Form 167. If you have accounts abroad, assume those platforms could eventually feed data into India through CARF connections. None of this is tax advice, but it’s common sense to keep clean records and reconcile your trades.

For global exchanges and service providers

If you serve Indian users, geofencing or not, the safer assumption is you’ll need an India‑ready reporting process. That means mapping your data to Form 167, adjusting KYC to capture tax‑residency and TIN details up front, and preparing for annual filings. The CBDT guidance is long for a reason: it expects robust, audit‑friendly systems. The Economic Times.

Header/cover image used with the A2Z Taxcorp story for CBDT’s ‘Guidance Note on Crypto‑Asset Reporting Obligations’ — useful as a visual pointer to the official guidance document (PDF) and its publication. — Source: A2Z Taxcorp LLP

Implementation curve: consultation, budgets, and a moving target

The consultation window

The CBDT and Ministry allowed public comments on the draft guidance, with a reported deadline of August 17, 2026. That’s not just a courtesy. It’s a chance for exchanges, custodians, and compliance vendors to flag things like conflicting data definitions, over‑broad user scopes, or unrealistic deadlines. Ricago.

Budgeting for compliance

If you’re a platform operator, assume you’ll need engineering cycles to add fields, new data validations, and reporting pipelines. Legal and tax will need bandwidth to interpret edge cases. Support teams will field “why are you asking for my TIN?” tickets. It’s a whole‑of‑company shift, even if the surface area looks like two extra onboarding questions.

Expect a few revisions

Guidance evolves. The first year usually surfaces mismatches between what’s written and what’s technically possible. That’s fine. Better to implement early with a clear paper trail than wait for the perfect spec that never arrives.

Risks & What Could Go Wrong

• Data accuracy: Bad residency or TIN data cascades into incorrect filings and user friction later.
• Privacy and security: Centralized storage of sensitive IDs increases breach exposure; encryption and access controls must level up.
• Scope creep: Over‑broad interpretations could pull in tools and protocols that don’t actually intermediate transactions.
• Regulatory divergence: If CARF timelines or definitions differ across countries, multi‑jurisdiction platforms face conflicting obligations.
• Operational load: Smaller exchanges may struggle with the cost and speed of building Form 167 reporting.
• User experience drag: More KYC steps could push some users off compliant venues and into riskier gray markets.

The biggest near‑term risk isn’t the rule itself; it’s rushed, error‑prone implementation that invites penalties and erodes user trust.

If you want steady, plain‑English updates as this framework settles, we cover the policy beats and on‑chain fallout at Crypto Daily.

Frequently Asked Questions

What is Form 167 and why is everyone talking about it?

Form 167 is the standardized return RCASPs will use to furnish information on specified crypto transactions to India’s Income Tax Department. It’s the compliance template introduced by the CBDT to turn policy into an annual reporting workflow. Business Standard.

Who exactly counts as a Reporting Crypto‑Asset Service Provider (RCASP)?

Think centralized exchanges and other intermediaries that facilitate crypto transactions for users and hold relevant data. The exact boundary can get nuanced, but if a business helps users trade, custodies assets, or settles orders, it should assume RCASP responsibilities until clarified. A2Z Taxcorp LLP.

What user information will exchanges now request?

Platforms will ask for your tax residency and a taxpayer identification number, and they’ll keep transaction‑level records for reporting. This aligns with the CBDT guidance and the broader OECD CARF model. The Economic Times.

When does cross‑border crypto data sharing begin for India?

According to the guidance, India intends to participate in the automatic exchange of cross‑border crypto transaction data starting April 1, 2027, under the OECD’s CARF system. Informist Media.

Is this the same as taxing crypto at new rates?

No. This development is about reporting and information exchange, not a new tax rate. It sits alongside India’s existing tax framework; the guidance focuses on who must report what, and how.

Can decentralized protocols or self‑custody users ignore this?

If there’s no intermediary that meets RCASP criteria and no custodial relationship, reporting obligations may not apply in the same way. But once a platform intermediates or holds user data, reporting can kick in. When in doubt, platforms should seek legal advice; users should keep complete records.

How can platforms prepare without over‑collecting user data?

Collect only what the guidance requires (residency, TIN, transaction details), implement strong data‑minimization and access controls, and document your rationale. Expect audits to value process discipline as much as raw data.

Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.