Case Study: FIU-IND Registration
How a Virtual Digital Asset Platform Completed FIU-IND Registration to Support Banking and Payment Partner Onboarding
For a Virtual Digital Asset (VDA-SP / VASP) platform preparing to operate in India, product readiness is only one part of launch readiness. Banking partners, payment gateways and other institutional counterparties may also expect more. Specifically, they may expect evidence that the business has addressed its applicable AML/CFT and regulatory obligations. Only then will they provide access to critical financial infrastructure. Registration with India’s Financial Intelligence Unit (FIU-IND) is not simply a commercial preference. It applies where a Virtual Digital Asset Service Provider carries out activities covered by India’s PMLA framework. In that case, registration and the applicable AML/CFT requirements form part of the regulatory foundation.
Below, this case study explains how Compliance7 supported a VDA platform through FIU-IND registration. That platform was preparing to operate compliantly in India.
Engagement at a Glance
- Client: Virtual Digital Asset platform preparing to serve the Indian market
- Challenge: Regulatory and AML/CFT readiness gap identified during launch and counterparty onboarding
- Service: PMLA applicability assessment, AML/CFT framework implementation and FIU-IND registration support
- Key deliverables: Risk assessment, AML/CFT policy framework, governance structure, registration documentation and regulatory response support
- Outcome: FIU-IND registration obtained, with an operational AML/CFT framework supporting launch readiness and institutional due diligence
The Problem
A Product-Ready Platform With an Unresolved Regulatory Gap
The platform was a Virtual Digital Asset Service Provider preparing to launch operations serving Indian customers. It had built its product and technology stack without factoring FIU-IND registration into its launch timeline. Like many platforms in this position, the founding team knew that crypto exchanges operate within a regulated AML/CFT environment in India. However, it had not yet assessed its activities against the notified VDA service categories. Nor had it incorporated its applicable PMLA Reporting Entity obligations into launch planning. It had also not yet designed an AML/CFT program capable of supporting FIU-IND registration and ongoing compliance.
The gap became urgent once the platform began approaching Indian banking partners and payment gateways. Those relationships were needed to support its fiat on- and off-ramp arrangements. Consequently, the move from product development to operational launch depended on satisfying counterparty compliance and due diligence expectations.
The platform encountered counterparties that were unwilling to progress discussions without evidence of FIU-IND registration. This reflected the platform’s need to demonstrate compliance with its applicable regulatory obligations before gaining access to critical banking and payment infrastructure.
Without registration, the platform faced three consequences. Its launch would stall. It could not secure banking relationships. Furthermore, it risked regulatory action for operating as an unregistered Reporting Entity.
The Solution
A Compliance Implementation Project, Not a Paperwork Exercise
Compliance7 structured the work as a compliance implementation project, not a document-preparation exercise. First, it assessed the platform’s business model and regulatory position. Next, it identified the gaps that needed addressing. Finally, it developed the governance, AML/CFT controls and supporting documentation the registration process required.
Scoping the Regulatory Position
FIU-IND registration obligations are activity-based. Therefore, the assessment began with the platform’s operating model. That meant its products, transaction flows, customer base, geographic exposure and the movement of fiat and Virtual Digital Assets. Compliance7 then assessed those activities against the applicable notified VDA service categories under the PMLA framework. The assessment established that the platform’s relevant activities brought it within the Reporting Entity framework. Consequently, it was required to meet the applicable registration and AML/CFT obligations.
AML/CFT Framework Design
The AML/CFT framework covered the full customer and transaction lifecycle. It ran from onboarding and risk assessment through customer due diligence, sanctions screening, blockchain analytics, travel rule, transaction monitoring and escalation. It also covered suspicious transaction assessment, record-keeping and governance oversight.
Governance Roles
The governance work went beyond identifying individuals for the Principal Officer (PO) and Designated Director (DD) roles. It also helped establish clear responsibility for AML/CFT oversight, escalation and reporting. Critically, that happened before the platform moved towards go-live.
Dossier and Regulatory Liaison
Compliance7 then compiled the completed registration dossier and supporting evidence for submission to FIU-IND. Afterwards, it supported the platform’s response to any subsequent regulatory queries during processing.
What the FIU-IND Registration Engagement Covered
The engagement ran across five areas. Together, they took the platform from an applicability question to a submitted application.
| Area | Support Provided |
|---|---|
| PMLA and FIU-IND applicability assessment | Assessing the platform’s activities against the applicable notified VDA service categories to confirm Reporting Entity status and determine the scope of applicable registration and AML/CFT obligations |
| AML/CFT program design | Risk-based CDD/KYC procedures, enterprise risk assessment, sanctions screening, blockchain analytics, travel rule, transaction monitoring, escalation and suspicious transaction assessment across the full customer and transaction lifecycle |
| Governance structure | Support with identifying and establishing the Principal Officer (PO) and Designated Director (DD) roles, together with clear responsibility for AML/CFT oversight, escalation, reporting and senior management accountability |
| Registration dossier | Preparation of the documentation and evidentiary basis required for the FIU-IND registration application |
| Regulatory liaison | Support in responding to FIU-IND queries or clarification requests during processing |
Scope of obligations depends on the services actually provided. The applicability assessment determined which of the platform’s business lines fell within the framework.
The Result
Registration Obtained and a Framework Built to Operate
The platform obtained FIU-IND registration. Before the engagement, it was a product-ready business with an unresolved regulatory and AML/CFT implementation gap. Afterwards, it had a launch-ready operating model. That model was supported by documented governance, customer due diligence procedures, risk assessment, transaction monitoring and registration documentation.
Following completion of the registration process, the platform used its regulatory and compliance documentation in ongoing discussions with banking and payment partners. That documentation gave it the evidentiary basis those counterparties had been asking for.
Beyond the registration itself, the platform also came away with an operational AML/CFT program. It was designed to function day to day, not merely to satisfy an application. Governance roles, policies and monitoring processes were already in place ahead of go-live.
FIU-IND registration decisions and processing timelines remain subject to the regulator’s assessment. Compliance7’s role is to support clients through the process. That support covers assessing applicability, developing the required compliance framework, preparing supporting documentation and assisting with regulatory queries where required.
Frequently Asked Questions (FAQ)
Which VDA Service Providers need to register with FIU-IND?
Virtual Digital Asset Service Providers (VDA-SP / VASP) carrying out activities covered by the notified VDA service categories under India’s PMLA framework are required to register with FIU-IND as Reporting Entities. They must also meet the applicable AML/CFT obligations. The requirement is activity-based. Whether a particular business falls within scope therefore depends on the services it actually provides. Relevant activities can include VDA-to-fiat exchange, exchange between VDAs and transfer of VDAs. They can also include the custodial or administration of VDAs, or of instruments enabling control over them.
What happens if a VDA platform operates in India without FIU-IND registration?
A VDA Service Provider carrying out activities that fall within the applicable PMLA framework is required to meet the relevant registration and AML/CFT obligations. Failure to do so can expose the business to regulatory action. Furthermore, it can create difficulties during banking and payment partner due diligence. It may also lead to operational disruption and reputational risk.
How long does FIU-IND registration take?
Timelines vary. They depend on the completeness of the application, the platform’s business model and the regulator’s own processing capacity. Ultimately, FIU-IND determines them rather than the applicant or its advisors. However, a well-prepared and complete application with a properly documented AML/CFT program is generally the most significant factor an applicant can control.
Preparing to Launch or Formalise a VDA / VASP Platform in India?
Does your business operate as a Virtual Digital Asset Service Provider serving Indian customers or is it preparing to? If so, Compliance7 can assess your PMLA applicability and manage the FIU-IND registration process. That covers AML/CFT program design, application submission and regulatory liaison.
