Legal nature and regulatory perimeter of stablecoins

Legal nature of stablecoins in Mexico: a functional test

Observed pattern. A defensible classification separates the token, the redemption right, and the service provided by each participant.

How to put it into practice

The first question is technological and functional: is the representation of value recorded electronically, does it circulate among the public, and is it transferred only by electronic means? The second is contractual: is there an identifiable issuer obligated to redeem, in what currency, and under what conditions? The third is regulatory: does someone raise funds, hold balances, custody keys, exchange assets, or receive funds to deliver them to a beneficiary?

These questions can produce simultaneous answers. A token may be analyzed as a virtual asset for preventive purposes, while the redemption right is examined as a credit right and the operator remains subject to obligations for the service it actually performs. The commercial label "stablecoin," on its own, resolves none of those layers.

The minimum matrix

Before issuing a conclusion, it is advisable to document: issuer and jurisdiction; redemption terms; composition and ownership of reserves; eligible users; admitted networks; custody; fiat flow; use before the public; fees; and who bears freezes, depeg, or insolvency. It must also be distinguished whether the operator acts on its own account, as a commission agent, as a custodian, or as a transmitter.

The practical consequence is clear: the legal memo must classify each function and each flow, not just the asset. If custody, the ultimate beneficiary, or the manner of receiving funds changes, the analysis may change even though the same token continues to be used.

Legal basis

LRITF in force, LFPIORPI in force, and Circular 4/2019.

Why a stablecoin does not become a currency by holding its peg

Observed pattern. The economic peg serves to describe price or design, but it does not replace the legal test of legal tender or foreign currency.

How to put it into practice

The distinction matters because several flawed analyses start from the token's symbol or the price screen. To argue that a right denominated in fiat exists, one would have to review the issuer's terms: who may redeem, whether the end user has a direct claim, what the minimums, terms, fees, and grounds for suspension are. A price reference without an enforceable obligation is not equivalent to an account in the reference currency.

Three quick tests

1. Enforceability test. Can the holder demand a specific amount of currency from an identified counterparty?
2. Transfer test. Is the right against the issuer transmitted, or a digital unit whose price depends on the market?
3. Use test. Is the product offered for payment, investment, treasury, or internal settlement?

The result must be carried over to taxation, accounting, contract, and advertising. Saying "equivalent to USD" may describe a value target; saying "digital USD" may lead people to believe that the same protection, availability, or backing exists as in a bank deposit. The contract must explain the difference and avoid guaranteeing absolute stability.

Legal basis

definition of virtual asset in the LRITF and Banco de México's virtual asset framework.

Additional language test. Compare the terminology used in the terms, the price quote, the accounting, and the advertising; if any of them calls the token a "currency," document the basis or correct the inconsistency before offering it.

The functional test for virtual assets under the Fintech Law

Observed pattern. The definition must be applied to the digital unit and to its actual use; the commercial name does not decide on its own.

The classification file should contain evidence on four points: value representation recorded electronically; use among the public as a means of payment; transfer only by electronic means; and the absence or presence of the cases excluded by the definition itself. When an exclusion is invoked on the basis of denomination in a currency or foreign currency, the actual legal right must be analyzed, not merely the peg objective.

The service also counts

Classifying the token does not exhaust the regulatory map. A platform may custody, exchange, or transfer value; an issuer may receive funds and promise redemption; and another participant may receive pesos to deliver them elsewhere. Each verb must be tested against its own regime. There is no generic "crypto" license that absorbs money transmission, electronic payment funds, or vulnerable activity.

The definition must also be reviewed by purpose. For an AML policy, a preventive approach is warranted; for taxes, the taxable act and the consideration must be identified; for contracts, what matters is determining ownership, the redemption right, and the moment of settlement. A single technical description does not automatically answer all three questions.

What to review

Prepare a one-page classification opinion per asset, attach the issuer's terms, and have it approved by legal/compliance before onboarding. Include review triggers: fork, network migration, change of reserves, new freezing powers, access to redemption, or use for the Mexican public.

Legal basis

LRITF in force and Banxico Circular 4/2019.

How to put it into practice

Article 30 LRITF sheet. This piece must prove that each element of the definition has an associated fact and evidence.

• describe the electronic representation of value.
• prove use among the public.
• document the function as a means of payment.
• confirm electronic transfer.
• review legal exclusions.
• version the conclusion per token.

The review must move from describing the electronic representation of value, test it against documenting the function as a means of payment, and end at versioning the conclusion per token without filling gaps with assumptions. The result returns to design if proving use among the public does not match confirming electronic transfer, or if reviewing legal exclusions lacks verifiable support.

The file must show first the electronic representation of value; then use among the public; and finally the review of legal exclusions, preserving the relationship among the three steps. If a change appears in transferability, use, electronic recording, or target public, the conclusion no longer covers the active version and is reviewed before the next operation.

Banxico, ITFs, and banks: limits on offering stablecoins

Observed pattern. The analysis of offering to the public must first identify whether an ITF, a bank, or a non-financial provider is involved.

The Circular requires prior authorization for operations within its scope and articulates a risk-separation approach. The operational point is not solely who touches the keys: it also matters whether the client buys, sells, transmits, or holds exposure to the asset through the institution.

Questions for a partnership

When a VASP connects with an IFPE or bank, the contract and the diagram must answer: who contracts with the user? who receives pesos? into which account? who sets the price? who executes the on-chain operation? who custodies? who files the reports? what does the institution see in its systems? Calling one party a "technology provider" does not fix a flow in which it materially performs a regulated function.

It must also be avoided to present the financial entity as sponsor or guarantor of the token. Communication to the public must distinguish the fiat service from the virtual asset service and explain risks, responsibilities, and complaint channels.

What to review

Before launch: a perimeter opinion, a review of each entity's authorization and corporate purpose, AML sign-off, a shared-data matrix, and reconciliation tests. Any API integration must be assessed with the same depth as a manual flow.

Legal basis

Circular 4/2019, LRITF in force, and Banxico's regulatory actions on virtual assets.

How to put it into practice

Regulated participant matrix. This piece must prove that each entity knows what it can offer, under what authorization, and with what restriction.

• identify each participant's license.
• map the operation with virtual assets.
• review Banco de México's determinations.
• document the applicable authorization.
• validate advertising and contract.
• record prohibitions and conditions.

The review must move from identifying each participant's license, test it against reviewing Banco de México's determinations, and end at recording prohibitions and conditions without filling gaps with assumptions. The result returns to design if mapping the operation with virtual assets does not match documenting the applicable authorization, or if validating advertising and contract lacks verifiable support.

The file must show first each participant's license; then the mapping of the operation with virtual assets; and finally the validation of advertising and contract, preserving the relationship among the three steps. If the incorporation of a bank, an ITF, a new asset, or a new offer to the public appears, the conclusion no longer covers the active version and is reviewed before the next operation.

When exchanging stablecoins triggers the LFPIORPI

Observed pattern. Habitual exchange, custody, and transfer require a function map before deciding the preventive scope.

The 2025 reform expanded and reinforced the preventive framework. That is why the product must map functions, users, and territory against the law in force, its transitional regime, and the applicable rules. In particular, a foreign provider must not rule out the analysis when its service reaches Mexican persons.

Substantive obligations

If the flow fits, compliance is not reduced to filing a report. It comprises enrollment and registration, client identification and knowledge, controlling beneficiary, record retention, attending inspections, training, risk assessment, audit in the applicable cases, and the filing of reports or notices. Thresholds and accumulations must be parameterized against the official version in force and the UMA of the period; they must not be hard-coded from a blog article.

Nor is it enough to know the person when opening the account. The evidence must link client, bank account, wallet, price quote, hash, consideration, and reporting decision. That chain makes it possible to explain why an operation was reported, accumulated, or halted.

What to review

Build a matrix with columns for the regulated verb, the entity that performs it, the jurisdiction, the system, the data captured, and the resulting obligation. Legal validates the perimeter; operations demonstrates that the actual flow matches; technology retains the necessary fields.

Legal basis

LFPIORPI in force, SAT: virtual asset activity, and SPPLD Portal.

How to put it into practice

Vulnerable activity matrix. This piece must prove that the Article 17 case is established by functions and not by commercial label.

• describe habituality and professionalism.
• identify purchase or sale by client.
• document custody or storage.
• map executed transfers.
• review territorial scope.
• assign Article 18 obligations.

The review must move from describing habituality and professionalism, test it against documenting custody or storage, and end at assigning Article 18 obligations without filling gaps with assumptions. The result returns to design if identifying purchase or sale by client does not match mapping executed transfers, or if reviewing territorial scope lacks verifiable support.

The file must show first habituality and professionalism; then the identification of purchase or sale by client; and finally the review of territorial scope, preserving the relationship among the three steps. If a change appears in habituality, platform, exchange, custody, or transfer, the conclusion no longer covers the active version and is reviewed before the next operation.

SPPLD registration: an administrative obligation, not a commercial license

Observed pattern. Administrative enrollment and substantive compliance are distinct fronts; neither should be presented as a commercial endorsement.

Substantive obligations arise from the legal case and from carrying out the activity. The company must be prepared to identify, compile files, retain information, monitor, and document decisions from the applicable start date. An administrative access problem does not make those obligations nonexistent, nor does it enable alternative channels unless the authority establishes them.

What the registration does not decide

The SPPLD does not resolve whether the flow also constitutes money transmission, deposit-taking, an electronic payment fund, a service subject to Banco de México authorization, or a specific tax treatment. Those conclusions require separate analysis. Nor should enrollment be used as a commercial seal of the UIF or the SAT.

The correct communication is descriptive: the person is registered in order to comply with the Vulnerable Activities regime, if that is verifiable, without asserting that the authority authorized the token, guaranteed the reserves, or approved contracts.

What to review

Keep an enrollment file with acknowledgments, responsible persons, calendar, access contingencies, and evidence of prior compliance. The board or administrator should receive a dashboard that distinguishes "registration," "substantive obligation," "report filed," and "financial authorization," avoiding a single ambiguous "regulated" box.

Legal basis

SAT enrollment requirements, SPPLD Portal, and LFPIORPI in force.

How to put it into practice

Enrollment and substantive compliance control. This piece must prove that the file distinguishes the register, the substantive obligations, and any license outside the SPPLD.

• retain the enrollment or update acknowledgment.
• record the declared activity.
• maintain the identification file.
• control reports and notices.
• prohibit language of official endorsement.
• schedule reviews of the register.

The review must move from retaining the enrollment or update acknowledgment, test it against maintaining the identification file, and end at scheduling reviews of the register without filling gaps with assumptions. The result returns to design if recording the declared activity does not match controlling reports and notices, or if prohibiting language of official endorsement lacks verifiable support.

The file must show first the enrollment or update acknowledgment; then the declared activity; and finally the prohibition of language of official endorsement, preserving the relationship among the three steps. If enrollment, modification, cancellation, change of activity, or a commercial message about the registration appears, the conclusion no longer covers the active version and is reviewed before the next operation.

Foreign VASP with Mexican clients: reach and presence

Observed pattern. The territorial matrix must review users, marketing, support, accounts, wallets, and execution, not just the corporate domicile.

The analysis must avoid two shortcuts: assuming that the server's geolocation decides the applicable law, or concluding that any Mexican user automatically creates all obligations. The correct approach is to document how the service is directed and provided.

Map of connections

It is advisable to review: acceptance of clients with Mexican domicile or nationality; local domain and marketing; quotation currency; bank accounts; agents and affiliates; terms and chosen law; support; custody; contractual counterparty; and who executes each transfer. Those facts are then tested against vulnerable activity, data protection, consumer law, taxes, and possible reserved financial activities.

Contractually blocking Mexico is also not enough if, in practice, Mexican documents, pesos, or local campaigns are accepted. Conversely, if the decision is to serve the market, the company needs an explicit route for registration, representative, retention, reports, and cooperation with counterparties.

What to review

Implement a country-product matrix approved by legal, technical controls consistent with the restrictions, and periodic reviews of traffic, clients, and payments. Each commercial exception must be recorded with its basis and an expiration date.

Legal basis

LFPIORPI in force, SAT: virtual asset activity, and FATF: VA/VASP update 2025.

How to put it into practice

Matrix of connections with Mexico. This piece must prove that the territorial conclusion lists facts, uncertainties, and obligations by jurisdiction.

• identify the user's citizenship and residence.
• locate marketing and contracting.
• map support and execution.
• document accounts and wallets.
• review the foreign providing entity.
• obtain local advice where appropriate.

The review must move from identifying the user's citizenship and residence, test it against mapping support and execution, and end at obtaining local advice where appropriate without filling gaps with assumptions. The result returns to design if locating marketing and contracting does not match documenting accounts and wallets, or if reviewing the foreign providing entity lacks verifiable support.

The file must show first the user's citizenship and residence; then the location of marketing and contracting; and finally the review of the foreign providing entity, preserving the relationship among the three steps. If a new country, campaign, support channel, account, or type of Mexican client appears, the conclusion no longer covers the active version and is reviewed before the next operation.

Mexican stablecoin issuer: IFPE, deposit-taking, or novel model

Observed pattern. Redeemable issuance requires modeling the liability, reserves, deposit-taking, payment funds, and redemption conditions before launch.

The central question is who receives the money and what right the user obtains. The segregation and ownership of reserves, redemption, use of funds, availability, yield, transmission among third parties, and offering to the public must be reviewed. Replacing "balance" with "token" does not transform the substance of the product.

Design decisions that change the perimeter

A closed, non-transferable token usable only with the issuer presents different questions from a publicly tradable one. The analysis also changes if only eligible participants can redeem, if there is intermediation by an IFPE, if the reserves are invested, or if the issuer guarantees an unconditional peg.

The novel models framework must not be presented as an automatic permit. It is a regulatory route that requires reviewing eligibility, timing, risks, and applicable authorizations. Before building, it is advisable to compare alternatives: accounting balance, electronic payment fund, tokenized asset, closed voucher, or purely technological infrastructure.

What to review

Prepare a funds-and-rights diagram, a deposit-taking/IFPE opinion, a reserve policy, redemption terms, an insolvency analysis, and an authorizations plan. The prototype must not accept real funds until the perimeter is resolved and communications to the public are consistent.

Legal basis

LRITF in force, Circular 4/2019, and CNBV: Financial Technology Institutions.

How to put it into practice

Issuance and redemption sheet. This piece must prove that the design is tested before launch against IFPE, deposit-taking, and the novel model.

• identify the liability toward the holder.
• document the reserve and its ownership.
• describe the receipt of funds.
• define minting and burning.
• prove the redemption right.
• analyze reserved activities.

The review must move from identifying the liability toward the holder, test it against describing the receipt of funds, and end at analyzing reserved activities without filling gaps with assumptions. The result returns to design if documenting the reserve and its ownership does not match defining minting and burning, or if proving the redemption right lacks verifiable support.

The file must show first the liability toward the holder; then the reserve and its ownership; and finally the redemption right, preserving the relationship among the three steps. If a change appears in the reserve, eligibility, redemption, yield, or receipt of funds, the conclusion no longer covers the active version and is reviewed before the next operation.

VAT on stablecoins: separating principal, fee, spread, and redemption

Observed pattern. Separating principal, fee, spread, and redemption in the contract and the accounting reduces contradictory tax conclusions.

At a minimum, the following must be distinguished: principal delivered by the client; asset received; explicit fee; embedded spread; gas or network cost; custody; transfer; intermediation; and any eventual redemption against the issuer. Then it is identified who provides each service, where it is deemed provided, and what supporting document corresponds.

Why the architecture matters

If the company acts on its own account, the documentation may differ from a commercial commission. If it charges a fee, that service needs its own analysis. If it passes on gas, it must be defined whether it is a documented reimbursement or part of the consideration. If the token embeds a redemption right, transferring that right requires a different analysis from the mere provision of technology.

There is no prudent rule that allows calling every stablecoin a "currency" and assuming an exemption. Nor is it sound to tax the full volume without identifying the act. In the absence of a specific criterion, the defense lies in a reasoned position that is consistent across contracts, accounting, CFDI, and returns.

What to review

Design a tax catalog by event and a daily reconciliation among order, price quote, blockchain, bank, invoice, and accounting. Exceptions must be escalated to tax/legal and the applied criterion retained. A formal ruling request may be appropriate when volume or novelty warrants it.

Legal basis

VAT Law in force, CFF in force, and LRITF in force.

How to put it into practice

Tax bridge by component. This piece must prove that the contract, CFDI, accounting, and reconciliation use the same economic components.

• separate principal and consideration.
• identify the underlying act.
• document the explicit fee.
• calculate the spread with a verifiable source.
• review the moment the tax accrues.
• reconcile redemption and refunds.

The review must move from separating principal and consideration, test it against documenting the explicit fee, and end at reconciling redemption and refunds without filling gaps with assumptions. The result returns to design if identifying the underlying act does not match calculating the spread with a verifiable source, or if reviewing the moment the tax accrues lacks verifiable support.

The file must show first the separation of principal and consideration; then the identification of the underlying act; and finally the review of the moment the tax accrues, preserving the relationship among the three steps. If a new fee, spread, discount, redemption, or ancillary service appears, the conclusion no longer covers the active version and is reviewed before the next operation.

Income tax, the CFF, and tax evidence for stablecoin operations

Observed pattern. Tax evidence must reconcile date, value, counterparty, hash, bank account, and CFDI or equivalent support.

The minimum file links the identity of the parties, the contract or order, the date and time, the asset and network, the amount, the price source, the exchange rate where applicable, fees, bank account, addresses, hash, confirmations, CFDI, and accounting record. An isolated screenshot does not prove the entire cycle.

Consistency before a perfect price quote

The valuation policy must define the source, the cutoff time, the treatment of low liquidity, and corrections. If an exchange is used, its representativeness must be justified. If the operation has a bilateral quote, the acceptance must be retained. For inventories or held assets, accounting and tax must agree on recognition events without assuming that the technological label decides the nature.

It is also advisable to separate own assets from client assets and to record internal transfers. Without that separation, a movement between wallets may look like a sale or income. Traceability must show purpose and ownership.

What to review

Adopt a "tax package per transaction" generated automatically and a signed monthly reconciliation. Legal retains the terms; operations, the execution; treasury, bank and wallets; tax, valuation and CFDI. Missing items are recorded as an exception, not corrected silently.

Legal basis

CFF in force, Income Tax Law in force, and VAT Law in force.

How to put it into practice

Tax file per operation. This piece must prove that income, cost, date, value, and support can be reconstructed from a single operation.

• record the date and time.
• retain the value and source.
• link the account and hash.
• identify the counterparty and residence.
• associate the CFDI or applicable support.
• document the accounting and tax treatment.

The review must move from recording the date and time, test it against linking the account and hash, and end at documenting the accounting and tax treatment without filling gaps with assumptions. The result returns to design if retaining the value and source does not match identifying the counterparty and residence, or if associating the CFDI or applicable support lacks verifiable support.

The file must show first the date and time; then the value and source; and finally the association of the CFDI or applicable support, preserving the relationship among the three steps. If a change of valuation, counterparty, residence, supporting document, or accounting policy appears, the conclusion no longer covers the active version and is reviewed before the next operation.