Two founders, one AI platform, and a regulatory question that changed their launch plan.
An illustrative case study based on the current IFSCA framework. The founders, company and conversations are fictional.
“We have the product, two interested overseas banks and an investor,” said Meera. “Let’s set up in GIFT City and launch.”
Her co-founder, Rohan, agreed.
Their Bengaluru start-up, ClearBridge AI, had built software that helps financial institutions spot suspicious transactions and review customer-onboarding documents. The platform did not accept deposits, lend money or move customer funds. It simply supplied technology to institutions that did those things.
The founders assumed they needed a “FinTech license.”
At the first advisory meeting, though, the conversation opened with a different question:
“Are you providing a financial service, or technology that supports a financial service?”
That one distinction changed their roadmap.
ClearBridge’s proposed AI, fraud-detection and KYC-support services pointed towards the IFSCA (TechFin and Ancillary Services) Regulations, 2025, commonly called the TAS framework.
One experimental feature, however, needed controlled testing with a financial institution. So the founders had two routes to weigh:
IFSCA’s FinTech Sandbox Framework, issued in March 2026, makes it clear that the sandbox is not a substitute for an authorization route that is already available. A sandbox is not a compulsory starting point for every technology company.
“So we shouldn’t enter a sandbox just because we’re a start-up?” Rohan asked.
“Exactly. Choose the route for the activity, not for the label on your pitch deck.”
For its commercial business, ClearBridge decided to set up a new company in GIFT-IFSC. The TAS framework also accommodates eligible LLPs, as well as branches of companies or LLPs established outside IFSC, whether Indian or overseas.
The founders drew up a coordinated implementation plan:
Incorporation, premises and regulatory approvals each run on their own track and need to be coordinated. Incorporating the company alone does not authorize it to operate as a TAS provider.
Meera’s presentation showed what the software could do. The application, on the other hand, had to explain what the business would do. The founders put together:
IFSCA’s published application checklist covers these business, ownership, premises and financial-information requirements. Since ClearBridge was a newly established applicant, its historical financial records had to be dealt with appropriately, not invented to satisfy a checklist.
Even the service description became sharper. Instead of presenting a platform that could do everything, they described it as technology supporting fraud detection and customer due diligence. It was never meant to be a platform authorized to carry out every banking activity.
That was Rohan’s next question, and a fair one. Under the standard TAS requirement, the Principal Officer and the Compliance Officer must be full-time employees based in IFSC. IFSCA’s FAQs do recognize limited exceptions. For instance, an entity serving only its own group entities in IFSC may be allowed to skip the Principal Officer, with IFSCA’s approval. An applicant should not assume, however, that oversight from a head office elsewhere satisfies the ordinary requirement.
ClearBridge therefore budgeted for local personnel and real operating substance, not just an office address. It also planned for specified foreign-currency operations, USD regulatory financial reporting, and an INR account for administrative and statutory expenses. Application and recurring fees would be checked against the prevailing fee circular, not an old FinTech brochure.
One more timeline worth knowing: after in-principle approval, a TAS applicant ordinarily has 180 days to fulfil the regulatory and approval conditions, unless IFSCA extends the period. That is a compliance window. It is not a promise that the whole registration process will take 180 days.
For its unproven feature, ClearBridge considered controlled testing. The Sandbox Framework, effective 16 March 2026, sets out a two-stage process on SWIT: a preliminary application first, which IFSCA examines for suitability, and then a final application once the preliminary proposal is accepted.
A credible proposal explains:
IFSCA may attach conditions, including a testing-partner requirement, before granting a Limited Use Authorization. Testing can run for up to twelve months, with a discretionary extension of up to six months.
The founders also learned that the sandbox is not one-size-fits-all. The FinTech Innovation Sandbox, which tests a solution in isolation from the live market using data made available by financial institutions in IFSC, does not require physical presence in IFSC. The FinTech Regulatory Sandbox, which involves live testing with a limited set of real customers, is a different matter with its own conditions. Either way, sandbox flexibility should not be confused with the operating requirements that apply to a commercial TAS provider.
ClearBridge’s sensible roadmap was to pursue the appropriate commercial registration for its deployable technology services, and to assess the experimental feature separately for sandbox testing.
Neither route would automatically allow deposit-taking, lending, payments or unrestricted handling of customer money. A sandbox authorization permits testing under specified conditions and is not a license for unrestricted commercial operations (see the IFSCA FinTech Sandbox Framework).
Recent changes also need to be read activity by activity. The May 2026 amendment to the TAS framework introduced a separate framework for Trust and Company Services Providers connected with permitted leasing activities. It did not turn every TechFin registration into a universal financial-services license.
At GIFT City, the smartest first investment is clarity.
Before committing to premises, hiring people or announcing a launch, ask:
“Exactly what will our entity do, for whom, and under which regulatory permission?”
That answer shapes the structure, the application, the cost and the compliance plan.
PKM Advisory Services LLP supports businesses with evaluating the right GIFT-IFSC route, entity structuring, application preparation, setup coordination and ongoing compliance planning.
To discuss your plans, write to us at pkm@pkmadvisory.com or pkmadvisory@gmail.com, or call +91 98987 14310.
Illustrative educational case study. Regulatory approvals depend on the proposed activities, eligibility and applicable requirements; no approval or timeline is guaranteed.
