Argentina -- Travel Rule Implementation Regulatory Overview
Methodology
AI-generated synthesis from web search results.
Limitations
- AI-generated content -- not reviewed by human expert
- Source URLs not independently verified
Argentina has fully implemented and enforces the FATF Travel Rule as of 2026 for registered PSAVs (Proveedores de Servicios de Activos Virtuales), integrated into its national AML/CFT framework via Law 27.739 and UIF Resolution 49/2024, with full enforceability from 31 December 2025.[1]
Adoption and Effective Date
- Adopted through Law 27.739 (March 2024), which defines PSAVs, followed by phased registration in 2025 and UIF Resolution 49/2024.[1]
- Fully enforceable since 31 December 2025, with the first annual compliance audit cycle starting 1 January 2026; obligations are live and enforced in 2026.[1]
Threshold Amounts
- Search results do not specify a numerical threshold (e.g., $1,000 as in FATF recommendations); obligations apply to "qualifying crypto-asset transfers" and "higher-value activity" requiring systematic reporting, without explicit details on de minimis limits.[1]
Covered VASPs
- Applies to registered PSAVs with Argentina's CNV (Comisión Nacional de Valores), including domestic and foreign entities targeting Argentine users.[1][2]
- Mandatory CNV registration by staggered deadlines: individuals by 1 July 2025, Argentine entities by 1 August 2025, foreign entities by 1 September 2025 (per CNV Resolution 1058/2025); unregistered platforms face higher risks.[1][2]
- Traditional banks can provide crypto services from April 2026 under supervision.[1]
Technical Implementation Requirements
- Registered PSAVs must transmit and retain originator and beneficiary information for in-scope transfers, aligning with FATF standards; includes KYC, risk assessments, suspicious activity monitoring, and enhanced AML/CFT measures.[1][2]
- Strict treatment of unhosted wallets and inbound cross-border transfers; no mandated specific technology, but compliance is central to PSAV operations.[1]
Penalties for Non-Compliance
- Results do not detail specific penalties; non-compliance risks regulatory enforcement, as Argentina's framework is "comparatively strict," with potential future access limits on unregistered foreign VASPs.[1][2]
Note on limitations: Specifics on thresholds and penalties are absent from results; implementation aligns with FATF Recommendation 16 but lacks granular local thresholds here. For official texts, refer to sources like CNV or UIF sites (e.g., Law 27.739 via Argentine government portals).[1][2]
Source Data
The Travel Rule is **fully live and enforced** as a core PSAV compliance requirement, aligning with FATF standards.[1]
Key timeline: Law 27.739 (March 2024) defined PSAVs; phased CNV registration in 2025; **full enforceability of AML/CFT and Travel Rule obligations on 31 December 2025**; first compliance audit cycle from 1 January 2026.[1]
CNV Resolution 1058/2025 (March 2025) mandated VASP registration with staggered deadlines: individuals by 1 July 2025, Argentine entities by 1 August 2025, foreign entities by 1 September 2025.[2]
FATF globally recommends ~$1,000/€1,000, but jurisdictions vary or apply to all transactions; Argentina's strict framework implies broad coverage, including systematic reporting for higher-value activity, without a stated cutoff.[1][4]
Applies to **registered PSAVs** (domestic and foreign VASPs operating in or targeting Argentina users), post-mandatory CNV registration.[1][2]
Unregistered platforms face higher risks and lack oversight; traditional banks can offer crypto services from April 2026 under supervision.[1]
Strict on unhosted wallets and inbound cross-border transfers.[1]
VASPs must **collect, transmit, and retain originator/beneficiary information** for in-scope crypto-asset transfers.[1]
Includes **KYC, risk assessments, suspicious activity monitoring, and AML/CFT standards**; enhanced data sharing for Travel Rule-compliant transactions, even on international exchanges.[1][2]
Systematic reporting for higher-value activity; first annual audits from January 2026.[1]
No specific protocols (e.g., interoperability standards) detailed; aligns with FATF Recommendation 16 but faces global challenges like fragmented tech solutions.[1][4]
Sources & Attribution
This article was generated by Perplexity Sonar .
Primary Sources
Based on reporting by
Edit History
Related Content
This article is maintained by AI research workers and reviewed by human editors. Learn about our methodology →