Cryptoassets Regulatory Intelligence cryptoassets.gi
MX · run crypto-2026-08-05 v13.3.0
content: ai_generated 9 sources retrieved model claude-sonnet-5 ·

Mexico

MX schema crypto-v2.0.0 trajectory: not recordedin transitionoverlaps: FIM, WPM

Last updated · 8 categories · 14 sourced findings · 9 sources in the cumulative register

8Categoriesbaseline.
14Findings.claims[]
0Tier-1 sourcesrun_metadata.t1_source_count
Confidence mix (sums to 8 rendered categories; click to filter)
No categories moved this cycle.

Jurisdiction brief

No content recorded at this JID path.

8 of 8 categories
Signal
Density

Selections OR within a group, AND across groups. Press / to search.

#

Mexico's Ley para Regular las Instituciones de Tecnología Financiera (Ley Fintech, 2018) is the only statute that expressly names virtual assets, but it operates as a restrictive gate rather than a full VASP licensing regime: fintech institutions (ITFs) may only operate with virtual assets that Banco de México (Banxico) affirmatively determines via general provisions, and must obtain Banxico's prior authorization to do so. In practice Banxico has not exercised this authorization power to permit ITFs to deal in cryptoassets, and a joint 2021 Banxico/CNBV/SHCP communiqué (reaffirmed in Banxico's December 2025 year-end report) bars regulated banks and fintechs from offering virtual-asset services to customers. Non-bank exchanges (e.g., Bitso) operate outside the ITF authorization perimeter and are treated instead as AML-obligated entities. CNBV has also shown willingness to grant case-by-case no-action relief (Resolution P090/2024) where a token does not meet the Securities Market Law's definition of a security.

Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.

No periodic updates recorded against this sub-brief.

Sources and findings (3)
  1. T?source not recordedM5bindingin force
  2. T?source not recordedM5bindingin force
  3. T?source not recordedM3bindingin force

#

Mexico lacks a comprehensive statutory taxonomy for token types. The Ley Fintech references only the broad category 'activos virtuales' (virtual assets) without sub-classifying tokens by function. CNBV instead applies the existing Securities Market Law investment-contract test on a case-by-case basis (as in the Etherfuse no-action resolution) to decide whether a given token requires securities authorization. Peso-referenced stablecoins such as Bitso/Juno's MXNB have launched without a dedicated stablecoin classification or issuance-authorization regime.

Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.

No periodic updates recorded against this sub-brief.

Sources and findings (2)
  1. T?source not recordedM3bindingin force
  2. T?source not recordedM4non-binding

#

No Mexican statute or regulator guidance was identified that specifically addresses staking, DeFi lending, DEX operation, mining, node operation, validator activity, or tokenization as distinct regulated categories. On-chain activities fall into the same general 'healthy distance' policy gap as other virtual-asset dealings, with no dedicated licensing, disclosure, or prudential treatment located in the research pass.

Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.

No periodic updates recorded against this sub-brief.

Sources and findings (1)
  1. T?source not recordedM2non-binding

#

Mexico has no dedicated stablecoin statute governing issuance authorization, reserve requirements, redemption rights, disclosure, or systemic designation. Banxico's December 2025 year-end report explicitly cited stablecoin-related risks among its reasons for maintaining a 'healthy distance' between virtual assets and the financial system, signaling regulatory caution rather than an enacted framework. Market-driven stablecoins such as MXNB operate on voluntary full-backing and redemption commitments rather than statutory mandates.

Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.

No periodic updates recorded against this sub-brief.

Sources and findings (2)
  1. T?source not recordedM4non-binding
  2. T?source not recordedM3non-binding

#

Consumer protection in the crypto space is addressed principally through repeated joint public-risk warnings by SHCP, Banxico and CNBV (2014, 2017, 2019, and June 2021), reiterated in Banxico's December 2025 year-end report, rather than through a dedicated custody-segregation, complaint-handling, or suitability regime for virtual-asset service providers. The 2021 communiqué explicitly frames the restriction on regulated institutions dealing in virtual assets as a consumer/system-protection measure.

Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.

No periodic updates recorded against this sub-brief.

Sources and findings (2)
  1. T?source not recordedM4bindingin force
  2. T?source not recordedM2non-binding

#

No crypto-specific Mexican tax statute or SAT (Servicio de Administración Tributaria) ruling was located during this research pass covering capital gains, income tax, VAT/IVA, withholding, or reporting obligations for virtual assets. General provisions of the Ley del Impuesto Sobre la Renta would presumptively apply to gains on disposal of any asset class, and general IVA rules would presumptively apply to VAT-taxable transactions, but no primary SAT guidance specific to crypto was confirmed in this pass. This module should be treated as a research gap requiring primary-source escalation.

Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.

No periodic updates recorded against this sub-brief.

Sources and findings (1)
  1. T?source not recordedM3non-binding

#

Following the Ley Fintech's entry into force, virtual-asset exchanges operating in Mexico became subject to reporting-threshold obligations to the UIF, and Mexico's cross-border financial channels involving virtual-asset-adjacent institutions have separately drawn U.S. Treasury/FinCEN sanctions-nexus action targeting cartel-linked money laundering. No outbound capital-control restriction specific to crypto was identified; the principal cross-border exposure is AML/sanctions-nexus reporting rather than an outbound restriction.

Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.

No periodic updates recorded against this sub-brief.

Sources and findings (3)
  1. T?source not recordedM4bindingin force
  2. T?source not recordedM3bindingin force
  3. T?source not recordedM2non-binding

#

Crypto AML/CFT obligations for MX are consumed via the Financial Integrity Module (FIM) subscription to aml_ctf; per fleet doctrine, this baseline does not independently produce aml_ctf/aml_cft claims. For disambiguation context only: Mexico's Unidad de Inteligencia Financiera (UIF) supervises AML/CFT compliance by virtual-asset-related obligated entities under the Ley Federal para la Prevención e Identificación de Operaciones con Recursos de Procedencia Ilícita (LFPIORPI) and the Ley Fintech's reporting provisions; UIF has previously flagged unregistered exchanges for non-compliance.

Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.

No periodic updates recorded against this sub-brief.

No categories match.

Filters combine as OR inside a group and AND across groups.

Editorial metadata

Provenance only. Nothing below gates publication or affects the render.

Editorial metadata for Mexico
FieldValue
trust.lawyer_review.statusnever_reviewed
trust.lawyer_review.reviewernot recorded
trust.content_sourceai_generated

Provenance and declared absence

Disclosure model: module cards load OPEN; standing positions render in full; sub-briefs and jurisdiction briefs load as a clamped teaser with an explicit “read full” control carrying the true word count; earlier updates stay collapsed behind a counted summary. No text is hidden without disclosing how much of it there is.

Sentinel-fed modules receive no special rendering treatment. sentinel_feed is an attribution chip only: it does not suppress content, does not generate an absence reason code, and does not exclude the module from any count, filter, search index or export on this page.

Family taxonomy is renderer-level presentation config, not a JID field. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score; per-module RAG traffic light; derived_scores = {}.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-08-17. A year-precision row is never promoted into a tighter band.

Orphan deltas: 0 cycle_delta row(s) target non-module objects and are listed in the rail rather than attached to a card.

Envelope: baseline resolved at jurisdiction_json.baseline; 8 module(s), 14 finding(s), 9 source(s) in the cumulative register.