The travel rule is being rewritten for every cross-border payment, not just crypto
Blog post from Didit
Excluded from normalized aggregate trends after staff review: 3056 posts were attributed to March 2026; 671 shared March 14, 2026. The preceding six-month median was 13.5 posts.
Review evidence: 3,056 posts in March 2026; 671 shared March 14, 2026; preceding six-month median 13.5. Reviewed August 9, 2026.
This company's pages remain public, but its content is excluded from normalized aggregate trends. Unfiltered raw trends and advanced filtering are available to Accelerate and Lead accounts.
The Financial Action Task Force revised Recommendation 16, its cross-border payment-transparency standard often called the Travel Rule in virtual-asset contexts, in June 2025 to reflect the broader role of fintechs and digital payment systems. Once implemented nationally, the changes will require peer-to-peer cross-border payments above USD/EUR 1,000 to include the sender’s or relevant party’s name, address, and date of birth, while defining the payment chain as beginning with the institution that receives a customer instruction. The revisions also call for technologies that reduce fraud and payment errors, including recipient banking-information verification, while retaining an exemption from full requirements for card payments used to purchase goods or services. FATF expects countries to be ready by the end of 2030, and an October 2025 assessment annex explains how compliance will be reviewed in mutual evaluations. Draft implementation guidance was consulted on from June to August 2026, focusing on misdirected payments, financial inclusion, digital wallets and mobile money, and data-protection issues. The changes do not directly bind firms until adopted by individual jurisdictions, but they may require payment providers to ensure onboarding records contain accurate, structured, transmissible identity and address information.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.