FATF’s 2026 virtual-asset update asks who is actually supervising, not who passed a law

The seventh targeted update on virtual assets measures whether Recommendation 15 is applied: licensing, examinations, and originator data that really moves with a transfer.

Stone courtyard in grey daylight
Standards · Virtual assets A European courtyard. The update is about supervision, not the building.

The standard is no longer the news

In July 2026 the Financial Action Task Force published its seventh targeted update on virtual assets and virtual-asset service providers. The public purpose of that series is blunt. Measure progress against Recommendation 15, and measure what is still missing. Recommendation 15 is the rule that pulled crypto firms into the same anti-money-laundering frame as banks: licensing or registration, supervision, and the travel rule, which says originator and beneficiary information has to move with a transfer. Passing the law was the easy milestone. It has been the easy milestone for years. The 2026 update is for readers who are tired of being told a jurisdiction is “aligned” because a statute exists. Faircroft reads these updates as a renewal tool, not as a thought piece. If you bank a VASP, or you bank a client who quietly is one, the question is no longer whether FATF has a standard. The question is whether the places that client serves have brought firms under that standard, and whether anyone has examined them. A licence PDF from one island does not cover customers booked in three others.

Supervision is the gap the reports keep naming

A jurisdiction can say the travel rule is in force and still have no evidence that exchanges send the data, store it, or refuse a transfer when the counterparty will not provide it. That is an examination gap. It does not show up in a press release about a new act. It shows up when a supervisor asks for a sample of real transfers and the firm produces a policy deck. The targeted updates exist so that this gap is visible between full mutual evaluations. Waiting for the next mutual evaluation before you tighten a VASP client is how you spend two years on a risk you were already shown. Unhosted wallets and stablecoin transfers sit at the edge of the same standard. FATF has already published separate work on both. They do not fall outside Recommendation 15 because the user holds the keys, or because the marketing word is “payment” rather than “crypto.” A 2026 onboarding that treats a stablecoin treasury as software, with no travel-rule control, is arguing with the standard. You can lose that argument in writing. You should not lose it by never having it.

What to ask the client

Three questions, in writing. Which jurisdictions do you serve, not which jurisdiction is on your letterhead. For each of those, is virtual-asset business under Recommendation 15 in force, and have you been examined. Show a sample of transfers where originator data moved, and a sample of what you did when the other side would not send it. If the client cannot show the sample, limit the client’s ability to move customer funds through your accounts until they can. A policy that mentions the travel rule is not a sample. Group compliance should keep one map of Recommendation 15 status for every country where a VASP client has customers. Local relationship managers will not maintain that map. They will maintain the relationship. Someone in London, or wherever the group actually decides, has to own the map and date it to the 2026 update, not to the 2021 one still sitting in the pack.

What banks get wrong about “technology clients”

Boards still let a client describe itself as a software vendor while the treasury movements look like exchange, custody, or transfer. The activity list is the test, not the client’s adjective. If the activity is in scope where it is performed, registration status can change the factual analysis overnight, including under regimes such as the BVI’s virtual-asset framework that have been spelling this out in public FAQs. Correspondent banks need the registration evidence in the account file as a primary document. A footnote in a pitch deck is how these files fail. Where a jurisdiction is still implementing, say so on the approval. Do not hide a partial regime inside the word “regulated.” Partial is a useful word. It justifies a lower limit and a shorter review cycle. It does not justify a speech about innovation.

What the update is not

It is not a list of banned coins. It is not a finding against any exchange named in your book. It is not a reason to exit every virtual-asset client in a single committee. It is a checklist against your own crypto client book, published so you cannot claim the gap was invisible. Faircroft would attach the 2026 update, your country map, and one redacted travel-rule sample to the next renewal. If you do not have the sample, the honest minute is that you do not have the control. Write that down before someone else does.

A renewal pack that would survive a supervisor

Date the FATF document July 2026 and call it the seventh targeted update, so nobody files it as “the crypto standard” without a year. Beside it, a table: client name, countries served, whether each country has brought VASPs under Recommendation 15, whether the client has been examined, and the date of the last travel-rule sample you saw. Empty cells are the point of the table. A full table of adjectives is how these packs lie. If a client serves customers in a jurisdiction that has the statute and no examinations, mark it partial and set the limit to match. If the client will not name the countries, the limit is zero until it will. Group boards should see that table once a year, not a slide that says virtual assets remain an emerging risk. Count the empty cells in the minute so the board sees the gap as a number. Emerging was a fair word in 2019. In 2026 the standard has been iterated seven times in this series alone. The residual risk is operational: data that does not move with the transfer, and supervisors who have not looked. Your own residual risk is the client you kept because the licence looked tidy and nobody asked for fifty transfers. Ask for them. Keep ten. If the ten do not show originator information, you have your answer, and it is better to have it in your minute than in someone else’s.