Skip to content
Back to journal
CoinDCX27 Aug 2026

Why an Exchange Delists a Coin, and What Its Own Policy Promises You

CoinDCX's policy lists six delisting grounds, one of them a catch-all, and promises no notice. Miss the window and the forced USDT conversion is still taxed.

RudraResearch note 8 min read
An open rulebook on a desk, one clause circled in orange, a brass stamp marking a single listed line REMOVED while the rest of the page stays untouched. Headline: The Rule Was Already Written. Read it before the stamp falls.

The point

CoinDCX's own Listing/Delisting Policy names six numbered grounds for pulling a token. The sixth alone lists seventeen more, including a catch-all for 'any reason not mentioned herein.' The policy also reserves the right to delist without prior notice. Miss the announced window and the exchange converts your holding to USDT for you. It withholds 1 percent as tax deducted at source on the spot. That conversion is a taxable transfer whether you asked for it or not.

The six grounds CoinDCX's policy names for pulling a token

Read CoinDCX's Listing/Delisting Policy on 2026-08-27 and the structure is six numbered categories.

A token's own team can ask to leave. That is voluntary delisting. CoinDCX can also pull a token because a partner exchange dropped it first.

Then there is the '7M score,' the exchange's own internal scoring framework. A token has to hold at least 3.5 on the main exchange, or 2.75 on CoinDCX Pro. Fall below that for five straight days and the token becomes eligible for delisting.

Regulatory pressure counts too, covered here in is CoinDCX legal in India. So does the issuing project going bankrupt, or looking like it is about to.

The sixth category is labelled 'Other Reasons,' and it alone runs to seventeen more grounds. Among them are failing to supply information CoinDCX asks for, weak development activity, a breach of public trust, a criminal conviction, and fraud. The list continues with breaking any term in the policy, losing community confidence, liquidity problems, a bad public image, and a change in law anywhere the token trades. It also covers a breach of the Listing Guidelines themselves, a breach of the Terms of Use, and a partner exchange delisting the token. The remaining four are a new compliance requirement, the underlying blockchain breaking, an IP violation, and 'detection of other risks.'

The policy adds one more line:

CoinDCX reserves the right to Delist any listed Token or trading pair without prior notice to the Users and/or Listing Partner due to any reason as CoinDCX may deem fit.

The catch-all is broad, and CoinDCX publishes it openly. All of this sits in one dated document anyone can read. 'The exchange can delist for cause' undersells what that document says. The working model is discretion, exercised against a long published list of reasons. Several of those exist so the exchange can move fast against fraud or insolvency, without waiting for a narrower test to cover every case.

What happens once your coin is chosen

Two CoinDCX support pages, both read on 2026-08-27, describe the sequence. Before the delisting date you have two options, per what CoinDCX says you can do before a delisting.

Sell the token through whatever INR or USDT pair is still open. Or move it to CoinDCX's Web3 Wallet, if that particular token supports a Web3 transfer. A forced sale runs through the same fee structure as any other sell order, so the four costs no CoinDCX fee page shows still apply.

Do neither, and the exchange acts for you. Its own words, on what CoinDCX says happens if you do not act in time:

your tokens will be automatically converted into USDT at the prevailing market rate within 5 working days from the delisting date
the converted amount will be credited to your wallet after deducting the applicable 1% TDS

The conversion happens whether or not you were watching. CoinDCX withholds tax deducted at source on that automatic conversion, which tells you the exchange itself treats it as a real, taxed transaction.

Why the forced conversion is still a tax event

You did not choose the timing, the price, or the asset you were converted into. The tax treatment does not depend on that.

India taxes the transfer of a Virtual Digital Asset the same way whether you clicked sell yourself or an exchange's policy did it on a schedule. The 1 percent TDS on that transfer comes off at the moment of the transaction rather than at year-end. That is the mechanic CoinDCX's own copy describes. See how the 1 percent TDS actually works for the general mechanism.

Any gain is taxed at a flat 30 percent, plus a 4 percent cess on that 30, for an effective 31.2 percent. That holds regardless of how long you had held the coin before it was delisted out from under you. A loss on that same forced conversion cannot be set off against a gain anywhere else in your crypto holdings that year. Neither rule bends for the fact that you did not start the transaction.

A worked rupee example

Say you put 10,000 rupees into a token at 10 rupees a unit, so 1,000 units. It gets delisted and you miss the window. Forty-five days later CoinDCX auto-converts your 1,000 units to USDT at 13 rupees a unit. That is 13,000 rupees before anything is withheld.

TDS comes off that 13,000 straight away: 1 percent is 130 rupees, so 12,870 rupees lands in your wallet. Your gain on the position is separate: 13,000 minus the 10,000 you paid, so 3,000 rupees. Tax on that gain is 30 percent, or 900 rupees, plus 4 percent cess on the 900, or 36 rupees. Total liability is 936 rupees, which is 31.2 percent of the gain. The 130 rupees already withheld as TDS is credited against that 936 when you file. That leaves 806 rupees more owed at return time.

Run the same numbers with the price at 7 rupees a unit instead of 13. Now you have a 3,000 rupee loss. CoinDCX still withholds 1 percent TDS on the 7,000 rupee conversion value, whether you gained or lost. And that 3,000 rupee loss has nowhere to go against other crypto gains that year.

The gap between the policy and the help page

Every fact in this piece came from a page CoinDCX itself publishes and keeps current. The gap sits between the governing document and the help pages describing daily practice. A reader deciding how fast to react should know which of the two they are reading.

The policy clause that binds the relationship reserves the right to delist without prior notice. The support articles describe an announced delisting date, a window to sell or transfer before it, and five working days afterward for the automatic conversion. That is current practice, stated plainly, on a help page CoinDCX can update anytime. The document that governs what CoinDCX owes you is the policy, and the policy promises no minimum notice at all. If the practice ever changes, the policy already gives CoinDCX room to change it without saying so in advance.

The same distinction runs through who actually sets the rules governing what you hold, and whether that party can change them without telling you first.

Four questions to run against any platform, including ours

Does your exchange's delisting policy name a specific, measurable test, or is the whole thing discretionary? Does it promise a minimum notice period in writing, rather than only on a help page it can change anytime? What happens automatically if you do nothing, and is that stated plainly? Does that automatic outcome count as a taxable event?

For more depth on the same four questions, read a 5-point framework for evaluating any published methodology, built for any provider's published rules.

A Qatobit Crypto Index answers the first two questions through its own construction. Composition changes happen on a fixed monthly rebalance against a published methodology. A rebalance is a scheduled review where holdings are adjusted on a set calendar date. An asset earns its place by filling a role the thesis requires. It is trimmed or removed when it stops filling that role, on the calendar date the methodology sets. That is a structural difference in how the two things work, and it says nothing about which one performs better. Read the actual document on whatever platform holds your coins, this one included, before you need to know what it says.

Frequently asked questions

What are the six grounds in CoinDCX's delisting policy?

Voluntary delisting requested by the token's own team, and delisting because a partner exchange dropped the token first. A 7M score that stays below 3.5, or below 2.75 on CoinDCX Pro, for five straight days. Regulatory pressure, and the issuing project going bankrupt or looking close to it. The sixth is a catch-all 'other reasons' category that alone lists seventeen more grounds.

Does CoinDCX have to warn me before delisting a coin I hold?

No. Its policy states plainly that CoinDCX can delist any token or trading pair without prior notice, for any reason it decides fits. Its support pages currently describe an announced date and a window to act. That description sits on a help page CoinDCX can update anytime, separate from the policy document that governs the relationship.

What happens to my coin if I do not sell or transfer it before the delisting date?

CoinDCX converts it to USDT automatically at the prevailing market rate, within 5 working days of the delisting date. It deducts 1 percent TDS from the converted amount before crediting your wallet.

Is a forced delisting conversion taxed the same as a sale I choose myself?

Yes. Any transfer of a Virtual Digital Asset is taxed the same way in India, whether you initiated it or an exchange's policy did it automatically. That means a flat 30 percent on any gain, plus 4 percent cess, with 1 percent TDS withheld on the transaction value itself.

Can I offset a loss from a forced delisting conversion against other crypto gains?

No. India's flat tax on Virtual Digital Assets does not allow a loss on one asset to be set off against a gain on another. That holds for an asset you were forced to exit through delisting.

Crypto investments are subject to market risk. Not financial advice.

“A better allocation begins with a better explanation.”

Qatobit principle

Published construction. Fixed cadence. Versioned control.