Mexico ID Number: What It Is and How to Verify It

The Mexico ID number, officially known as the CURP (Clave Única de Registro de Población), is the primary identification code for Mexican citizens and residents. It is used for identity verification in government services, financial transactions, employment, and more. This guide explains what the Mexico ID number is, how to validate it in real time through an API, and how businesses can integrate it into their compliance and onboarding workflows.

What Is a Mexico ID Number?

The Mexico ID number is the CURP (Clave Única de Registro de Población), a unique 18-character alphanumeric code assigned to every person living in Mexico. It is issued by the National Population Registry (RENAPO) and serves as a foundational identity document for citizens, residents, and even some foreign nationals.

CURP vs. RFC: What’s the Difference?

While the CURP is the primary identity identifier, the RFC (Registro Federal de Contribuyentes) is a tax ID number used for fiscal purposes. The two are different documents:

A CURP is based on a person’s name, date of birth, gender, and state of birth, plus a checksum digit. It is also used to derive the NSS (Social Security Number) for IMSS registration. The RFC, on the other hand, can be derived from the CURP but includes additional verifications for tax compliance.

When Do You Need a Mexico ID Number?

You need a CURP in almost every official interaction in Mexico:

• KYC and onboarding – Financial institutions, fintechs, and insurance companies verify identity via CURP.
• Employment verification – Employers use CURP to register workers with IMSS and query the NSS.
• Government services – Health care, education, voting, and social programs all require the CURP.
• AML screening – The CURP is the key to linking a person with sanctions lists, PEP databases, and the SAT 69-B list.

For developers and businesses, the CURP API provides programmatic access to this data, enabling real-time verification without manual checks.

How to Validate a Mexico ID Number (CURP) in Real Time

Rather than relying on manual document inspection, you can validate a CURP instantly by querying the official RENAPO database through an API. The process is simple: you send the CURP and optionally the name and date of birth, and the API returns a verification status plus enriched demographic data.

What Data Does a CURP API Return?

A typical response from a CURP API includes:

• Validation status – Whether the CURP matches the RENAPO record.
• Full name – First name, middle name, two surnames.
• Date of birth – Day, month, year.
• Gender – Male or female.
• State of birth – Mexican state code and name.
• Nationality – Mexican or foreign.
• Photograph – If available from the official database.
• Fraud detection signals – Velocity checks, cross-client duplicate detection, mismatch flags.

Some providers also return a signed verification hash to prove data integrity, which is critical for regulated industries.

Integration Steps for Developers

1. Obtain the CURP from the user via a form (manual input or OCR from an INE card or birth certificate).
2. Perform format validation – The CURP must be 18 characters, match the regex pattern, and pass the checksum (digit 18).
3. Send a request to the API endpoint with the CURP (and optionally name/DOB for extra validation).
4. Parse the response – Check valid status, handle errors (e.g., invalid CURP, no record).
5. Use the data – Store the verification result, log identity details, and proceed with onboarding or transaction.

For high-volume workflows, many providers support bulk validation (up to 100 CURPs per request) and webhook notifications for asynchronous processing. The API Pull documentation covers the full request/response format, error codes, and rate limits.

When to Use a Mexico ID Number in Your Business Workflow

The CURP is the linchpin of identity verification in Mexico. Here are three common integration scenarios:

KYC and Onboarding Flows

Fintechs, neobanks, and lending platforms use the CURP as the first step in identity verification. During onboarding, a user enters their CURP and name, and the system checks it against RENAPO. If the data matches, the user is considered verified. This is faster than manual document review and reduces fraud.

Employment and Social Security Verification

Human resources platforms use the CURP to look up the NSS (Social Security Number) and register employees with IMSS. The NSS is required for payroll, health insurance, and retirement (AFORE) contributions. An API can take a CURP and return the associated NSS, making onboarding seamless. See the Social Security Number Mexico API guide for more details.

Anti-Money Laundering (AML) Screening

Regulated entities must screen customers against official sanctions lists. The CURP is the key identifier to query the SAT 69-B list (fake invoice issuers), OFAC, UN consolidated lists, and PEP databases. Integrating an AML API Mexico allows you to cross-reference the CURP against these watchlists in real time, ensuring compliance with CNBV regulations.

Common Pitfalls When Working with Mexico ID Numbers

Even with an API, there are challenges to watch out for:

CURP Format Errors and Validation Checks

Users often mistype their CURP, confusing characters like 0 (zero) and O (letter), or 1 and I. Always perform client-side format validation before sending to the API. The checksum digit (position 18) is a powerful tool to catch typos. Many APIs also accept name and date of birth to double-check the match.

Detecting Fraudulent or Stolen Identities

Fraudsters may use a legitimate CURP but with a different name or photo. Use fraud detection features like:

• Velocity checks – Is the same CURP being used from multiple IPs in a short time?
• Cross-client data – Does the CURP appear with different names across your user base?
• Mismatch alerts – Do the name, DOB, or gender not match the RENAPO record?

These signals can be combined with webhook notifications to flag suspicious activity immediately.

When This Is the Wrong Tool: Alternatives to CURP Verification

The CURP is not always the right identifier. Consider these exceptions:

• Tax reporting – For CFDI invoices, you need the RFC, not the CURP. Use the Validate RFC API for tax data.
• Voting and age verification – The INE (voter ID) card is the official document for proving age and residency. It includes a photograph and is more secure than a CURP alone.
• Foreign nationals – Non-residents without a CURP may use a passport or FM3 (temporary residency card). The CURP is only issued to those with a legal stay in Mexico.

For identity verification, the CURP is the most common starting point, but combine it with other documents (INE, passport, RFC) for a complete picture.

Compliance and Legal Considerations for Using Mexico ID Data

Working with personal data in Mexico is governed by the Ley Federal de Protección de Datos Personales en Posesión de los Particulares (LFPDPPP). Key points:

Data Protection and Consent

• Obtain explicit consent before collecting a CURP.
• Minimize data: only store the fields you need for your workflow.
• Ensure secure transmission (HTTPS) and storage (encryption at rest).

Audit Trails for Regulated Industries

Institutions regulated by CNBV (e.g., SOFIPOs, banks) must maintain audit trails. The API should return a signed response or verification hash that proves the data hasn’t been tampered with. This is especially important for AML compliance, where you may need to produce evidence of screening.

For more on compliance, refer to the official CNBV guidelines and RENAPO documentation.

Next Steps: Integrating Mexico ID Verification into Your Application

Now that you understand the Mexico ID number and its verification options, here’s how to get started:

1. Sign up for a sandbox environment – Test CURP validation with synthetic test cases before going live. Many providers offer free tiers or sandbox keys.
2. Review the API documentation – Learn the exact endpoint, parameters, and response format. The API Pull docs provide a complete reference, including error codes and rate limits.
3. Plan your integration – Decide whether to use synchronous calls for real-time verification or webhooks for batch processing. For high-volume workflows, bulk endpoints are available.

APIs are the fastest way to verify the Mexico ID number in your application. They eliminate manual checks, reduce fraud, and keep you compliant with local regulations. Start building today.