Mexico’s 2026 LFPIORPI rules: compliance guide for vulnerable activities
What changes on November 30, 2026 under Acuerdo 115/2026, who must build the unique identification file, and how to verify INE, CURP and RFC by API.
Status as of November 17, 2026: SHCP Acuerdo 115/2026 rewrites the LFPIORPI General Rules. It was published in the evening edition of Mexico’s Official Gazette (DOF) on August 7, 2026 and, under Transitory Article One, takes effect on November 30, 2026. Other duties (risk-based approach, the internal manual, automated mechanisms and PEP consultation) have later deadlines, through 2028.
If your business carries out a vulnerable activity — real estate, vehicle sales, jewellery, virtual assets, non-bank lending, notarial work, gaming and lotteries, among others — the new rules require you to identify the customer directly, build a unique file with officially recognised documents and, on digital channels, keep a record of the identification mechanism. This guide summarises what changes, who is covered and how to handle the identity-verification part by API.
What Acuerdo 115/2026 is and what changes on November 30
The LFPIORPI is Mexico’s federal law to prevent and identify operations with illicit-origin resources in non-bank vulnerable activities. Article 17 lists those activities and the UMA thresholds for identifying the customer and for filing Avisos (notices). Article 18 sets the duties to identify and know the customer and, for legal entities, to identify the controlling beneficiary.
Acuerdo 115/2026, signed on July 24, 2026, replaces the General Rules that implement that law. For a compliance or product team, the main points are:
- Rules, article 11: identify and know the customer directly, with written procedures for verifying and updating data, inside the Internal Policies Manual (article 37).
- Article 12: build a unique identification file for each customer, before or during the operation, with the data and documents in Annexes 3 (Mexican individuals or residents), 4 (Mexican companies), 5 and 6 (foreigners), among others.
- Rules, article 18: for electronic or digital channels, the file must be built in advance, identification mechanisms must prevent misuse of the channel, and the results must be stored in the file.
- New chapters on a risk-based approach (II Quáter), risk classification (III Bis), customer knowledge (III Ter), the PEP list (III Quáter), the controlling beneficiary (III Quinquies), automated mechanisms (XIII), the manual, training and audit.
Transitory timeline
| Date | What takes effect | Transitory article |
|---|---|---|
| November 30, 2026 | General entry into force of the Rules. | First |
| March 1, 2027 | The risk-based evaluation must be available to the authority; the Manual must include the methodology; the chapters on risk classification, customer knowledge and the controlling beneficiary apply to operations from that date; staff selection for new hires. | Second, Third, Fourth and Sixth |
| June 1, 2027 | The automated mechanisms in Chapter XIII must be in place. | Ninth |
| Nine months after November 30, 2026 (around late August 2027) | Access to the UIF PEP consultation (Consulta PEP 2.0). | Tenth |
| January 1 to December 31, 2027 | First annual training period. | Seventh |
| 2028 | First audit period. | Eighth |
November 30 is not the only deadline: it is the day the general identification rules already apply. The formalised risk-based approach, controlling-beneficiary rules and the UIF PEP consultation come later.
Who must comply
Anyone who carries out a vulnerable activity under article 17 of the LFPIORPI and is registered in SAT’s register. It also covers virtual-asset service providers (Chapter II Bis of the Rules) and those acting through fideicomisos (Chapter II Ter). Identification and Aviso thresholds are set in UMA in article 17 itself; check the official text for your activity, because they are not the same in every case.
The unique file and valid identification
The file is built with the data and documents in the annexes. For Mexican individuals or residents (Annex 3), valid ID is an original official document, current or expired by less than two years, with a photo and signature. The Rules expressly mention the INE voter credential. A professional licence (cédula profesional) is not listed as valid ID in that annex. CURP and RFC are also captured.
For Mexican companies (Annex 4) you collect corporate information and identify the controlling beneficiary. Article 18, section II, of the law requires, for business relationships, collecting the customer’s activity or occupation, supported by RFC registration notices.
Keep copies of the documents and the result of each check in the file. The Rules require you to retain the risk-grade and transactional-profile history for at least 10 years.
Digital onboarding (Rules, article 18)
If the operation runs on an electronic or digital channel, the Rules in practice require three things: build the file before the operation, put in place identification mechanisms that prevent misuse of the channel, and store the result in the file. A common operational design — not a single recipe written into the text — is:
- validate the INE credential against the official source and extract the data into the file;
- validate CURP and, where required, RFC;
- compare a selfie with the document photo, with liveness, to reduce the risk that someone uses another person’s credential;
- store the identifier, date, thresholds and signed result of each query.
Controlling beneficiary and politically exposed persons
Article 18, section III, of the LFPIORPI requires identifying the controlling beneficiary of legal entities and, for individuals, obtaining a declaration on whether one exists. Chapter III Quinquies of the Rules develops that duty from March 1, 2027 for operations from that date.
The UIF PEP list consultation (Consulta PEP 2.0, Chapter III Quáter) is not available on November 30, 2026: Transitory Article Ten enables it nine months after entry into force. Until then, we do not attribute a query to that list to Verifik; there is no Mexico PEP endpoint or UIF blocked-persons list endpoint in the current documentation.
Risk-based approach and automated mechanisms
Chapter II Quáter introduces the risk-based approach. Chapter III Bis classifies customers; the simplified measures in article 17 of the Rules apply only to low-risk customers. The automated mechanisms in Chapter XIII must be in operation by June 1, 2027. An identity API does not replace those modules, but you can use repeatable checks and the evidence each query leaves to feed your risk classification and your file.
Penalties (LFPIORPI articles 53 to 56)
The figures come from the law, as last reformed in the DOF on July 16, 2025:
- Articles 53, section II, and 54, section I: breaching any article 18 duty (identification, controlling beneficiary and others) is fined at 200 to 2,000 times the daily UMA.
- Article 54, section III: omitting Avisos or carrying out prohibited operations is fined at 10,000 to 65,000 UMA, or 10–100% of the operation’s value, whichever is higher.
- Article 54 Bis: SHCP can order a temporary suspension of operations with specific customers. Article 55 provides a one-time waiver for spontaneous self-correction, and a 50% reduction afterwards. Article 56 allows permit revocation for some activities on repeat offences.
The daily UMA in force from February 1, 2026 is 117.31 Mexican pesos, according to INEGI’s notice published in the DOF on January 9, 2026. On that reference, 200 to 2,000 UMA is about 23,462 to 234,620 pesos, and 10,000 to 65,000 UMA is about 1,173,100 to 7,625,150 pesos. Those peso figures are illustrative: the authority applies the UMA in force when the fine is imposed.
How Verifik fits these controls
Verifik does not file Avisos with SAT and does not query the UIF PEP list. It also does not “make you compliant” with the LFPIORPI on its own: you remain the obligated party. What the API does is automate several identification and international-list checks, with a Verifik signature on each response.
| Duty | Control | What Verifik offers |
|---|---|---|
| Law art. 18-I and Annex 3: verify official ID (INE) | Validate the credential against the official source and, if needed, extract the data by OCR | GET /v2/mx/ine (CIC, OCR or clave de elector) and POST /v2/mx/ine/ocr |
| Annex 3: CURP | Validate the CURP | GET /v2/mx/curp |
| Law art. 18-II: activity or occupation from the RFC | Validate the RFC | GET /v2/mx/rfc |
| Rules art. 18: identification on a digital channel | Compare a selfie with the document photo, with liveness | smartENROLL flow and POST /v2/face-recognition/compare-with-liveness |
| Annex 4 / controlling beneficiary | A company lookup as one input to the file (it does not replace a beneficial-owner register) | GET /v2/mx/company, which takes an FME identifier, not an RFC. It does not claim full discovery of the controlling beneficiary. |
| Risk classification / mitigants | Screen the customer and beneficiary against international lists | GET /v2/ofac, GET /v2/onu, GET /v2/interpol |
For batch or no-code checks you can use smartCHECK. To authenticate a customer who has already been onboarded, HumanAuthn (smartACCESS).
1. Validate the INE credential
The INE documentation requires documentType=INE and a documentNumber that can be a CIC (9 digits), OCR (13) or clave de elector (18 characters). The example uses a test identifier from the docs:
curl -G "https://api.verifik.co/v2/mx/ine" \
-H "Accept: application/json" \
-H "Authorization: Bearer $VERIFIK_TOKEN" \
--data-urlencode "documentType=INE" \
--data-urlencode "documentNumber=187639699"Example 200 response (fields published in the docs):
{
"data": {
"cic": "187639699",
"documentNumber": "187639699",
"documentType": "INE",
"electorKey": "CSFTGV76061131H400",
"emissionNumber": "1",
"emissionYear": "2018",
"identifierType": "cic",
"message": "Vigente como medio de identificacion y puede votar",
"ocr": "0276031206745",
"validity": "31 de diciembre de 2030"
},
"signature": {
"dateTime": "July 14, 2026 10:00 AM",
"message": "Certified by Verifik.co"
}
}2. Complete CURP and RFC
import axios from "axios";
const headers = {
Accept: "application/json",
Authorization: `Bearer ${process.env.VERIFIK_TOKEN}`,
};
const { data: curp } = await axios.get("https://api.verifik.co/v2/mx/curp", {
params: { documentType: "CURP", documentNumber: "ABCD890513ABCDEF09" },
headers,
});
const { data: rfc } = await axios.get("https://api.verifik.co/v2/mx/rfc", {
params: { documentType: "CURP", documentNumber: "LOPE900501HDFGRN01" },
headers,
});
console.log(curp, rfc);3. Liveness on the digital channel
After you show the customer the relevant notice and collect consent, you can compare the selfie with the document photo:
import os, requests
url = "https://api.verifik.co/v2/face-recognition/compare-with-liveness"
headers = {
"Content-Type": "application/json",
"Authorization": f"Bearer {os.getenv('VERIFIK_TOKEN')}"
}
payload = {
"probe": "<base64>",
"gallery": ["<base64>"],
"search_mode": "FAST",
"liveness_min_score": 0.6,
"compare_min_score": 0.8
}
r = requests.post(url, json=payload, headers=headers)
print(r.json())4. Store the result in the file
A simple pattern is to write each response with a timestamp and the query identifier, so you can keep the file:
function toExpediente(check, response) {
return {
check,
at: new Date().toISOString(),
queryId: response.id,
signature: response.signature,
data: response.data,
};
}
// expediente.identificacion.push(toExpediente("ine", ineResponse));Implementation checklist
- Confirm whether your operation is a vulnerable activity under article 17 of the LFPIORPI and whether you are on SAT’s register.
- Draft or update the Internal Policies Manual with identification and data-update procedures (Rules arts. 11 and 37).
- Define the unique file’s contents according to the matching annex (3, 4, 5 or 6).
- Accept as official ID the INE card or another document that meets Annex 3; do not use a professional licence as valid ID.
- Validate INE, CURP and, where applicable, RFC against official sources and store the result in the file.
- If you operate on a digital channel, build the file before the operation and add face comparison with liveness.
- Capture the controlling beneficiary of legal entities and the corresponding declaration for individuals; remember that those Rules apply to operations from March 1, 2027.
- Do not assume the UIF PEP consultation is available on November 30, 2026: it is scheduled for nine months after entry into force.
- Prepare the risk evaluation and classification for March 1, 2027 and the automated mechanisms for June 1, 2027.
- Retain the risk and transactional-profile history for at least 10 years.
- Decide who files Avisos with SAT: Verifik does not file them.
- Review the penalties in articles 53 to 56 and the self-correction process in article 55.
Related reading
Frequently asked questions
Is the INE credential enough on its own to identify the customer?
It is the official ID the Rules expressly mention in Annex 3, but the unique file also captures CURP and RFC and, in a business relationship, the customer's activity or occupation. On a digital channel, article 18 of the Rules also requires identification mechanisms that prevent misuse of the channel and storage of their results in the file.
Can I onboard customers remotely?
Yes. Article 18 of the Rules covers electronic or digital channels, with three conditions: build the file in advance, put in place identification mechanisms that prevent misuse of the channel, and store the results in the file.
What if the customer has no INE card?
Annex 3 allows an original official document, current or expired by less than two years, with a photo and signature. A professional licence (cédula profesional) is not listed as valid ID in that annex. Check the annex that applies (including the ones for foreigners) in the official text.
Is the November 30, 2026 date final?
Yes. It is the general entry into force set by Transitory Article One of Acuerdo 115/2026, published in the DOF on August 7, 2026. Other duties — the risk-based approach, the controlling beneficiary, automated mechanisms and the PEP consultation — have later deadlines, between March 2027 and 2028.
Do I need PEP screening on November 30, 2026?
The UIF PEP list consultation (Consulta PEP 2.0) is enabled nine months after entry into force, around late August 2027 (Transitory Article Ten). It is not available on November 30. Verifik does not currently offer a Mexico PEP endpoint or a UIF blocked-persons list endpoint.
What fines apply?
Breaching an article 18 LFPIORPI duty is fined at 200 to 2,000 times the daily UMA. Omitting Avisos or carrying out prohibited operations is fined at 10,000 to 65,000 UMA, or 10–100% of the operation's value, whichever is higher (articles 53 and 54). The daily UMA in force from February 1, 2026 is 117.31 pesos (INEGI, DOF January 9, 2026).
Does Verifik file Avisos with SAT?
No. Verifik automates identification, biometrics and international-list checks. Avisos and registration in SAT's register remain the obligated party's responsibility.
Other regulations
- ChileChile Law 21,719 on personal data: a guide for digital onboardingIn force from Dec 1, 2026 (postponement bill pending)Effective: Biometrics as sensitive data, data subject rights, breaches and fines up to 20,000 UTM.
- ColombiaColombia Law 2573 of 2026: identity verification against identity theftTakes effect Nov 19, 2026Effective: "Sufficient and reasonable" identity verification, a 10-business-day document check and the SIC/Superfinanciera protocol.
- PeruSBS Resolution 2660-2015: Peru AML and customer due diligence guide (2026)In forceGeneral, simplified and enhanced due diligence; insurance update in force since October 30, 2026.
- ColombiaColombia SAGRILAFT 2026: guide to Supersociedades Circular 100-000020 and Chapter IXIn force; adapt by 31 May 2027Effective: SAGRILAFT and PTEE merge into Chapter IX; existing systems must be adapted by 31 May 2027.
Need identity verification and consent that hold up to an audit?
Talk to a compliance specialist
Tell us about your onboarding flow and we will map the identity checks, biometrics and consent records you need.
Sources
- Acuerdo 115/2026 — Official Gazette text (7 Aug 2026, evening edition, Spanish)
- DOF PDF for 7 August 2026 (evening edition)
- LFPIORPI — Chamber of Deputies text (last reform DOF 16 Jul 2025, Spanish)
- INEGI / DOF: 2026 UMA value (9 January 2026, Spanish)
- Verifik docs — INE verification
- Verifik docs — CURP
- Verifik docs — RFC
- Verifik docs — face comparison with liveness
Disclaimer: This content is for information only and is not legal advice. It summarizes the official text as of the last-reviewed date; always check the official source and your legal counsel before making compliance decisions.