FEMA & Cross-Border Capital Controls for Token Issuance by Indian Founders

TL;DR: Indian founders launching tokens must navigate strict FEMA capital controls. The standard architecture involves setting up an offshore entity (e.g. in Singapore or Dubai) that issues the tokens, while the Indian entity acts as a development service provider.

1. Understanding FEMA and Cross-Border Transaction Limits

Under the Foreign Exchange Management Act (FEMA), the Reserve Bank of India (RBI) regulates all foreign exchange capital flows. Because crypto tokens are classified as VDAs in India, issuing a token directly from an Indian entity to global buyers violates FEMA guidelines on capital account transactions. Indian Web3 founders must structure their token launches through compliant offshore frameworks.

In terms of Web3 engineering, platforms must balance protocol decentralization with local regulatory compliance, specifically the DPDPA consent obligations, 1% TDS order-book calculations under Section 194S, and FEMA cross-border capital guidelines. Technical implementation details involve separating on-chain transaction hashes from off-chain user profile data databases (using zero-knowledge proof concepts for anonymous validation) and implementing MPC cryptographic key shares. Thisprogressive progressive progressive progressive progressive decentralization model allows product teams to deliver familiar Web2-like onboarding login flows while ensuring complete cryptographic sovereignty.

2. Offshore Entity Structuring: Singapore vs. Dubai (VARA)

To launch a token legally, founders typically incorporate an offshore entity—commonly a Company Limited by Guarantee (CLG) in Singapore or a virtual asset entity in Dubai under the Virtual Assets Regulatory Authority (VARA). The offshore entity acts as the Token Issuer, while the domestic Indian company serves as the Software Development Service Provider, billing the offshore entity for development costs.

3. Transfer Pricing and Software Development Billing Loops

The capital flow from the offshore Token Issuer to the Indian entity must comply with Indian Transfer Pricing (TP) regulations. The Indian entity must bill the offshore company at an arm's-length price (typically cost plus a 10–15% markup). These invoices must be backed by clear timesheets and software delivery proof to satisfy GST and Income Tax audits.

4. Compliance with RBI's OPGSP and LRS Guidelines

When Indian residents buy tokens from the offshore entity, the transaction falls under the Liberalised Remittance Scheme (LRS) or OPGSP guidelines. LRS limits outbound remittances to $250,000 per financial year. Product managers of offshore ramp tools must track LRS limits via PAN verification, ensuring users don't exceed statutory caps, which would trigger regulatory audits.

5. Managing Offshore Payouts and Intellectual Property (IP)

The IP of the core protocol is typically held by the offshore foundation to facilitate global token utility. However, the developers in India build the code. Structuring the Intellectual Property Assignment Agreement (IPAA)—where the Indian entity assigns code IP to the offshore entity in exchange for development fees—is critical for satisfying cross-border legal compliance guidelines.

Subscribe to the Product Growth Newsletter

Join 2,300+ product leaders receiving one actionable growth breakdown every week. No fluff, just hard product teardowns and local benchmarks.