Koinex
Koinex was an Indian cryptocurrency exchange that let users trade digital assets in the local market before shutting down in 2019.
View original storyProduct snapshot
What it was
Koinex operated a cryptocurrency exchange for Indian users to trade digital assets.
Who it was for
Problem / value
It gave local users access to crypto trading and exchange liquidity in India.
Core workflow
Users deposited funds or assets, traded cryptocurrencies, held balances, and withdrew assets through exchange workflows.
Core dependency
Banking access, regulatory clarity, custody operations, and a credible user-exit plan.
Product form
Pricing model
Exchange fee model implied by the category; exact fee schedule and revenue are not disclosed in the reviewed public sources.
Competitors or alternatives
What happened
Summary
Koinex shut down trading services after regulatory uncertainty and banking constraints made crypto-exchange operations in India difficult.
Outcome
Koinex shut down trading services in June 2019.
Core risk
A finance product can lose its operating base when external rails or regulation change, even if users still want the core service.
Shutdown reason
Public reports cite regulatory uncertainty, banking constraints, and disruption in India’s cryptocurrency environment.
Demand signal
Koinex should not be read as a simple no-demand case. Public reports describe it as a leading Indian crypto exchange; the risk was that trading and custody workflows depended on banking access and regulatory clarity outside the product team’s control.
Distribution issue
The distribution problem was not mainly user acquisition. For an exchange, bank rails, deposits, withdrawals, compliance posture, and user trust are part of the operating channel; once those weakened, normal product demand could not keep the service stable.
Timeline
- Koinex operated as an Indian cryptocurrency exchange
- Indian crypto businesses faced banking and regulatory pressure after the 2018 RBI circular described in public reporting
- Moneycontrol reported Koinex stopped trading services at 2 pm on June 27, 2019
- Users were given a deadline to withdraw digital assets
- Public reports framed the shutdown as a consequence of regulatory uncertainty and disruption in India’s crypto market
Before you build
Why it matters
For exchanges, payment apps, lending tools, and custody-like products, banking access and regulation are not back-office details. They define whether the product can operate at all.
Primary check
Map banking, regulatory, custody, and exit-plan dependencies before building a finance product whose core workflow depends on external permission.
Checklist
- What happens if your bank account is closed?
- Can users retrieve assets without normal trading services?
- Which regulator or partner can stop the core workflow?
- Identify every bank, custodian, license, and compliance dependency
- Design a withdrawal or migration plan before launch
- Test whether partner rails survive adverse policy changes
- Prepare customer communication for service interruption
Relevant if
- You are building crypto, payments, lending, or fintech software
- Your product depends on bank accounts, licenses, custody, or platform permissions
- Users store assets or balances inside your product
Less relevant if
- Your product is informational only and does not handle funds or assets
- You already have regulated partners and tested fallback rails
Pre-build tests
- Get written confirmation from banking or regulated partners
- Run a tabletop shutdown and withdrawal exercise
- Build the first version around minimal custody and clear exit paths
Transferable lessons
- Map all external rails before launch
- Create a customer exit plan before holding assets
- Treat regulatory ambiguity as a core product risk
- Do not rely on one banking path for critical workflows
If you build this today
Before launching a finance or crypto product, define the banking fallback, regulatory decision tree, user-withdrawal plan, and partner migration path that will work if the main operating rail is interrupted.