A token issuer expanding into Latin America discovers that Mexico's regulatory framework for digital assets sits inside a broader fintech statute – and that the authorisation path depends entirely on whether the activity qualifies as electronic payment, exchange or custody. Operating without the right classification exposes the business to enforcement action, frozen banking rails and the loss of correspondent relationships that took months to build. The question turns on how the Ley Fintech (Fintech Law) defines virtual assets and which activities trigger authorisation by the Comisión Nacional Bancaria y de Valores (CNBV), Mexico's banking and securities regulator.
Mexico introduced its Fintech Law in 2018, making it one of the first jurisdictions in Latin America to legislate comprehensively for fintech activity – including a category called instituciones de fondos de pago electrónico (electronic payment funds institutions, or IFPEs) and instituciones de tecnología financiera (fintech institutions, or ITFs). The law recognises virtual assets (termed activos virtuales) as a regulated category distinct from fiat electronic money. Businesses that custody, exchange or facilitate payment using virtual assets may require CNBV authorisation, subject to secondary regulation that has evolved in stages since the framework took effect. For an operator considering Mexico, the analysis begins with the legal perimeter, moves to the specific instrument needed for the planned activity, and ends with the cross-border reality that many digital-asset businesses face: where the entity sits, where users are, and where banking lives rarely align.
This page sets out the authorisation route under Mexico's Fintech Law as it applies to digital assets, the classification logic that determines which licence you need, the practical constraints that shape the timeline, and the cross-border factors that influence whether Mexico is the right domicile for your build. It is written for general counsel and founders at exchanges, custodians and token issuers who already understand crypto mechanics and need the legal answer.
What is the Fintech Law and how does it treat digital assets?
The Ley para Regular las Instituciones de Tecnología Financiera (Fintech Law) is Mexico's framework for regulating technology-driven financial services. It defines two main categories of regulated institution: IFPEs, which issue and manage electronic payment funds, and ITFs, which extend credit through digital channels. For digital-asset operators, the key concept is the definition of activos virtuales: representations of value recorded electronically, used as a medium of exchange or investment, and transferred peer-to-peer without requiring a traditional intermediary. The law explicitly excludes representations that qualify as securities or fiat currency.
Crucially, the framework distinguishes between virtual assets permitted for public offering (determinados) and those restricted to qualified or institutional investors. The CNBV publishes a list of authorised virtual assets – at the time of writing, that list has not been populated with any tokens beyond certain stablecoins in testing environments, creating a structural constraint for businesses planning retail operations. Secondary regulation issued by the Banco de México (Banxicode) and the CNBV governs custody obligations, anti-money-laundering controls and disclosure. The result is a licensing regime that is comprehensive on paper but limited in practical implementation.
In our cross-border practice, we see operators approach Mexico for three reasons: access to the Latin American user base, the existence of a formal legal framework, and the perception that an authorised entity carries more weight with regional banking partners. The reality is more textured. The framework provides legal certainty for the activities it permits, but the narrow universe of authorised tokens and the CNBV's cautious approach to new authorisations mean that the route is viable primarily for payment-focused or institutional-custody models, not for broad retail exchange activity.
Who needs CNBV authorisation for crypto activity in Mexico?
CNBV authorisation is required if your activity falls within the regulated perimeter: issuing or managing electronic payment funds denominated in virtual assets, or operating as a trading platform that facilitates exchange between virtual assets and fiat or between different virtual assets. The threshold is functional. If the business custodies user funds, matches orders or facilitates settlement, it is performing a regulated activity. The legal question is whether that activity is carried out in Mexico or is merely accessed by Mexican users from an offshore platform.
The CNBV takes a territorial view: an entity with a physical presence in Mexico, Mexican employees handling operations, or a business model that targets Mexican residents is operating in Mexico for licensing purposes. A pure offshore exchange with no local establishment, no Mexican bank account and no active marketing in Mexico typically falls outside the perimeter – but loses the ability to bank locally or form partnerships with Mexican financial institutions. Operators we advise often discover this constraint when a correspondent bank closes the account of an offshore SPV that was facilitating MXN settlement for what the bank assessed as a Mexico-facing service.
Common scenarios that trigger authorisation: a custodian holding virtual assets on behalf of Mexican users; an exchange allowing MXN-to-crypto or crypto-to-crypto trades where one leg is a determinado asset; a payment processor converting crypto to fiat for merchant settlement in Mexico. Activities that generally do not trigger authorisation: providing software tools or API access without custody; publishing price data or market information; offering advisory services on tokenomics or blockchain implementation. The analysis is fact-specific and turns on where control, custody and settlement occur.
Is the activity classified as IFPE, ITF or exempt?
The first branching question is whether the business is issuing or managing electronic payment funds (which points to an IFPE authorisation) or operating as a trading platform (which may fall under a separate regime or require a specific authorisation tied to the exchange function). The Fintech Law does not use the term "virtual asset service provider" in the way MiCA or other regimes do; instead, it adapts the existing IFPE and ITF structures to accommodate digital-asset activity.
An IFPE structure suits a business that issues a stablecoin or manages a wallet holding determinado assets for payment purposes. It does not naturally fit a pure exchange that does not issue tokens or hold balances for payment as opposed to trading. For exchange activity, the CNBV has signalled that a variant authorisation or a separate regime may apply, but at the time of writing the detailed rulebook for exchange operators remains a work in progress. This creates a structuring challenge: the law is clear that the activity is regulated, but the precise instrument and process are not yet fully operationalised for all business models.
Exempt activities include technology provision (building a blockchain, issuing non-financial NFTs, providing wallet software without custody), brokerage that does not involve holding client assets, and certain institutional-only services where the counterparties are all qualified investors and the activity does not involve retail public offering. The exemption turns on the absence of custody and the nature of the client base. A business that moves from B2B institutional service to consumer-facing custody crosses the regulatory line and must seek authorisation.
What does the CNBV authorisation process involve?
The CNBV authorisation process for a fintech institution follows a staged approach. The applicant files a formal request with detailed documentation covering the business model, technology architecture, compliance and risk-management frameworks, financial projections, and the backgrounds of directors and key personnel. The regulator conducts a preliminary review, issues observations, and schedules meetings to clarify points of uncertainty. Once satisfied, the CNBV grants authorisation subject to conditions, which may include restrictions on the virtual assets the institution may handle, caps on transaction volumes during a pilot phase, and specific reporting obligations.
The timeline for CNBV authorisation is difficult to generalise and depends on the complexity of the model, the completeness of the filing, the regulator's internal workload and the novelty of the proposed activity. Applicants should expect a process measured in quarters, not weeks. The lack of a published list of determinado assets beyond pilot cases means that applications involving a broad range of tokens face additional scrutiny and may be invited to submit a pilot proposal for a narrower scope before full authorisation is considered.
In practical terms, the preparation phase – assembling the compliance manuals, the AML programme, the technology and security documentation, and the financial model – typically takes longer than the formal regulatory review. For a business coming from an offshore structure with no prior Mexican regulatory relationship, building the internal capability to meet CNBV expectations is the long pole. Operators we have worked with in comparable regimes allocate several months to preparation before filing, treating the application as the output of that internal build-out rather than the start of the process.
The timeline above describes a greenfield application. If your entity already operates elsewhere and is seeking to add a Mexican subsidiary or branch, the cross-border compliance stack – ensuring that AML, data-protection and cybersecurity controls meet both home and Mexican standards – becomes the critical workstream. For a scoped timeline based on your structure and the assets you intend to handle, contact OBOLUS at info@oboluslaw.com.
What are the capital and operational requirements?
The CNBV sets minimum capital requirements for authorised institutions, varying by the nature and scale of the activity. The capital base must be maintained throughout the life of the authorisation and is subject to ongoing supervision. The specific figures and any tiered structure depend on whether the institution is an IFPE or falls under another category, and whether it handles only determinado assets or a broader range. Because the detailed capital tables are subject to secondary regulation that continues to evolve, firms at the structuring stage should obtain current figures directly from the regulator or from counsel familiar with recent authorisations.
Operational requirements include segregated client-asset accounts, cybersecurity and business-continuity plans meeting Banxicode standards, ongoing AML and CFT controls aligned with Mexican anti-money-laundering law (which implements FATF recommendations), and regular reporting to the CNBV on transaction volumes, client numbers, compliance incidents and financial condition. The institution must appoint a compliance officer and a technology officer, both subject to CNBV approval. Directors and significant shareholders undergo background checks.
Technology expectations are detailed. The CNBV requires documentation of the custody architecture, the key-management approach, the transaction-monitoring system and the disaster-recovery plan. For custodians, the expectation is that private keys are held in a manner that prevents single points of failure and that client assets are segregated from the institution's proprietary holdings. The regulator may request a demonstration or a third-party audit of the technology stack before granting final authorisation. These requirements align Mexico with the expectations seen in other flagship regimes, but the documentation burden is heavier than in some offshore centres.
How does the Mexico structure interact with cross-border operations and banking?
A CNBV-authorised entity gains legal standing in Mexico and access to the local banking system – a significant advantage given that Mexican banks are otherwise reluctant to serve offshore crypto businesses. The authorisation also allows the institution to market its services to Mexican residents without the legal ambiguity that offshore operators face. However, the structure does not automatically solve the cross-border banking challenge. Mexican banks still assess crypto clients on a case-by-case basis, and correspondent banks outside Mexico may apply their own restrictions regardless of the local authorisation.
For operators serving users across Latin America, a single Mexican entity is rarely sufficient. Licensing and banking must be mapped jurisdiction by jurisdiction. A Mexican IFPE can serve Mexican users with legal certainty, but serving Colombian, Brazilian or Argentine users from the same entity requires analysis of whether those jurisdictions treat the activity as a cross-border service or as local activity requiring separate registration. In our practice, clients typically structure a hub entity in Mexico or another regional centre and then add local registrations or partnerships as user volumes in each country justify the cost.
Tax is another layer. Mexico taxes worldwide income of resident entities and source income of non-residents. A Mexican subsidiary of an offshore parent must manage transfer pricing, withholding on intra-group payments, and VAT on service fees. Digital-asset transactions are not exempt from VAT under current law, meaning that the tax treatment of crypto-to-fiat and crypto-to-crypto trades must be analysed with a local tax adviser. The interaction between the tax position and the regulatory structure – what portion of revenue is booked in Mexico versus in a holding jurisdiction – shapes the ultimate cost of the build.
What are the common mistakes when structuring for Mexico?
The first mistake is assuming that a CNBV authorisation is a regional passport. It is not. Each Latin American jurisdiction has its own regime, and while a Mexican licence may carry reputational weight with banking partners, it does not grant a legal right to operate in other countries. Operators who skip the jurisdiction-by-jurisdiction analysis often discover compliance gaps after launch, when a local regulator issues a cease-and-desist or a bank closes an account because the structure was not aligned to the user footprint.
A second common error is underestimating the constraint created by the narrow list of determinado assets. A business planning to offer a wide range of tokens to retail users will find that most of its intended product set is not yet authorised for public offering in Mexico. Attempting to launch with an incomplete product or pivoting to an institutional-only model mid-process wastes time and capital. The analysis must start with the asset universe and work backward to the viable business model, not the other way around.
A third mistake is treating the authorisation as the finish line. Ongoing compliance – reporting, audits, staff training, system updates, regulator liaison – is a permanent operational cost. Institutions that budget for the application but not for the compliance function find themselves unable to meet the regulator's expectations and may face supervisory action or even withdrawal of authorisation. The discipline required to maintain a Mexican licence is closer to running a regulated financial institution than to operating a pure technology business, and the team must be built accordingly.
How does Mexico compare with other licensing options for a regional build?
Mexico offers a formal legal framework, access to local banking and the ability to serve a large domestic market – advantages that matter for operators prioritising Latin America. Compared to offshore centres like the BVI or Cayman, Mexico imposes higher capital and operational requirements but delivers stronger regulatory credibility and better banking access. Compared to jurisdictions like Lithuania or Malta under the MiCA transition, Mexico is less established for cross-border digital-asset activity and the narrow authorised-asset list limits product flexibility.
For a business targeting the broader Latin American region, the choice often comes down to whether the Mexican user base alone justifies the cost of a local entity, or whether a lighter offshore structure with correspondent banking is sufficient. Operators with significant MXN flows, partnerships with Mexican financial institutions or plans to expand into remittances and payment processing typically find that the Mexican licence is worth the investment. Operators focused on crypto-to-crypto trading with a user base spread across multiple countries often choose a different hub and treat Mexico as a later-stage add-on.
The CNBV's cautious approach means that Mexico is not the fastest route to market for a crypto business. It is, however, one of the most credible in the region once the authorisation is in place. The decision turns on the operator's risk appetite, the importance of local banking, and the timeline to revenue. For a comparative view of how the Mexico route stacks up against other licensing options in the context of your user base and business model, write to info@oboluslaw.com.
Self-assessment: is a Mexico structure right for your build?
Consider a Mexico-domiciled entity if: your user base is concentrated in Mexico or you are planning MXN-denominated payment or remittance services; you need access to Mexican banking and are willing to meet the capital and compliance expectations that come with a CNBV authorisation; your product involves only determinado assets or you are prepared to launch with a restricted asset set and expand as the regulator's list grows; you have the operational capability to maintain ongoing reporting, audits and regulator liaison at the standard expected of a licensed financial institution.
A Mexico structure may not be optimal if: your user base is distributed across Latin America with no particular concentration in Mexico; your product requires a broad universe of tokens and you cannot launch profitably with a restricted set; you are optimising for speed to market and cannot afford a multi-quarter authorisation process; your business model is B2B or institutional-only and does not require local banking or retail-facing authorisation. In these cases, an offshore entity with selective in-country registrations as user volumes justify them may be more efficient.
The cross-border factors always matter. Where is your founding team? Where will you bank? Where do your institutional counterparties sit? If the operational centre of gravity is outside Mexico, forcing a Mexican domicile for the holding entity may create tax and governance complexity without delivering proportionate benefit. The licensing question and the structuring question must be answered together, not in sequence.
Related at OBOLUS
- Licensing & Registration for Digital-Asset Businesses – how we map the licence stack across operating, custody and payment layers before you commit capital.
- VARA Licence Application in Czech Republic – the MiCA CASP authorisation route in a newer EU member state and how it compares with mature hubs.
- Governance Expectations for Boards of Licensed VASPs – what regulators in flagship jurisdictions expect from directors and how that shapes board composition.
FAQ
How long does a crypto licence take to obtain?
The timeline for a CNBV authorisation in Mexico is measured in quarters and depends on the completeness of the application, the complexity of the business model and the regulator's workload. Preparation – building the compliance framework, the technology documentation and the financial model – typically takes as long as or longer than the formal review. For a business coming from an offshore structure with no prior Mexican regulatory relationship, budget several months for the internal build-out before filing. Timelines in other flagship jurisdictions vary widely; an EU MiCA CASP authorisation or a Singapore MAS licence follows a different cadence. A scoped timeline depends on your structure and planned activities.
Which jurisdiction suits my crypto business?
The choice of jurisdiction depends on where your users are, where you can bank and what your business model requires in terms of regulatory credibility versus speed to market. Mexico offers formal legal standing and local banking access for operators targeting the Mexican market or broader Latin America, but imposes capital and operational requirements closer to a traditional financial institution. Offshore centres like the BVI or Cayman are faster but offer weaker banking access. EU jurisdictions under MiCA provide passporting but demand higher compliance investment. The analysis must account for the user footprint, the banking stack, the tax position and the operational centre of gravity. There is no universal best jurisdiction.
Do I need a separate custody licence?
Whether custody is a separate licence or is covered within a broader authorisation depends on the jurisdiction. In Mexico, custody of virtual assets as part of an IFPE or exchange function is regulated under the Fintech Law, and the CNBV authorisation addresses custody within that context. In other regimes – MiCA in the EU, for example – custody is a distinct service under the CASP framework and must be included in the authorisation scope if you plan to hold client assets. The custody function always attracts heightened regulatory expectations around key management, segregation and cybersecurity, regardless of whether it is a standalone licence or a service category within a broader authorisation. The analysis starts with your business model and works out to the applicable regime.
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 capital, because a single offshore licence is rarely enough to serve clients globally. Operators we advise routinely discover that the jurisdiction they chose for formation is not the jurisdiction where they can bank or where their users sit, and we help them build the multi-entity structure that aligns legal, banking and tax before launch, not after enforcement. To discuss your situation, contact info@oboluslaw.com.
By Aisha Tan, Licensing & Jurisdictions Analyst – advising on VASP authorisation routes and cross-border licensing strategy for digital-asset businesses across Latin America, the EU and Asia-Pacific.
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.