Crypto Exchange Operations in India: Regulatory Structure and Technical Constraints

Indian crypto exchanges operate under a regulatory framework that treats digital assets as property rather than currency or securities, creating specific compliance obligations and operational constraints that differ materially from those in the US, EU, or Singapore. This article examines the technical and procedural mechanics that define how Indian exchanges structure custody, fiat settlement, taxation reporting, and user verification.

Regulatory Classification and Banking Access

Indian law does not recognize cryptocurrencies as legal tender. The Reserve Bank of India (RBI) imposed a banking ban on crypto entities in 2018, which the Supreme Court struck down in March 2020. Since then, exchanges have regained access to banking infrastructure, but no formal licensing regime exists specifically for crypto platforms. Instead, exchanges register as legal entities (typically private limited companies) and comply with anti-money laundering (AML) and know-your-customer (KYC) obligations under the Prevention of Money Laundering Act (PMLA) 2002.

This means Indian exchanges must:

• Maintain records of customer identification and transactions for five years minimum
• Report suspicious transactions to the Financial Intelligence Unit (FIU-IND)
• Implement risk based KYC procedures, including video verification for accounts above certain thresholds

Banking relationships remain discretionary. Banks can refuse service to crypto businesses, and many do. Exchanges typically maintain accounts with a small subset of private banks willing to service the industry. This concentration creates settlement risk: if a partner bank exits, the exchange must rapidly migrate fiat rails or suspend INR deposits and withdrawals.

Tax Reporting and Withholding Mechanics

Budget 2022 introduced two tax provisions that directly affect exchange architecture:

Section 115BBH: A 30 percent flat tax on income from transfer of virtual digital assets (VDAs), with no deduction for expenses except acquisition cost. No loss offsetting is permitted across transactions.

Section 194S: A 1 percent tax deducted at source (TDS) on every transaction where consideration exceeds 10,000 INR in a financial year (or 50,000 INR for specified persons).

Exchanges must calculate TDS at trade execution, deduct it from the seller’s proceeds, deposit it to the government within seven days, and issue Form 16A certificates quarterly. This creates several implementation constraints:

• The exchange must track aggregate annual transaction volume per user per financial year (April 1 to March 31) to determine when the threshold is crossed
• TDS applies to the gross transaction value, not profit. A user trading 1 lakh INR of Bitcoin for 1 lakh INR of Ether triggers 1,000 INR in TDS even if no gain occurred
• Refunds for excess TDS deducted are handled through annual income tax returns, not by the exchange

The TDS obligation applies even to peer-to-peer trades if the exchange facilitates them. Some platforms have restructured P2P modules to avoid being deemed an intermediary for TDS purposes, but regulatory clarity on this remains limited.

Custody and Settlement Models

Most Indian exchanges use omnibus hot wallet structures with cold storage for the majority of user balances. Unlike jurisdictions with specific crypto custody regulations, India has no legally mandated separation of customer and house funds, no insurance requirements, and no prescribed audit standards for reserves.

Exchanges typically implement:

• Multi signature wallets requiring two or more signatories for cold wallet withdrawals
• Daily reconciliation between database balances and onchain holdings
• Withdrawal limits tiered by KYC level, with higher limits requiring video verification or additional documentation

Because there is no regulatory requirement to prove reserves, proof of reserves attestations are voluntary. When provided, they usually consist of Merkle tree commitments showing user liabilities and wallet addresses demonstrating control of funds. Independent audits of these attestations are rare.

Fiat settlement happens through segregated bank accounts. INR deposits are credited to user accounts after confirmation from the bank, usually within a few hours for UPI or IMPS transfers. Withdrawals are processed in batches, typically two to four times daily, and settled via NEFT, RTGS, or IMPS depending on amount and user preference.

KYC Tiers and Operational Limits

Exchanges implement tiered KYC to balance onboarding friction against compliance risk. A common structure:

Tier 1: Email and phone verification. Allows trading up to 10,000 to 50,000 INR daily. No fiat withdrawal.

Tier 2: PAN card, Aadhaar, bank account verification. Unlocks full trading and fiat withdrawal up to 1 to 5 lakh INR daily.

Tier 3: Video KYC or in-person verification. Required for limits above 5 lakh INR daily or institutional accounts.

The Central Board of Direct Taxes (CBDT) mandates that exchanges collect PAN numbers for all users, as PAN is the unique taxpayer identifier used for TDS reporting. Exchanges cannot process trades for users who fail to provide PAN.

Aadhaar based e-KYC through the Unique Identification Authority of India (UIDAI) is permitted for financial service providers, but its applicability to crypto exchanges is subject to interpretation. Some platforms use Aadhaar for identity verification but do not rely solely on it for compliance purposes.

Worked Example: INR to BTC Purchase with TDS

A user deposits 100,000 INR via UPI. The exchange credits the account within 15 minutes. The user places a market order to buy Bitcoin at a price of 50,00,000 INR per BTC, receiving 0.02 BTC.

This is the user’s first transaction of the financial year. Because the transaction value is 100,000 INR, which exceeds the 10,000 INR annual threshold, the exchange deducts 1 percent TDS (1,000 INR). The user’s account is debited 101,000 INR total: 100,000 for the Bitcoin purchase and 1,000 for TDS. Since the user deposited only 100,000 INR, the order fails unless the user had a preexisting INR balance to cover the TDS.

In practice, exchanges handle this by either:

• Requiring users to maintain an INR buffer for TDS
• Adjusting the order size automatically to account for TDS
• Displaying TDS inclusive pricing at order preview

The exchange deposits the 1,000 INR TDS within seven days using challan ITNS-281 and updates the user’s Form 26AS (the consolidated tax statement) to reflect the deduction.

Common Mistakes and Misconfigurations

• Ignoring TDS thresholds across multiple exchanges: TDS applies per exchange, not per user. Trading below 10,000 INR on five different platforms does not trigger TDS on any of them, even though the aggregate exceeds the threshold.
• Assuming crypto to crypto trades avoid TDS: Section 194S applies to all VDA transfers for consideration. Swapping Bitcoin for Ether triggers TDS based on the INR equivalent value.
• Failing to preserve TDS certificates: Form 16A is required to claim credit for TDS when filing annual returns. Exchanges are required to issue it, but users must download and retain it.
• Using exchanges without PAN linkage: Trades executed before completing PAN verification may not generate valid TDS certificates, complicating tax filing.
• Overlooking bank account mismatch restrictions: Most exchanges require the linked bank account name to match the KYC name exactly. Deposits from third party accounts are rejected or frozen pending manual review.
• Assuming withdrawal reversibility: Crypto withdrawals to external wallets are irreversible. Address errors or network selection mistakes (sending ERC-20 tokens to a Bitcoin address) result in permanent loss.

What to Verify Before You Rely on This

• Confirm the current TDS rate and threshold. These are subject to change through annual budget announcements.
• Check whether the exchange has an active banking partnership. Suspend or migrate if fiat rails are disrupted.
• Verify the exchange’s proof of reserves publication schedule and methodology. Absence of recent attestations is a red flag.
• Review the exchange’s insurance coverage, if any. Most Indian platforms do not insure user funds against hacks or insolvency.
• Confirm supported withdrawal networks for each asset. Not all exchanges support all ERC-20 tokens or Layer 2 networks.
• Check the exchange’s policy on frozen or locked accounts due to suspicious activity flags. Understand the appeals process and typical resolution time.
• Verify whether the platform reports to FIU-IND and maintains PMLA compliance. Non-compliant exchanges face regulatory and banking access risks.
• Review the fee structure for TDS inclusive and exclusive scenarios. Some exchanges charge fees before TDS deduction, others after.
• Confirm the exchange’s domicile and regulatory filings. Offshore entities operating in India without local registration face enforcement risk.
• Check whether the platform supports tax reporting exports in the format required by Indian tax software or chartered accountants.

Next Steps

• Select exchanges based on banking partnerships, custody transparency, and TDS reporting reliability rather than trading fees alone.
• Maintain detailed transaction logs outside the exchange platform, including timestamps, amounts, TDS deducted, and wallet addresses for all deposits and withdrawals.
• Structure trades to minimize TDS impact, such as consolidating small trades into fewer larger transactions or using exchanges that optimize order sizing for TDS efficiency.

Category: Crypto Exchanges