
Executive summary
This page provides an overview of crypto-asset transfer regulation and Travel Rule requirements in Argentina. It is intended for Virtual Asset Service Providers operating locally (known as PSAVs), financial institutions, and compliance teams interacting with the Argentine market.
Following the adoption of Law 27.739 and subsequent regulatory measures, Argentina has formally integrated virtual asset service providers into its national AML/CFT framework. As of 2026, Travel Rule obligations are fully live and enforced, forming a central component of PSAV compliance requirements and Argentina’s alignment with international standards.
This content is provided for informational purposes only and does not constitute legal advice.
Regulatory landscape overview
Argentina’s crypto regulatory framework represents a significant shift from a previously fragmented environment toward a structured, FATF-aligned regime. Virtual asset activity is now explicitly regulated within national AML/CFT laws, with defined registration, reporting, and information-sharing obligations.
Key characteristics of the Argentine approach include:
Formal legal recognition of PSAVs under national law
Integration of Travel Rule requirements into AML supervision
Coordination between financial, AML, and tax authorities
Use of dynamic thresholds tied to national economic indicators
The framework aligns with Financial Action Task Force (FATF) standards and reflects Argentina’s broader effort to strengthen financial integrity and regulatory credibility.
Supervisory and regulatory authorities
Travel Rule compliance in Argentina is overseen through a multi-authority structure:
Comisión Nacional de Valores (CNV): Maintains the PSAV registry and oversees licensing and market entry
Unidad de Información Financiera (UIF): Primary AML/CFT authority responsible for enforcing Travel Rule obligations and receiving reports
Banco Central de la República Argentina (BCRA): Oversees banking participation and integration of crypto services within the financial system
Administración Federal de Ingresos Públicos (ARCA): Monitors transaction activity for tax and reporting purposes
This structure reflects Argentina’s emphasis on coordinated supervision across AML, financial, and tax domains.
Travel Rule status in Argentina
The Travel Rule is fully implemented and enforced for registered PSAVs under Law 27.739 and UIF Resolution 49/2024.
Under the Argentine framework:
Travel Rule obligations apply to qualifying crypto-asset transfers conducted by registered PSAVs
Originator and beneficiary information must be transmitted and retained for in-scope transactions
Systematic reporting obligations apply for higher-value activity
Argentina’s approach is considered comparatively strict, particularly in its treatment of unhosted wallets and inbound cross-border transfers.
Timeline and key milestones
March 2024: Law 27.739 establishes the legal definition of PSAVs
2025: Phased registration of domestic and foreign PSAVs with the CNV
31 December 2025: Full enforceability of AML/CFT and Travel Rule obligations
1 January 2026: First annual audit cycle for Travel Rule compliance begins
April 2026: Regulatory changes allow traditional banks to provide crypto services under supervision
Thresholds and scope
Argentina applies a dynamic threshold model linked to national wage indicators.
Threshold: Six times the Salario Mínimo, Vital y Móvil (SMVM)
Aggregation: Transactions may be assessed cumulatively over defined periods
Systematic reporting: Transfers exceeding the threshold are subject to additional reporting obligations
This wage-indexed approach is distinctive and requires ongoing operational awareness.
Required data elements (high-level)
For in-scope transfers, Argentine regulations generally require information relating to:
The originator, including identifying details and national identifiers
The beneficiary, including identifying details and wallet or account identifiers
For Argentine residents, national tax identifiers may play a role in data reconciliation and reporting. Specific data elements are defined in regulation and UIF guidance and must be made available to authorities upon request.
Local nuances and interpretive considerations
Several features of the Argentine framework are particularly relevant for compliance teams:
Dynamic thresholds: Compliance systems must account for periodic changes to the national minimum wage
Tax alignment: Travel Rule data may intersect with tax reporting obligations
Audit intensity: Regulatory expectations emphasise documentation, traceability, and long-term record retention
These elements contribute to a compliance environment that is operationally demanding but clearly defined.
Self-custodied (unhosted) wallet considerations
Argentina applies a high-risk classification to transfers involving self-custodied wallets.
Additional verification measures may apply for transfers above the applicable threshold
Enhanced monitoring and screening of unhosted wallets is expected
Repeated or high-value interactions may trigger enhanced due diligence
This approach is more restrictive than in many jurisdictions and reflects UIF supervisory priorities.
Cross-border and interoperability considerations
Argentina adopts a comparatively strict stance toward cross-border Travel Rule enforcement.
Key considerations include:
Attempts to obtain required information for inbound transfers from non-compliant jurisdictions
Expectations that foreign PSAVs targeting Argentine users comply with local registration and data standards
Operational implications for international platforms serving Argentine customers
Interoperability and counterparty readiness are therefore critical for cross-border activity involving Argentina.
Indicative compliance readiness checklist
The following considerations are illustrative and non-exhaustive:
Active registration in the CNV PSAV registry
Appointment of a registered AML compliance officer
Ability to adapt to wage-indexed Travel Rule thresholds
Processes for handling unhosted wallet transfers
Record-keeping aligned with Argentine AML retention requirements
