Web3 practice · Service · India, UAE and EU

Crypto AML programme design and MLRO support, after the registration.

The FIU-IND guidelines updated on 8 January 2026 set the standard a registered VDA service provider is supervised against: a full-time Principal Officer in India, PAN-based KYC with a liveness selfie and a geotagged onboarding, KYC refresh every six months for high-risk clients, continuous monitoring, a travel rule with no threshold and an independent annual audit. FIU-IND registration, a VARA licence or a MiCA authorisation is the gate. What the regulator supervises afterwards is the programme behind it: named officers, risk assessments, monitoring, reporting and audit. We design that programme, document it and support the officer who runs it.

Advised on $100M+ of founder fundraising and $200M+ in deal value, with 10+ IPO and pre-IPO mandates. Figures are internal, as of 2026.

The FIU-IND guidelines updated on 8 January 2026 require every registered VDA service provider to run a Board-approved AML, CFT and CPF programme: a Designated Director and a separate, full-time, India-based Principal Officer; PAN-based KYC with a liveness selfie, the latitude and longitude of the onboarding location with timestamp and IP address, and penny-drop bank verification; KYC refresh every six months for high-risk clients and yearly for the rest; monitoring that traces the origin and destination of each asset; a travel rule with no threshold; sanctions screening at every transaction; prompt STRs and a Monthly Report; and an independent annual audit. After FIU-IND registration or a VARA licence, Infinilex designs and documents that programme and supports the Principal Officer or MLRO on a retainer, while the statutory roles and the reserved decisions stay with your own appointees.

A crypto AML compliance consultant for India, the UAE and the EU does not hold your Compliance Officer or Principal Officer role; the rules reserve those for your own appointee. VARA requires a full-time Compliance Officer, UAE resident or passport holder, approved by VARA, and FIU-IND a full-time, India-based Principal Officer. Infinilex designs the AML programme those officers run, documents it against the FIU-IND guidelines of 8 January 2026, the VARA rulebooks and MiCA with the AML Directive, and supports the MLRO or Principal Officer on a retainer.

This page is about what happens after the gate; the gate is on FIU-IND registration, VARA licensing and MiCA authorisation. Principal Officer and Designated Director requirements are in FIU-IND registration for crypto businesses in India; travel rule thresholds are on the travel rule page. The US gate, FinCEN registration on Form 107 and the state licences the BSA programme precedes, is on which US crypto licences you need.

What the FIU-IND guidelines of 8 January 2026 require

The document is titled AML and CFT Guidelines for Reporting Entities Providing Services Related to Virtual Digital Assets (updated as on 08.01.2026). It sets out the registration process (chapter 2) alongside the programme obligations. Paragraph 1.4 states that the obligations are activity-based and apply irrespective of physical presence in India; paragraph 2.1(b) treats non-registration as a violation that may invite action under section 13(2) of the PMLA. On 9 September 2026 the Director issued section 13 notices to fifteen offshore VDA service providers, with notices to take down their apps and URLs (Ministry of Finance, PIB Release ID 2308131); the names are on the registered VDA service providers page. The programme below is what the Director tests at the in-person meeting, which the Designated Director and Principal Officer must attend with a live demonstration of the KYC, transaction monitoring, blockchain analytics, travel rule and sanctions screening tools (paragraph 2.5), so the design work starts before the FIU RE-ID is issued.

Schedule B · FIU-IND guidelines of 8 January 2026: the programme, paragraph by paragraph (read in full 6 October 2026)
AreaWhat the guidelines requireParagraph
OfficersA Designated Director and a Principal Officer who are separate people. The Principal Officer is full-time and exclusive, at management level, has at least three years of AML experience, is based in India and sits outside business and operations. The Principal Officer reports to the Board preferably quarterly, and at least once a year on programme effectiveness, open risks, STR summaries, FIU-IND instructions and proposed policy changes.3.1, 3.2, 3.3(j)
Policies and client acceptanceBoard-level AML, CFT and CPF Policies, on a group basis where PMLR rule 3A applies; an independent annual review of the Policies by people who did not write them; a summary displayed on the website or app used for onboarding and login; a Board-approved client acceptance framework with no anonymous or fictitious accounts and termination where CDD cannot be completed.3.4, 3.5
Risk assessmentA documented enterprise risk assessment at a Board-set interval not exceeding one year, re-run before any new technology, product or service; clients classified as at least High and Medium risk, with the classification reviewed at least once in six months.3.6.1, 3.6.2
Onboarding KYCPAN is mandatory, plus one of passport, driving licence, proof of possession of Aadhaar number, Voter ID or the equivalent e-document; mobile and email verified by OTP or link; a live photograph with liveness detection; the latitude and longitude of the onboarding location with date, timestamp and IP address; enhanced measures where the geo-coordinates do not match the address given; penny-drop verification of the bank account; IP address, device ID, wallet addresses and transaction hashes collected as identifiers.4.1.4, 4.2.1 to 4.2.6
Enhanced due diligenceMandatory for clients from FATF grey or black list and other high-risk jurisdictions, for PEPs and for non-profit organisations; source of funds, purpose and open-source checks; where enhanced measures cannot be completed, the relationship is terminated and an STR filed.4.4
KYC refreshAt least every six months for high-risk clients and at least yearly for all others, measured from account opening or the last update; any extra measure such as live video or physical presence must be written into the Board-approved CDD programme.4.5
MonitoringSystems that identify the origin and destination of a VDA, covering intermediary and hosted-wallet cases; FIU-IND red-flag indicators and typologies built into the scenarios; every alert reviewed by the monitoring team and the Principal Officer without delay; transaction data stored for reconstruction with role-based access and backup.5.1, 5.2
Travel ruleOriginator PAN and identity document number, name, wallet address, verified address and date of birth, and beneficiary name and wallet address, transmitted before or with every transfer between reporting entities; no threshold and no post-facto submission; counterparty CDD and screening first.5.3
Sanctions screeningAt onboarding, on any KYC change, on any list change and when any VDA transaction is initiated; UNSC, UAPA and WMDA directives applied promptly; a wallet may be held until screening clears.5.4
Reporting and recordsSTRs filed promptly, including attempted transactions and irrespective of amount, built on KYC, transaction, metadata, IP and device data; no tipping off before, during or after a filing; a Monthly Report of metrics, activity indicators and compliance status; records kept five years and audit trails tamper-proof.5.5 to 5.7, 6.2
Assets and counterpartiesAnonymity-enhancing tokens, mixers and tumblers are not to be facilitated; transfers to or from unhosted wallets carry data collection and enhanced measures; smart-contract automation does not relieve the obligations and ICO or ITO activity is strongly discouraged; unregistered VDA service providers are treated as high risk.7.1 to 7.5
Audit and trainingAn independent annual audit of AML, CFT and CPF controls and an internal audit at least yearly, both reported to the Board or a Board committee; recruitment screening, an ongoing training programme and written instruction manuals.3.6.3, 3.7

Source, read in full 6 October 2026: FIU-IND, AML and CFT Guidelines for Reporting Entities Providing Services Related to Virtual Digital Assets, updated as on 8 January 2026 (33 pages); Ministry of Finance release of 9 September 2026, PIB Release ID 2308131. Paragraph numbers are to the guidelines.

Schedule A: who must be named, and what the programme must do, in each regime

Schedule A · Named officers and programme duties: FIU-IND, VARA with UAE federal law, MiCA with the AML Directive, as at 6 October 2026
DimensionIndia: FIU-INDDubai: VARA and UAE federal lawEU: MiCA and the AML Directive
Named officersDesignated Director (PMLR rule 2(1)(ba)) and Principal Officer (rule 2(1)(f)), separate people, both notified through FINGate.Compliance Officer at management level with independent decision-making (Cabinet Resolution 134 of 2025, Art 22). VARA: a Compliance Officer (Part I.C) and an MLRO (Part III.A), one person absent conflicting duties.Compliance officer at management level (AMLD Art 8(4)(a)) and a responsible board member (Art 46(4)); from 10 July 2027, a compliance manager plus a compliance officer (AMLR Art 11).
Who can hold itManagement level, full-time and exclusive, based in India, three years’ AML experience, outside business and operations.CO: five years’ experience, Fit and Proper, VARA-approved, UAE resident or passport holder, full-time employee reporting to the Board. MLRO: two years’ AML/CFT experience, Fit and Proper.AMLR Art 11: sufficiently high hierarchical standing; until then, national transposing law.
OutsourcingAlert analysis may be delegated; the STR decision rests with the Principal Officer.MLRO, CISO and Data Protection Officer may be outsourced (Company Rulebook Part IV.A.3), the individual accountable to VARA, which may require a full-time employee; cross-border outsourcing needs prior notification. The CO is not outsourced.From 10 July 2027: permitted with prior notification and full liability retained, save six reserved tasks (AMLR Art 18).
Risk assessment cadenceEnterprise assessment at most yearly and before any new product or technology; client classification reviewed at least six-monthly.Business and client risk assessments no longer than every three months and on significant change (Part III.D, Rules III.D.3 and III.D.8).Procedures monitored and regularly evaluated (MiCA Art 68(8)); business-wide risk assessment by the compliance officer, approved by the management body (AMLR Art 10).
KYC refresh and ongoing CDDPeriodic CDD updation at least every six months for high-risk clients and at least yearly for all others, measured from account opening or the last update (para 4.5.2); the onboarding record carries PAN, a liveness selfie, geo-coordinates with timestamp and IP address and a penny-drop bank check (paras 4.2.1 to 4.2.6).CDD before or during onboarding (Rule III.E.3) and ongoing supervision that keeps CDD records up to date by regular review (Rule III.E.5); client risk assessments re-run no longer than every three months (Rule III.D.8); MLRO and Senior Management approval before any PEP relationship (Rule III.E.6).CDD applied to existing customers at appropriate times on a risk-sensitive basis and when circumstances change (AMLD Art 14(5)); ongoing monitoring with documents kept up to date (Art 13(1)(d)); procedures regularly evaluated (MiCA Art 68(8)).
Independent auditIndependent annual audit of AML, CFT and CPF controls; internal audit at least yearly, reported to the Board.Independent audit function (Cabinet Resolution 134 of 2025, Art 21); VARA internal audit at least quarterly and an annual auditor attestation on the internal control structure.Independent audit function where size warrants (AMLD Art 8(4)(b)); an external expert where none exists (AMLR Art 9(2)(b)).

Sources, read 25 September 2026: FIU-IND VDA guidelines, 8 January 2026; VARA Compliance and Risk Management Rulebook (current version, 2025), Parts I.C, I.G, I.H, III.A, III.B, III.D; VARA Company Rulebook Part IV; Decree-Law 10 of 2025; Cabinet Resolution 134 of 2025; MiCA; Directive 2015/849; Regulation 2024/1624; Regulation 2023/1113. Read 6 October 2026: the FIU-IND guidelines of 8 January 2026 in full; VARA Compliance and Risk Management Rulebook version 19 May 2025, Parts III.D, III.E and I.H; Directive 2015/849, consolidated text of 9 July 2024; PIB Release ID 2308131 of 9 September 2026.

“With their presence in both the US and India, Infinilex provides Indian founders with US-incorporated entities seamless guidance through the complex maze of compliance requirements.”

Gaurav Luhariwala · Founder & CEO, TejasAI

What crypto AML programme design covers

  • Enterprise and client risk assessment. Documented and proportionate, built to the shortest cycle you are under (quarterly under VARA, at most annual under FIU-IND with a six-monthly client review) and re-run before any new product or technology goes live.
  • The policy set and its approvals. Board-level AML, CFT and CPF Policies, the website summary FIU-IND requires, the group-basis policy where PMLR rule 3A applies, and for VARA a policy pack prepared for third-party attestation and the 21-day resubmission after every change.
  • CDD, enhanced due diligence and KYC refresh. The FIU-IND onboarding standard of paras 4.2.1 to 4.2.6 (PAN plus one identity document, OTP-verified mobile and email, a liveness selfie, geo-coordinates with timestamp and IP address, and a penny-drop bank check), the six-monthly and yearly KYC refresh of para 4.5.2, VARA’s risk-based CDD with occasional-transaction checks at AED 3,500 and MLRO plus Senior Management sign-off for PEPs, enhanced measures for FATF grey and black list exposure, and the refresh calendar. The India build list is in our FIU-IND registration checklist.
  • Monitoring, screening and the travel rule. Scenarios mapped to FIU-IND red-flag indicators and the FATF Virtual Assets Red Flag Indicators report, distributed ledger analytics with the capability review VARA expects, real-time sanctions screening, the FIU-IND rules on anonymity-enhancing tokens, mixers and unhosted wallets, and travel rule information moving before or with the transfer (thresholds: the travel rule page).
  • Reporting lines. STRs to FIU-IND filed promptly, irrespective of amount and including attempted transactions, the Monthly Report and tipping-off controls; under VARA, immediate reporting to the UAE FIU on goAML, the 48-hour response to FIU or VARA requests, and the Part I.H returns.
  • MLRO and Principal Officer support. Alert quality assurance, the Board pack at each regulator’s cadence (FIU-IND preferably quarterly and at least annually, paras 3.2(h) and 3.3(j); VARA quarterly), training, regulator correspondence and the evidence file for the annual audit, so your appointee decides on a complete record.

How the programme is built: ten steps

  1. Enterprise risk assessment. FIU-IND para 3.6.1, VARA Part III.D, AMLD Art 8(1), AMLR Art 10 from 2027; outcome to the Board.
  2. Board-approved policies. FIU-IND para 3.4, VARA Part III.B with third-party attestation, AMLD Art 8(5), Cabinet Resolution 134 of 2025, Art 21.
  3. Client risk classification. At least High and Medium under FIU-IND, reviewed six-monthly (para 3.6.2); quarterly under VARA (Rule III.D.8).
  4. CDD and enhanced due diligence. FIU-IND chapter 4 with the 2026 onboarding data points (paras 4.2.1 to 4.2.6) and the KYC refresh calendar (para 4.5.2), VARA Part III.E, and the originator and beneficiary information the TFR requires with every transfer.
  5. Sanctions screening. UNSC, UAPA and WMDA lists at onboarding, on list changes and at every transaction (FIU-IND para 5.4); automated real-time screening and immediate freezing (VARA Part III.H).
  6. Transaction monitoring with chain analytics. Systems that identify a VDA’s origin and destination (FIU-IND para 5.2); ledger analytics and red-flag scenarios (VARA Part III.C).
  7. Travel rule technology. FIU-IND para 5.3, VARA Part III.G, TFR Art 14; counterparty VASP due diligence and the sunrise plan.
  8. STR and regulator reporting lines. FIU-IND paras 5.5 to 5.7, VARA Parts III.F and I.H, AMLR Art 11(2); who decides, who files, and the reasons recorded on closed alerts.
  9. Training and hiring screening. FIU-IND para 3.7, VARA Part I.J, AMLD Art 46, AMLR Art 12.
  10. Independent annual audit. FIU-IND para 3.6.3, Cabinet Resolution 134 of 2025, Art 21, AMLD Art 8(4)(b), AMLR Art 9(2)(b), alongside VARA’s quarterly internal audit and annual auditor attestation.

A licence is the gate, not the compliance

A VARA licence or an FIU-IND registration records that the regulator was satisfied on the day it was granted. What the bank asks for from the same programme, in the UAE, the EU and India, is on bank and EMI accounts for a licensed VASP. Supervision starts the day after, and it runs on a calendar. Under VARA Part I.H (rulebook version 19 May 2025, read 6 October 2026) a VASP files monthly financial statements and the addresses of its VA wallets; quarterly Board and committee minutes, a statement of compliance with VARA’s financial requirements and a risk exposure report; and annually audited financial statements with the auditor’s attestation on internal controls, a Senior Management compliance assessment, a sample of the first 100 clients onboarded and the group structure chart with UBOs, with VARA able to require further information on request (Rule I.H.4). Business and client risk assessments are re-run no longer than every three months (Rules III.D.3 and III.D.8).

Under the FIU-IND guidelines a registered provider files STRs and a Monthly Report (paras 5.5 and 5.7), reviews client risk classification at least every six months (para 3.6.2), refreshes KYC on the six-month and one-year cycle (para 4.5.2), takes the Principal Officer’s report to the Board (para 3.3(j)) and commissions the independent annual audit (para 3.6.3); the Director may cancel a registration where the obligations are not met (para 2.5.3). None of this is done by the licence. It is done by the programme and the officers who run it, which is the work on this page.

How a crypto AML programme engagement is staged

Fixed-scope stages, mapped on a free discovery call. Stage one is the gap assessment: your current programme read against the FIU-IND guidelines, the VARA rulebooks or MiCA with the AML Directive, with a finding on each of the ten steps; it stands on its own. Stage two is the build: policies, procedures, risk assessments, training, reporting templates and the audit evidence file. Stage three, optional, is MLRO or Principal Officer support on a monthly retainer. Plan and cost are agreed first: how engagements work.

Who signs what on crypto AML programme work

Infinilex is a consultancy: we design and document the programme and hold the evidence file. The statutory roles stay with your appointees: the Designated Director and Principal Officer under the PMLA, the Compliance Officer and MLRO under VARA and UAE federal law, the compliance officer and responsible board member under the AML Directive. They take the reserved decisions: the STR, the risk profile, the onboarding call. The India leg of the advisory work is signed by Infinilex counsel enrolled as advocates in India, or by Infinilex’s company secretary or chartered accountant where a statute names that professional; the UAE leg by Infinilex counsel qualified for VARA matters. For the EU, Infinilex scopes the work, builds the fact record and briefs the EU local counsel who sign and file, named to you before they act.

VARA’s policy attestation is by the competent third party the rulebook requires. Where an opinion is needed alongside the programme, Infinilex counsel qualified in India, the UAE and the US sign opinions for those jurisdictions; for the EU and any other jurisdiction Infinilex scopes and coordinates the local counsel who sign.

Frequently asked questions

Can a VASP outsource its Compliance Officer or MLRO under VARA?

Yes, with conditions. The VARA Company Rulebook, Part IV.A.3, lets a VASP outsource the MLRO, CISO and Data Protection Officer roles if Part IV is complied with and the individual accepts personal responsibility to VARA. VARA may at its discretion require a full-time employee in any of those roles, encourages in-house resourcing, and must be notified before any cross-border outsourcing. The Compliance Officer is different: Part I.C.1 of the Compliance and Risk Management Rulebook requires a full-time employee, UAE resident or passport holder, approved by VARA.

Can Infinilex be our Compliance Officer or Principal Officer?

No, and the rules are the reason. FIU-IND requires a Principal Officer exclusively engaged with the reporting entity full-time, based in India, with at least three years of AML experience, and a separate Designated Director. VARA requires a full-time Compliance Officer, UAE resident or passport holder, approved by VARA. Both appointments are yours. Infinilex designs the programme those officers run, documents it, trains the team, prepares the Board and regulator reporting and supports the officer on a retainer, so the role does not rest on one person.

What does the annual independent AML audit cover?

For an FIU-IND reporting entity, paragraph 3.6.3 of the 8 January 2026 guidelines requires an independent annual audit of AML, CFT and CPF controls, systems, procedures and safeguards, an internal audit at least yearly reported to the Board or a Board committee, plus an annual independent review of the Policies by people who did not write them. In the UAE, Article 21 of Cabinet Resolution 134 of 2025 requires an independent audit function testing AML controls; VARA adds a quarterly internal audit and an annual auditor attestation on the internal control structure. In the EU, AMLD Article 8(4) requires an independent audit function where size warrants it.

Which AML decisions can never be outsourced?

In the EU, Article 18 of Regulation (EU) 2024/1624, applying from 10 July 2027, lists six tasks that can never be outsourced: proposing and approving the business-wide risk assessment, approving internal policies, the customer risk-profile decision, the decision to onboard, suspicious transaction and threshold reporting to the FIU, and approving the criteria for detecting suspicious transactions. FIU-IND places the ultimate STR decision with the Principal Officer, who records the reasons for reporting or closing every alert. VARA keeps the Compliance Officer accountable for anything delegated. Infinilex builds the programme around those reserved decisions; your appointee takes them.

What do the FIU-IND guidelines of 8 January 2026 require of a VDA service provider?

A Board-approved AML, CFT and CPF programme run by named officers. The guidelines require a Designated Director and a separate Principal Officer who is full-time, India-based, at management level and has at least three years of AML experience (para 3.2). Onboarding needs PAN plus one identity document, OTP-verified mobile and email, a live photograph with liveness detection, the latitude and longitude of the onboarding location with date, timestamp and IP address, and penny-drop verification of the bank account; a mismatch between the geo-coordinates and the address given triggers enhanced due diligence (paras 4.2.1 to 4.2.6). KYC is refreshed at least every six months for high-risk clients and at least yearly for the rest (para 4.5.2). Monitoring must trace the origin and destination of each asset (para 5.2), travel rule data moves before or with every transfer with no threshold (para 5.3), sanctions screening runs at onboarding, on KYC or list changes and at every transaction (para 5.4), STRs are filed irrespective of amount alongside a Monthly Report (paras 5.5 and 5.7), anonymity-enhancing tokens and mixers are not facilitated (paras 7.4 and 7.5), and an independent annual audit reports to the Board (para 3.6.3). The guidelines were read in full on 6 October 2026.

Does a VARA licence or an FIU-IND registration mean my crypto business is fully compliant?

No. The licence or registration records that the regulator was satisfied on the day it was granted; compliance is what the regulator supervises afterwards, on a calendar. Under VARA a VASP files monthly financial statements and wallet addresses, quarterly Board minutes, a statement of compliance with the financial requirements and a risk exposure report, and annually audited accounts with an auditor attestation on internal controls and a Senior Management compliance assessment (Part I.H); it re-runs business and client risk assessments at least every three months (Rules III.D.3 and III.D.8) and resubmits policies within 21 days of any change. Under FIU-IND a registered provider files STRs and a Monthly Report, reviews client risk classification at least every six months, refreshes KYC on the six-month and one-year cycle, takes the report of the Principal Officer to the Board and commissions an independent annual audit; the Director may cancel a registration where the obligations are not met (para 2.5.3), and on 9 September 2026 issued section 13 notices to fifteen offshore providers that had not complied. A licence without a working programme is the exposure, not the cover.

After FIU-IND registration or a VARA licence, who designs our AML programme and supports the MLRO?

Infinilex does, and your appointee runs it. Infinilex writes the enterprise and client risk assessments, the Board-level policy set, the CDD and enhanced due diligence procedures, the monitoring scenarios, the travel rule and screening set-up, the reporting lines and the training, then supports the Principal Officer or MLRO on a retainer with alert quality assurance, the Board pack, regulator correspondence and the evidence file for the annual audit. The statutory roles stay yours: the Designated Director and Principal Officer under the PMLA, the Compliance Officer and MLRO under VARA. Where an opinion is needed alongside the programme, Infinilex counsel qualified in India, the UAE and the US sign opinions for those jurisdictions; for the EU and any other jurisdiction Infinilex scopes and coordinates the local counsel who sign. Email is answered within one working day.

Next step

Tell us which regulator has you, and who holds the role today.

Send the registration or licence you hold, the officers you have named and the last Board report. We will tell you on the discovery call where to look first, before any commitment.

Thirty minutes with Prashant Sharma, the founder, who does the work himself. You leave with next steps either way. Email is read by the founder and answered within one working day.

Further reading

FIU-IND registration for crypto businesses in India · FIU-IND registration checklist · FIU-IND registered VDA service providers: the full list · The crypto travel rule: India, the UAE, the EU and the US · UAE VASP licensing-readiness checklist · Self-custody compliance controls checklist · MPC and smart-contract wallets: which key arrangements are custody?

Related services: FIU-IND registration · VARA licensing · MiCA authorisation · ADGM and DIFC crypto licensing · Fractional general counsel and compliance retainer

This page is general information about the service, not advice on your facts. Guidelines and rulebooks change; positions are stated as at 6 October 2026 for the FIU-IND guidelines, VARA Parts I.H, III.D and III.E, the AML Directive and the PIB release of 9 September 2026, and as at 25 September 2026 for the other VARA, UAE federal and EU sources; all are re-verified quarterly. Whether a regulator accepts a programme, officer or outsourcing arrangement depends on your facts; no outcome is promised.