Cross-Framework Mapping

India Account Aggregator Framework (RBI)vsFATF Recommendation 16 - Virtual Asset Travel Rule

See exactly how India Account Aggregator Framework (RBI) controls map to FATF Recommendation 16 - Virtual Asset Travel Rule. Pre-computed mappings, identified gaps, and coverage analysis.

1
Controls Mapped
7
Gaps Found
12%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

India Account Aggregator Framework (RBI) maps to FATF Recommendation 16 - Virtual Asset Travel Rule with 12% coverage across 1 directly mapped controls. Analysis of 8 India Account Aggregator Framework (RBI) controls identifies 7 compliance gaps — primarily concentrated in RBI AA Industry Standards + Coordination.

Source: TheArtOfService Knowledge Graph | 8 controls analysed | 718 frameworks | 330K+ cross-framework mappings

Control Mappings

Showing 1 of 1 mapped controls across 1 domains. Sign up to explore all 330K+ mappings across 718 frameworks.

RBI AA Ecosystem(1 mappings)

RBI-AA-Ecosystem-FIPs-FIUs-Interoperability-Onboarding-Sahamati-DPI-IndiaStackRBI AA Ecosystem - Financial Information Providers (FIPs) + Financial Information Users (FIUs) + Interoperability + Sahamati SRO Onboarding + DPI India Stack + Cross-Sector Regulators
R.16-VATR.UnhostedUnhosted (self-hosted / non-custodial) wallet transfers - 2024 Targeted Update

Related Comparisons

Other India Account Aggregator Framework (RBI) comparisons

Other FATF Recommendation 16 - Virtual Asset Travel Rule comparisons

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 718 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 718 framework browser
  • Cross-framework mappings (330K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between India Account Aggregator Framework (RBI) and FATF Recommendation 16 - Virtual Asset Travel Rule?

India Account Aggregator Framework (RBI) has 8 controls across its framework, while FATF Recommendation 16 - Virtual Asset Travel Rule covers 13 controls. Direct mapping analysis identifies 1 overlapping controls (12% coverage). The frameworks diverge most significantly in RBI AA Industry Standards + Coordination, where 1 India Account Aggregator Framework (RBI) controls have no direct FATF Recommendation 16 - Virtual Asset Travel Rule equivalent.

How many controls map between India Account Aggregator Framework (RBI) and FATF Recommendation 16 - Virtual Asset Travel Rule?

Of 8 total India Account Aggregator Framework (RBI) controls, 1 map directly to FATF Recommendation 16 - Virtual Asset Travel Rule controls — representing 12% coverage. The remaining 7 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping India Account Aggregator Framework (RBI) to FATF Recommendation 16 - Virtual Asset Travel Rule?

7 India Account Aggregator Framework (RBI) controls have no direct equivalent in FATF Recommendation 16 - Virtual Asset Travel Rule. The highest concentration of gaps is in RBI AA Industry Standards + Coordination with 1 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between India Account Aggregator Framework (RBI) and FATF Recommendation 16 - Virtual Asset Travel Rule?

The domain with the highest gap count is RBI AA Industry Standards + Coordination (1 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.