An exchange serving Argentine users discovers that a planned expansion into local banking channels requires formal registration with the National Securities Commission. The registration obligation runs from the first peso-denominated settlement, not from the date the business decides to "go live" in Argentina. Without a clear read of the triggers, operators move funds, open accounts and sign partnerships before they understand that they are already inside the regulated perimeter.
Argentina's virtual asset service provider regime requires registration with the Comisión Nacional de Valores (CNV) for entities offering custody, exchange or payment services involving crypto-assets to or from Argentine residents. The registration process imposes disclosure obligations, capital maintenance expectations and ongoing compliance reporting, and it conditions access to the domestic banking system. For a business that already holds a VASP licence elsewhere, the Argentine requirement is a second, overlapping layer rather than a substitute.
This page sets out who must register, the categories of regulated activity, the application and compliance expectations, and the practical cross-border interactions that turn an apparently local registration into a structure and banking question. We address the timeline, the capital and AML posture that the CNV expects, and the common mistakes that stall applications or expose an operator to enforcement before registration completes.
Who must register under the Argentine VASP regime
Registration is mandatory for any entity that provides custody, exchange or transfer services for virtual assets to Argentine residents or that uses Argentine payment rails to settle virtual-asset transactions. The CNV's definition of a virtual asset follows the FATF standard: a digital representation of value that can be digitally traded or transferred and used for payment or investment purposes. The obligation applies whether the entity is incorporated in Argentina or operates from overseas with Argentine users.
The registration trigger is activity-based rather than incorporation-based. An entity incorporated in Switzerland that opens an Argentine bank account and accepts peso deposits for stablecoin purchases is inside the perimeter. A custody provider domiciled in the BVI that holds private keys for Argentine clients is inside the perimeter. The legal domicile of the service provider is relevant to enforcement reach, but it does not determine the registration obligation itself.
The CNV regime distinguishes between three registration categories: custody providers, exchange platforms and payment-service providers. A business that offers a combined exchange and custody service must register under both categories and comply with the requirements of each. There is no simplified category for small operators or for entities whose Argentine user base falls below a specified threshold. The regulatory framework applies from the first qualifying transaction.
In our cross-border practice, operators commonly assume that registration is required only after a material presence – an office, local staff or a marketing campaign. That assumption is incorrect. The CNV's interpretation turns on where the user sits, not where the entity markets or incorporates. A platform that never mentions Argentina in its terms but accepts signups from Buenos Aires and processes peso on-ramps is already subject to the registration requirement.
What activities trigger the registration requirement
Custody means the safeguarding of private keys or the provision of wallet services where the provider holds, directly or through a sub-custodian, the cryptographic keys necessary to transfer a user's virtual assets. Self-custody wallets – where the user holds the private key and the provider offers only software – fall outside the custody definition, but the moment the provider introduces a key-recovery service or a co-signing arrangement, the CNV reads it as custody.
Exchange services include operating a platform that matches buy and sell orders for virtual assets, whether the platform charges a spread, a commission or a flat fee per trade. The definition covers order-book exchanges, automated market makers (AMMs) run by a legal entity with identifiable management, and over-the-counter desks that quote prices and settle trades. Purely decentralised protocols with no legal operator typically fall outside the CNV's registration perimeter, but the line between a protocol and a platform turns on control, not on the label the project uses.
Payment services encompass the acceptance of virtual assets in payment for goods or services, the conversion of virtual assets to fiat for payment purposes, and the issuance of stablecoins or similar instruments that function as a means of payment. The payment-service category overlaps significantly with the exchange category where a service converts crypto to pesos as part of a checkout flow.
The CNV applies a substance-over-form test: the economic function of the service determines the category, not the terminology in the whitepaper or the marketing. A token issuer that describes its instrument as a utility token but accepts it in redemption for fiat or other crypto-assets may be classified as operating an exchange. An NFT marketplace that includes a secondary trading function with fiat settlement may be classified as an exchange platform.
The registration application process and indicative timeline
The application is filed with the CNV through its electronic portal. The required documentation includes the entity's certificate of incorporation and constitutional documents, proof of tax registration in the home jurisdiction, a business plan describing the services to be offered in Argentina, and detailed information on the directors, shareholders and beneficial owners. For entities incorporated outside Argentina, the application must include an apostilled power of attorney appointing a local legal representative with authority to receive official notices and to act on behalf of the entity in dealings with the CNV.
The CNV reviews the application for completeness, assesses the compliance framework that the applicant has put in place, and may request additional information on AML procedures, cybersecurity controls and fund-segregation arrangements. Where the applicant's home jurisdiction operates a VASP licensing or registration regime, the CNV may request confirmation of the applicant's status under that regime, but home-country authorisation does not exempt the applicant from Argentine registration.
The timeline from submission to registration approval varies according to the complexity of the business model and the quality of the initial filing. A straightforward custody-only application with complete documentation and a clear fund-segregation model typically progresses faster than a multi-service exchange application that requires clarification of settlement flows and counterparty risk. Operators we advise regularly see timelines in the range of several months from initial submission to formal registration, but a deficient filing can extend that period significantly.
During the review period, the applicant may not offer the regulated services to Argentine users. The CNV has made clear in recent guidance that registration is a prior authorisation requirement, not a notification-after-commencement process. Operating without registration exposes the entity to administrative penalties, including orders to cease activity and public warnings that make it difficult to secure banking relationships later.
Capital maintenance and financial-resource expectations
The CNV expects registered VASPs to maintain a level of capital and liquid resources adequate to the nature and scale of their Argentine operations. The specific capital figure varies by the category of service and by the volume of assets under management or the transaction throughput of the platform. The framework does not prescribe a uniform minimum capital applicable to all registrants; instead, the CNV assesses the adequacy of the applicant's capital on a case-by-case basis, taking into account the risks inherent in the business model.
For custody providers, the capital assessment focuses on the entity's ability to make clients whole in the event of a loss resulting from a security breach, operational failure or sub-custodian default. The CNV may require the custodian to hold professional-indemnity insurance covering cyber risk and errors-and-omissions exposure, with coverage limits proportionate to the value of assets under custody. Where the custodian uses a sub-custodian arrangement – for example, a third-party cold-storage provider – the CNV expects a clear contractual allocation of liability and evidence that the sub-custodian meets equivalent security standards.
Exchange platforms are expected to hold sufficient working capital to meet settlement obligations and to cover operational costs during periods of market stress. The CNV's review looks at the applicant's balance sheet, the liquidity of its assets, and the arrangements in place to segregate client funds from the platform's proprietary assets. Commingling of client funds with operational reserves is a common reason for the CNV to request restructuring before granting registration.
Payment-service providers face capital expectations that reflect the float they hold between the moment a user initiates a payment and the moment the payment settles. The capital requirement is conceptually similar to the approach taken in other payment-services regimes: the provider must hold enough liquid resources to honour redemption requests and to meet regulatory capital calls without interrupting service.
AML obligations and the Travel Rule under the Argentine regime
Registered VASPs are subject to Argentina's Anti-Money Laundering and Counter-Terrorist Financing framework, administered by the Unidad de Información Financiera (UIF). The obligations include customer due diligence (CDD), enhanced due diligence (EDD) for high-risk customers, transaction monitoring, suspicious-activity reporting and record-keeping for a minimum retention period. The UIF's guidance on virtual assets aligns broadly with FATF Recommendation 15, which treats VASPs as obliged entities equivalent to traditional financial institutions.
The Travel Rule – the requirement to pass originator and beneficiary information with a virtual-asset transfer – applies to Argentine VASPs for transactions above a specified threshold. The threshold and the technical standard for transmitting the required data are set by the UIF in coordination with the CNV. Operators that process cross-border transfers must ensure that their systems capture and transmit the originator's name, account identifier and geographic address, and the beneficiary's name and account identifier, in a format compatible with the receiving VASP's compliance infrastructure.
Compliance with the Travel Rule in practice requires either a direct integration with the counterparty VASP's compliance system or the use of a Travel Rule solution provider. Where the counterparty VASP is located in a jurisdiction that does not yet enforce the Travel Rule, the Argentine VASP must still collect and retain the required data, even if the counterparty does not reciprocate. Failure to comply with Travel Rule obligations exposes the VASP to administrative sanctions from the UIF and may result in the suspension of its CNV registration.
The UIF publishes periodic guidance on typologies and red flags specific to virtual-asset transactions. Registered VASPs are expected to incorporate that guidance into their transaction-monitoring rules and to update their risk assessments when the UIF issues new alerts. In our disputes practice, we have seen enforcement actions against VASPs that continued to process transactions for customers flagged in UIF alerts without conducting enhanced due diligence or filing a suspicious-activity report.
The banking and tax layers: how registration affects access to financial services
Registration with the CNV is a precondition for opening and maintaining Argentine bank accounts for business purposes in the crypto sector. Argentine banks apply a tiered risk-assessment process to VASP clients, and an unregistered entity is typically classified as unacceptable risk regardless of the quality of its AML controls or its licensing status in other jurisdictions. A registered VASP improves its risk profile but still faces bank-by-bank underwriting: registration demonstrates regulatory recognition, but it does not guarantee that any particular bank will accept the account.
The tax interaction is equally important. Argentine VASPs are subject to corporate income tax on profits derived from Argentine-source activities, and they must register with the Administración Federal de Ingresos Públicos (AFIP) for tax purposes. The tax treatment of virtual-asset transactions – whether a trade generates a capital gain or ordinary income, and whether a staking reward is taxable on receipt or on sale – follows general Argentine tax principles, but the AFIP has issued specific guidance addressing the characterisation of crypto-to-crypto exchanges and the timing of income recognition for mining and staking.
For a foreign entity operating in Argentina through a branch or a subsidiary, the question of permanent establishment arises: if the foreign parent provides services to Argentine users without a local legal presence, does it create a taxable presence in Argentina? The answer turns on the facts – the location of servers, the residence of employees, the point at which contracts are concluded – but CNV registration itself does not automatically create a permanent establishment. A careful structure separates the registered Argentine entity from the foreign parent's global operations, routing Argentine user activity through the local entity and keeping the parent's direct dealings with Argentine users to a minimum.
Operators we advise commonly underestimate the tax and banking sequencing. They file for CNV registration, obtain approval, and then discover that the bank account application takes as long as the registration process itself, or that the tax registration requires additional corporate steps that should have been completed before the CNV application. A coordinated approach – tax, banking and CNV registration planned as a single workstream – avoids the situation where one approval becomes useless because another piece is missing.
If your business model crosses the custody, exchange or payment categories, the capital and compliance stack needs to be pressure-tested before the CNV filing. The time to discover a structural deficiency is before the application, not in the third round of CNV questions. For a scoped assessment of your operating structure and a roadmap to Argentine registration, contact OBOLUS at info@oboluslaw.com.
Cross-border considerations: when an Argentine registration interacts with licences elsewhere
An entity that holds a VASP licence in Lithuania or a regulatory authorisation in Singapore and then expands into Argentina faces a multi-licence compliance burden. The Argentine registration does not replace or supersede the home-country licence; instead, the entity must comply with the requirements of both regimes. Where the requirements conflict – for example, if the home-country regulator mandates a particular custodial arrangement that the CNV considers inadequate – the operator must find a structure that satisfies both, or else ring-fence the Argentine business under a separate legal entity.
The question of passporting arises frequently. Under MiCA, a crypto-asset service provider authorised in one EU member state may passport its authorisation across the EU. Argentina does not participate in any comparable mutual-recognition framework, and it does not recognise home-country licences as a substitute for CNV registration. Even an entity authorised by ESMA or by a national competent authority under MiCA must register separately with the CNV if it offers services to Argentine users.
Data residency and cross-border data flows add a further layer. Argentina's data-protection framework requires that personal data of Argentine residents be handled in accordance with the country's privacy legislation, and cross-border transfers of personal data may require additional safeguards or contractual clauses. A VASP that processes Argentine user data on servers located outside Argentina must ensure that the data-export arrangements comply with Argentine law. The CNV may request evidence of data-protection compliance as part of the registration review.
For operators running a global platform with a single technology stack, the Argentine registration requirement can force a choice: build a separate instance of the platform for Argentine users, with data and funds segregated from the rest of the user base, or apply Argentine compliance standards globally. The former approach is cleaner from a regulatory perspective but more complex operationally; the latter approach simplifies operations but may impose higher compliance costs on non-Argentine users who do not require the same level of oversight.
Common mistakes that delay or derail an Argentine VASP application
The most frequent mistake is filing the application before the entity's AML and compliance documentation is complete. The CNV expects to see policies, procedures, risk assessments and evidence of staff training, not a statement that these will be developed "post-registration." An incomplete compliance framework triggers requests for information that extend the review period and signal to the CNV that the applicant is not ready to operate.
A second common issue is ambiguity about the business model. An applicant that describes its service as "facilitating peer-to-peer transactions" without specifying whether it holds user funds, controls private keys or matches orders will face repeated questions from the CNV. The application must set out clearly which of the three registration categories (custody, exchange, payment) apply, and it must describe the transaction flow from user deposit to user withdrawal in enough detail that the CNV can assess the risk points.
Operators frequently underestimate the importance of the local legal representative. The appointed representative must be an Argentine resident with authority to act for the entity in all dealings with the CNV, including receiving enforcement notices and responding to information requests. Appointing a representative who lacks decision-making authority or who is unavailable during business hours creates delays and, in some cases, a presumption that the entity is not genuinely committed to Argentine compliance.
A fourth mistake is launching marketing or user-acquisition activity in Argentina before registration is granted. The CNV monitors advertising and social-media campaigns, and it treats pre-registration marketing as evidence of unregistered operation. An operator that builds a user base before the registration is approved faces not only a compliance violation but also the practical problem of unwinding those user relationships or transferring them to a registered entity after the fact.
Enforcement posture and the penalties for operating without registration
The CNV's enforcement powers include the authority to issue cease-and-desist orders, to impose administrative fines and to refer cases to the public prosecutor for criminal investigation where the conduct involves fraud or money laundering. Operating a VASP without registration is classified as an administrative offense, and the penalty framework provides for fines calculated as a multiple of the annual revenue derived from the unregistered activity. The CNV publishes a list of entities that have been ordered to cease operations, and inclusion on that list makes it nearly impossible to secure banking or payment-processing services in Argentina.
In enforcement proceedings, the CNV applies a strict-liability standard: the fact that the operator was unaware of the registration requirement or believed that its home-country licence was sufficient is not a defence. The obligation to register is triggered by the activity itself, and ignorance of the law does not excuse non-compliance. For entities that self-report an inadvertent failure to register and cooperate with the CNV's investigation, the regulator has discretion to reduce penalties, but there is no automatic safe harbour for voluntary disclosure.
The interaction between CNV enforcement and criminal liability is significant. Where an unregistered VASP processes transactions that the UIF later identifies as linked to money laundering or terrorist financing, the individuals controlling the entity may face criminal charges in addition to the administrative penalties. Argentine prosecutors have brought cases against VASP operators on the basis that operating without registration constitutes a failure to comply with AML obligations, and that failure facilitated the laundering of illicit funds. A registration that the operator viewed as a bureaucratic formality becomes, in hindsight, the line between an administrative matter and a criminal investigation.
If a bank closed your account or a partnership stalled because of registration concerns, the path back into the market starts with understanding why the application failed or what the CNV saw that triggered concern. A second read of the structure and a revised filing can resolve the issue, but only if the analysis identifies the real objection. To map your route to CNV registration, write to info@oboluslaw.com.
How the Argentine regime compares for an inbound operator
Argentina's registration requirement is less onerous than a full VASP licence in jurisdictions like Singapore, Hong Kong or the UAE, but it is more complex than the notification-based regimes in some Central European markets. The CNV does not impose a prescribed minimum capital applicable to all categories, but its case-by-case assessment means that an applicant cannot predict its capital requirement in advance. That uncertainty complicates financial planning, particularly for operators seeking to allocate a fixed budget across multiple jurisdictions.
The timeline is competitive by regional standards. A well-prepared application with complete documentation and a straightforward business model can progress to registration within a timeframe comparable to other South American regimes. The CNV's electronic filing system is functional, and the regulator provides reasonably clear guidance on the information it expects at each stage. Where the process slows, it is usually because the applicant's submission was incomplete or because the compliance framework was underdeveloped.
From a banking and tax perspective, Argentine registration does not solve the banking problem by itself – it is a necessary condition but not a sufficient one. Operators still face bank-by-bank underwriting, and the availability of banking services depends as much on the bank's risk appetite and the operator's AML controls as on the fact of registration. For tax, the Argentine corporate-tax rate and the complexity of the VAT treatment of crypto transactions make Argentina a more expensive jurisdiction to operate in than some alternatives, but the access to a large and growing user base justifies the cost for many operators.
The cross-border interaction is Argentina's distinguishing challenge. An operator with licences in multiple jurisdictions must build a structure that keeps Argentine user data and funds ring-fenced from other markets, that satisfies the CNV's expectations on fund segregation and that accommodates the travel-rule and AML reporting obligations without breaking the global compliance architecture. That structure is achievable, but it requires planning at the entity level, not as an afterthought once the business is running.
When to engage counsel on an Argentine VASP registration
The decision to register in Argentina should be informed by a clear view of the user base, the revenue the Argentine market represents and the banking and tax costs of maintaining a registered operation. For an operator whose Argentine users account for a material share of global volume, registration is unavoidable. For an operator testing the market with a small pilot, the cost and complexity of registration may outweigh the benefit, and a more prudent approach is to geo-block Argentine users until the business is ready to commit to full compliance.
Counsel is useful at three points in the process. First, at the structuring stage, before the first Argentine user signs up: the question is whether the planned service triggers the registration requirement, and if so, whether the business should establish a local subsidiary or operate through a branch. Second, during the application, when the CNV requests clarification or additional information: the quality of the response determines whether the application progresses or stalls. Third, if the operator is already serving Argentine users without registration and needs to assess enforcement risk and design a remediation plan.
The remediation scenario is the most time-sensitive. An operator that discovers mid-operation that it should have registered faces a choice: file an application immediately and disclose the prior unregistered activity, or continue operating and hope the CNV does not notice. The former approach carries short-term cost and reputational risk, but it limits the downside to an administrative penalty. The latter approach risks a cease-and-desist order, public enforcement and the loss of banking relationships that cannot easily be restored. Operators who consult counsel at this point typically choose disclosure and remediation, but they underestimate how much reputational and operational continuity they preserve by getting ahead of the enforcement curve.
Related at OBOLUS
- Licensing & Registration for Digital-Asset Businesses – the global licence map and the questions every operator faces when choosing a home base.
- Crypto Exchange Setup in Jersey – how Jersey's regime compares on timeline, capital and the banking interaction.
- Founder Relocation and Tax in Czech Republic – structuring personal tax residence when the business operates across borders.
FAQ
How long does a crypto licence take to obtain?
Timeline depends on jurisdiction and the complexity of the application. In Argentina, a complete VASP registration application with well-prepared compliance documentation typically progresses over several months from submission to approval. Deficiencies in the initial filing or requests for additional information extend the process. Fast-track regimes in some European and Middle Eastern hubs can deliver authorisation in shorter windows, but they impose higher capital and operational standards. The timeline is never the sole decision factor – access to banking, the tax environment and the user base matter as much as speed.
Which jurisdiction suits my crypto business?
The answer turns on where your users sit, where you can bank and where the tax burden is tolerable. A custody business serving institutional clients needs a jurisdiction with strong legal certainty on digital-asset property rights and access to correspondent banking – Malta, Switzerland or Singapore. An exchange targeting retail users in Latin America needs a hub that supports peso or real on-ramps and accepts the AML risk – often a local licence in the target market rather than a single offshore base. There is no universal "best" jurisdiction; the right choice depends on the operating model, the risk appetite and the banking reality.
Do I need a separate custody licence?
In most leading regimes, custody is a regulated activity distinct from exchange or payment services. If you hold users' private keys or offer wallet services where you control the ability to move funds, you need either a custody-specific licence or a multi-category authorisation that covers custody. Self-custody wallets – where the user holds the key and you provide only software – typically fall outside the licensing perimeter, but the line is substance-based. The moment you introduce key recovery, multi-signature arrangements or custodial staking, you cross into regulated custody territory. Argentina, the EU under MiCA, Singapore and the UAE all treat custody as a separate regulated function.
About OBOLUS
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. We map the licence stack across operating, custody and payment layers before you commit, and we structure licensing, banking and tax as one mandate rather than three disconnected workstreams. To discuss your situation, contact info@oboluslaw.com.
By Aisha Tan, Licensing & Jurisdictions Analyst – Aisha leads OBOLUS's work on VASP registration and cross-border licensing strategy across Latin America, Europe and the Middle East.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.