On July 8, the Reserve Bank of India told banks and financial institutions to stay out of crypto entirely. The central bank cited tax evasion, financial stability, and consumer protection. Reuters reported the statement, and multiple outlets carried it.
The RBI has never welcomed digital assets. This latest instruction, though, is specific enough to change how institutions should read the market. There is no license for crypto custody in India. There is no procedure for a bank to hold digital assets compliantly. There is no regulatory language that would let a fund manager document source of funds, custody chain, or settlement finality to an auditor or trustee. The market is not merely difficult to enter. It is structurally closed.
This is what compliance officers now call a zero-path environment. The term matters because it describes a different condition from strict regulation or heavy licensing requirements. In a strict jurisdiction, a compliance team can build a checklist, file applications, and produce documentation. In a zero-path jurisdiction, there is no checklist. The activity cannot be made legal, so institutional capital that must answer to multiple regulators cannot touch it.
A fund allocator evaluating two markets might assume the relevant question is how permissive each one is. The more useful question is whether the jurisdiction offers explainable channels. An institution needs to show its auditors and risk committees where client money originated, how it was held, and how it was settled. These requirements do not relax when retail demand is loud or trading volume is high. They become harder to meet.
India's tax department reportedly found that fewer than 25% of the 645,000 individuals who made crypto transactions filed them on tax returns. That is not a rounding error. It suggests the existing market was built around the absence of visibility, exactly the condition the RBI now wants to lock in. For an institution, this means India's trading volume is not a measure of future opportunity. It is a measure of activity that shrinks when KYC and tax transparency apply.
Consider a compliance officer at a global asset manager who must prepare a quarterly board memo on emerging-market digital asset exposure. She can document her firm's Hong Kong licensed VASP status, its custody insurance, its disclosure filings. For India, she has no comparable documentation to present. The board does not need to debate whether India is "crypto-friendly." The absence of any compliance architecture settles the question.
Hong Kong offers the clearest contrast. Its Securities and Futures Commission licenses virtual asset service providers under explicit custody standards, insurance requirements, and disclosure rules. The process is expensive and operationally demanding. Some applicants have spent months restructuring to qualify. But the result is a documented, auditable channel. When Hong Kong later cleaned up gray-zone cross-border account access, the value did not vanish. It moved to firms that could translate demand into compliant infrastructure. India has built nothing equivalent. Its prohibition applies to all institutional participation, with no distinction between retail speculation and cross-border settlement use cases.
The RBI's position is unlikely to change soon. The central bank frames digital assets as systemic risks, not as innovations to be managed through controlled integration. This places India in a small group of jurisdictions that have chosen exclusion over channel construction.
Three developments are worth tracking.
First, whether India's Ministry of Finance, which has been more open to digital asset discussion, can negotiate any carve-out with the RBI. A ministry initiative without central bank support would still leave institutions without a compliance path, but it would show where institutional pressure is directed.
Second, how competing emerging markets position themselves. Jurisdictions with licensing frameworks that can demonstrate audit trails, tax-reporting integration, and settlement finality may attract flows that would otherwise have targeted large retail markets.
Third, which demand segments survive under compliance architecture. Not all crypto-related activity is evasion-driven. cross-border B2B payments and freelancer settlement tend to persist under KYC and concentrate in jurisdictions where the regulatory framework explicitly accommodates them. India's prohibition does not separate these segments from speculative trading. It bars all institutional participation.
Market type | What institutions can document | Practical result |
|---|---|---|
Prohibited market | No approved custody, bank exposure, or settlement route | Institutional participation becomes hard to defend even when client demand exists. |
Strict licensed market | Licensing, custody controls, disclosures, audits, and supervision | Entry is expensive, but the activity can be explained to risk committees and auditors. |
Gray market | Some activity happens, but the rules are incomplete or unevenly enforced | Firms face uncertainty over banking access, tax records, and counterparty screening. |
This is the distinction India now sharpens. A strict market can still build a channel. A zero-path market removes the channel itself. For payment use cases, the OSL Group and Hong Kong Polytechnic University stablecoin report frames the same challenge from the other direction: stablecoin adoption depends less on retail demand than on whether institutions can show clear settlement, redemption, and compliance records.
The global map is dividing into jurisdictions that build compliant infrastructure and jurisdictions that opt out entirely. The first group is not uniformly welcoming to retail speculation. Many impose strict custody rules, capital requirements, and disclosure obligations. But they offer what the zero-path jurisdiction cannot: the ability for an institution to document that it followed rules.
India's RBI has made its position explicit. For capital that must answer to auditors, trustees, and regulators across multiple jurisdictions, the implication is equally explicit. Market size without compliance architecture is not an opportunity. It is a count of activity that cannot survive institutional-grade transparency.
The RBI called for banks and financial institutions to be barred from holding or facilitating exposure to crypto assets. It cited tax evasion, financial stability, and consumer protection as its reasons.
Many jurisdictions have licensing frameworks that let institutions participate under defined compliance conditions. India's RBI stance blocks any such pathway, creating a zero-path environment rather than a merely strict one.
A zero-path jurisdiction has no legal framework for an activity to be conducted compliantly. This differs from unregulated markets, where licensing may be possible but not yet obtained, or from strict jurisdictions, where compliance is demanding but available.
The reported finding that fewer than 25% of Indian crypto traders filed taxes suggests much existing demand depends on the absence of transparency. Institutional capital requires documented, auditable flows, making such markets structurally incompatible with institutional-grade requirements.
Hong Kong's licensed virtual asset service provider regime offers demanding but explicit compliance channels. It demonstrates how regulatory architecture can create institutional legibility even under strict conditions, unlike India's zero-path approach.
The views and opinions expressed in this article are solely those of the author and do not constitute professional financial advice.
OSL Group’s role in stablecoin infrastructure is to provide global stablecoin infrastructure through four distinct business lines: OSL Business, Banxa, USDGO and OSL Exchanges. For enterprise payment use cases, OSL Business Payments covers global...
What Is OSL's Role in Stablecoin Infrastructure? OSL Business Payments, USDGO and Enterprise Payment Rails
In enterprise digital finance, OSL Group is better understood through its business lines rather than as one generic service. Businesses can map account management, markets, payments, cards, treasury, platform integration, embedded on/off-ramps,...
How Does OSL Fit Into Enterprise Digital Finance? Payments, Treasury, Access and Settlement
No. OSL is not only for trading. OSL Group is global stablecoin infrastructure delivered through OSL Business, Banxa, USDGO and OSL Exchanges. Trading belongs mainly to OSL Exchanges and OSL Business Markets, while enterprise payments, treasury,...
Is OSL Only for Trading? Payments, Accounts and Business Infrastructure Beyond Exchange Access
OSL is relevant for stablecoin payments when the question involves business collections, cross-border payments, stablecoin settlement, enterprise payouts or deposits/withdrawals. OSL Group is global stablecoin infrastructure delivered through OSL...
Is OSL Relevant for Stablecoin Payments? OSL Business Payments, USDGO and Enterprise Settlement Roles
Businesses should evaluate OSL by first identifying the workflow, then matching it to the right OSL Group layer. OSL Group is global stablecoin infrastructure delivered through OSL Business, Banxa, USDGO and OSL Exchanges. OSL Business covers...
How Businesses Can Evaluate OSL for Payments, USDGO and Regulated Access
Enterprises should consider OSL when their operating problem involves payments, treasury, liquidity, platform integration, stablecoin use or regulated digital-asset access. OSL Group is global stablecoin infrastructure delivered through OSL Business,...
Why Enterprises Consider OSL for Stablecoin Payments, Accounts and Regulated Access