W3C Verifiable Credentials (VC) Data Model 2.0vsFATF Recommendation 16 - Virtual Asset Travel Rule
See exactly how W3C Verifiable Credentials (VC) Data Model 2.0 controls map to FATF Recommendation 16 - Virtual Asset Travel Rule. Pre-computed mappings, identified gaps, and coverage analysis.
Need this as a report you can hand to an assessor? A coverage crosswalk for this pair can be built to order.
According to the TheArtOfService Compliance Knowledge Graph:
W3C Verifiable Credentials (VC) Data Model 2.0 maps to FATF Recommendation 16 - Virtual Asset Travel Rule with 3% coverage across 1 directly mapped controls. Analysis of 32 W3C Verifiable Credentials (VC) Data Model 2.0 controls identifies 31 compliance gaps, primarily concentrated in Holders and Presentations.
Source: TheArtOfService Knowledge Graph | 32 controls analysed | 686 frameworks | 306K+ cross-framework mappings
Control Mappings
Showing 1 of 1 mapped controls across 1 domains. Sign up to explore all 306K+ mappings across 686 frameworks.
Ecosystem(1 mappings)
A W3C Verifiable Credentials (VC) Data Model 2.0 to FATF Recommendation 16 - Virtual Asset Travel Rule crosswalk, built to order
The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which FATF Recommendation 16 - Virtual Asset Travel Rule controls your existing W3C Verifiable Credentials (VC) Data Model 2.0 work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.
This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.
If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.
This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.
If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.
- Every evidenced control, with the reasoning behind it
- Every gap, with what it requires
- Its level of review stated plainly, not a bare number
Why this page shows two different percentages. The 3% in the header counts how many W3C Verifiable Credentials (VC) Data Model 2.0 controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many FATF Recommendation 16 - Virtual Asset Travel Rule controls are actually evidenced, after a pass that argued against each mapping and kept only what survived. They answer different questions and they are not meant to agree.
A crosswalk narrows the work. It does not replace an audit, and your assessor may take a different view on individual controls. Mappings between frameworks are judgements, not text printed in either standard, which is why every claim in the report shows its reasoning. Questions go to support@theartofservice.com.
Related Comparisons
Other W3C Verifiable Credentials (VC) Data Model 2.0 comparisons
Other FATF Recommendation 16 - Virtual Asset Travel Rule comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 686 frameworks, at a fraction of consulting costs.
Free
- ✓ 686 framework browser
- ✓ Cross-framework mappings (306K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between W3C Verifiable Credentials (VC) Data Model 2.0 and FATF Recommendation 16 - Virtual Asset Travel Rule?
W3C Verifiable Credentials (VC) Data Model 2.0 has 32 controls across its framework, while FATF Recommendation 16 - Virtual Asset Travel Rule covers 13 controls. Direct mapping analysis identifies 1 overlapping controls (3% coverage). The frameworks diverge most significantly in Holders and Presentations, where 5 W3C Verifiable Credentials (VC) Data Model 2.0 controls have no direct FATF Recommendation 16 - Virtual Asset Travel Rule equivalent.
How many controls map between W3C Verifiable Credentials (VC) Data Model 2.0 and FATF Recommendation 16 - Virtual Asset Travel Rule?
Of 32 total W3C Verifiable Credentials (VC) Data Model 2.0 controls, 1 map directly to FATF Recommendation 16 - Virtual Asset Travel Rule controls, representing 3% coverage. The remaining 31 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping W3C Verifiable Credentials (VC) Data Model 2.0 to FATF Recommendation 16 - Virtual Asset Travel Rule?
31 W3C Verifiable Credentials (VC) Data Model 2.0 controls have no direct equivalent in FATF Recommendation 16 - Virtual Asset Travel Rule. The highest concentration of gaps is in Holders and Presentations with 5 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 W3C Verifiable Credentials (VC) Data Model 2.0 and FATF Recommendation 16 - Virtual Asset Travel Rule?
The domain with the highest gap count is Holders and Presentations (5 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
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.