India operates a bifurcated crypto market where exchanges must navigate active enforcement, indirect banking friction, and fragmented regulatory clarity. This article examines the technical and operational realities: how Indian exchanges route fiat settlement, apply tax withholding at the protocol layer, and structure liquidity to comply with TDS requirements without breaking user experience.
Fiat Settlement Architecture
Indian exchanges cannot rely on consistent banking partnerships. Most route INR deposits and withdrawals through payment aggregators or scheduled banking partners that periodically exit the relationship due to compliance concerns. The technical consequence is that exchanges build redundancy into their fiat rails.
A typical setup separates user facing deposit instructions from backend settlement. When a user initiates INR deposit, the exchange generates a unique virtual account number tied to their UID. Funds hitting that VAN trigger an API callback to credit the user balance. Withdrawals reverse the flow: user requests INR out, exchange batches requests, and submits them to the payment processor in 4 to 6 hour cycles to reduce per transaction scrutiny.
The weak link is bank account turnover. Exchanges maintain 3 to 5 active settlement accounts across different banks and PSPs. When one closes, user facing deposit instructions must update within hours. Operationally, this means exchanges cannot hardcode bank details in client apps. They fetch deposit instructions via API at request time.
Tax Withholding at Transaction Layer
India mandates 1% TDS on crypto sales. Exchanges must deduct this at trade execution and remit it to tax authorities with buyer and seller PAN details. The technical implementation happens in the matching engine.
When Alice sells 0.5 BTC to Bob at ₹25,00,000, the engine calculates TDS as ₹25,000 and debits it from Alice’s INR balance before crediting the net ₹24,75,000. The exchange tags this deduction with Alice’s PAN, trade ID, and timestamp. These records batch into challan files submitted monthly via the income tax portal.
The complication arises with users who lack verified PANs. Exchanges either block trades for unverified accounts or apply higher TDS rates as specified in fallback provisions. Some platforms implement a two tier fee structure: lower taker fees but mandatory KYC with PAN linkage to avoid the higher withholding.
This creates liquidity fragmentation. Users who cannot or will not link PANs congregate on offshore exchanges accessible via VPN, accepting higher counterparty risk to avoid the TDS and KYC burden.
Liquidity Sourcing and Crossborder Flow
Indian exchanges face thin domestic liquidity. To offer competitive spreads, they aggregate offshore orderbooks or partner with liquidity providers who inject depth. The technical mechanism varies.
Some exchanges operate as brokers: they show users a synthetic orderbook and execute offsetting trades on Binance or Bybit. User sees price X, clicks buy, exchange buys on offshore spot and delivers to user’s custodial wallet, marking up the price to cover spread and FX risk. This model avoids maintaining deep local liquidity but introduces latency and dependency on offshore API uptime.
Others use liquidity APIs from market makers. The MM commits to quote two sided spreads within a tolerance and the exchange routes trades to them via FIX or REST. Settlement happens in stablecoins to avoid INR conversion delay. The exchange then converts USDT or USDC to INR at its own FX rate, pocketing the spread.
Neither model supports true peer to peer orderbook discovery for most pairs. Only BTC/INR and ETH/INR typically have enough local volume to sustain a native CLOB. Altcoin pairs route offshore.
Custody and Withdrawal Mechanics
Indian exchanges predominantly use hot wallet, warm wallet, and cold storage tiers. Hot wallets handle immediate withdrawals up to a per user limit (commonly ₹1,00,000 to ₹5,00,000 equivalent in crypto per day). Requests above that threshold trigger manual review and cold wallet signing, adding 12 to 48 hours of delay.
Withdrawal addresses go through AML screening against chainalysis or similar services. If the destination address links to a sanctioned entity or mixing service, the exchange blocks the transaction and flags the account. Some platforms whitelist withdrawal addresses, requiring users to pre register and verify ownership via a test deposit.
Operationally, this creates friction for users moving funds to DeFi protocols or offshore exchanges. An address associated with a DeFi router may false positive as a mixer. Users then open support tickets, creating manual backlog.
Worked Example: INR Deposit to Altcoin Purchase
Priya wants to buy 10,000 MATIC. She logs into an Indian exchange, navigates to deposit INR, and receives a VAN linked to her account. She transfers ₹80,000 from her bank via IMPS. The exchange’s PSP receives the funds in 20 minutes, API callback credits her account.
Priya navigates to MATIC/INR pair. The orderbook shows a best ask of ₹8.05. She places a market buy for 10,000 MATIC. The matching engine fills at ₹8.05, totaling ₹80,500. She’s short ₹500. She cancels and adjusts to 9,900 MATIC for ₹79,695.
Trade executes. The engine deducts 1% TDS: ₹796.95. Priya’s PAN is verified, so standard rate applies. She receives 9,900 MATIC in her exchange wallet. Total deductions: ₹796.95 TDS plus ₹200 taker fee.
Priya initiates withdrawal to her MetaMask address. The exchange checks the address against its AML provider. No flags. Withdrawal processes from hot wallet in 10 minutes.
Common Mistakes and Misconfigurations
- Assuming deposit bank details remain static. Always fetch current VAN or UPI ID from the exchange dashboard rather than reusing saved instructions.
- Linking unverified or mismatched PAN. Exchanges apply punitive TDS rates or block trades. Verify PAN matches your registered name exactly.
- Ignoring withdrawal address whitelisting. Some platforms silently reject withdrawals to non whitelisted addresses, creating support delays.
- Failing to account for TDS in trade sizing. If you have ₹1,00,000 and buy at ₹1,00,000 notional, the 1% TDS leaves you short. Size trades at 99% of available balance.
- Relying on offshore price parity. Indian exchange prices can diverge 2% to 5% from global spot due to fiat conversion friction and liquidity constraints.
- Expecting instant large withdrawals. Amounts above platform specific thresholds trigger manual review. Plan 24 to 48 hour buffer for cold storage withdrawals.
What to Verify Before You Rely on This
- Current TDS rate and exemption thresholds. These may change via budget amendments or income tax circulars.
- Whether the exchange’s banking partner recently changed. Check deposit instructions each session.
- PAN verification status in your account settings. Unverified PANs may trigger higher TDS or trade blocks.
- Withdrawal limits and cold storage threshold for your KYC tier. Limits vary by platform and account verification level.
- AML screening policy. Confirm whether your destination address type (DeFi contract, offshore exchange) is permitted.
- Liquidity sourcing model. Ask support whether trades execute on a local orderbook or broker model with offshore fills.
- Fee structure interaction with TDS. Some platforms bundle TDS into fees, others separate it. Confirm how your net proceeds calculate.
- Stablecoin support. Not all Indian exchanges offer USDT or USDC rails. Verify before planning crossborder arbitrage flows.
- Regulatory status of the exchange. Monitor whether the platform faces enforcement actions or banking disruptions.
- Customer support SLA for withdrawal escalations. Know the expected resolution time if a withdrawal flags for review.
Next Steps
- Map your fiat onramp and offramp flow before depositing. Identify backup exchanges in case your primary faces banking disruption.
- Link and verify PAN immediately after account creation to avoid TDS and trade execution issues.
- Test a small withdrawal to your intended destination address type before moving significant balances, confirming it clears AML screening.
Category: Crypto Exchanges
