出典確認済みリサーチ: FATF 2026 Virtual Assets

Decision Matrix

Source Map

• FATF: Seventh Targeted Update on Implementation of the FATF Standards on Virtual Assets/VASPs (fatf-2026-targeted-update)
• FATF: The FATF Recommendations (fatf-recommendations)
• FATF: FATF launches public consultation on guidance to increase payment transparency (fatf-r16-consultation)
• FATF: Updated Guidance for a Risk-Based Approach to Virtual Assets and Virtual Asset Service Providers (fatf-va-vasp-guidance)
• Bitpanda Helpdesk: Withdraw cryptocurrencies (bitpanda-withdraw-crypto)

Control Notes

1. Standard layer

Standard layer is the part of the decision where a public source has to become an operating rule. In this package, it means FATF materials describe international standards and implementation gaps. The useful action is to avoid translating FATF language into a platform guarantee. The unresolved edge is local legal implementation, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, standard layer should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material. The record can stay simple: the official source URL, the date checked, the product or network under review, and a non-secret note describing why the next step is acceptable. Screenshots should avoid balances, identity documents, tax identifiers, API keys, recovery phrases, private keys, passphrases, verification codes and support-ticket private data.

2. VASP scope

VASP scope is the part of the decision where a public source has to become an operating rule. In this package, it means Travel Rule obligations depend on VASP and jurisdiction context. The useful action is to identify whether both sides are VASPs or a self-hosted wallet is involved. The unresolved edge is counterparty classification, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, vasp scope should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.

3. Data request

Data request is the part of the decision where a public source has to become an operating rule. In this package, it means platforms may request recipient or wallet-host information. The useful action is to prepare required beneficiary fields without publishing private data. The unresolved edge is jurisdiction-specific field list, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, data request should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.

4. Implementation gap

Implementation gap is the part of the decision where a public source has to become an operating rule. In this package, it means FATF reports progress and remaining gaps at the same time. The useful action is to treat absence of a request as unknown rather than non-applicability. The unresolved edge is platform enforcement timing, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, implementation gap should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.

5. Deadline framing

Deadline framing is the part of the decision where a public source has to become an operating rule. In this package, it means R.16 consultation discusses implementation guidance toward 2030. The useful action is to track guidance status before relying on new rules. The unresolved edge is final guidance wording, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, deadline framing should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.

6. User impact

User impact is the part of the decision where a public source has to become an operating rule. In this package, it means Travel Rule controls can affect withdrawals, holds or information requests. The useful action is to record non-secret evidence for transfer review. The unresolved edge is support response during false positives, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

For an operator, user impact should be recorded before funds, account access, wallet recovery, API order flow, document exports, tax records, whitelist changes, chain transfers, event-contract trades or tokenized-asset decisions become material.

7. Stop rule

Stop rule is the part of the decision where a public source has to become an operating rule. In this package, it means a transfer should stop when counterparty data or jurisdiction scope is unclear. The useful action is to pause until venue-specific instructions are current. The unresolved edge is future rule amendments, so this article does not convert that uncertainty into a promise, ranking, reward, approval, recovery guarantee, safety claim or future-availability claim.

Known Unknowns

• local legal implementation
• counterparty classification
• jurisdiction-specific field list
• platform enforcement timing
• final guidance wording
• support response during false positives
• future rule amendments

Practical Takeaway

The safest version of this article is the one that stays boring and exact. FATF's 2026 virtual-assets materials frame Travel Rule implementation as a jurisdiction and VASP compliance gap, not a user-facing guarantee that every exchange transfer will carry the same data, timing or support outcome. FATF's July 2026 targeted update says jurisdictions have continued progress on virtual-asset risk assessments, regulatory approaches, licensing or registration, Travel Rule implementation and supervisory or enforcement action, while the same update is explicitly about remaining gaps. FATF's Recommendations page says the Recommendations were amended in June 2026, and its R.16 consultation discusses payment-transparency guidance for implementation by 2030. The decision outcome is to map whether a user's transfer touches a regulated VASP, self-hosted wallet, counterparty data request, jurisdiction gap or platform-specific hold before treating Travel Rule language as settled operational certainty. The user outcome is a clearer next inspection step, not a promise that a platform, API, transfer route, report, market contract or tokenized asset will work under every future condition.