What Is RENAPO Mexico? A Developer’s Guide to CURP Identity Verification

RENAPO Mexico (Registro Nacional de Población) is the official government registry of every Mexican citizen and resident. It issues the CURP (Clave Única de Registro de Población) and serves as the authoritative source for identity verification. For developers and compliance teams, programmatic access to RENAPO data is essential for KYC onboarding, AML screening, and employment verification. This guide explains how to query RENAPO via a CURP API, what data you get, and when to use—or avoid—this integration.

What Is RENAPO Mexico and Why Does It Matter for Identity Verification?

RENAPO (Registro Nacional de Población) is the Mexican government’s central population registry, managed by the Secretaría de Gobernación (SEGOB). It maintains a database of every individual’s identity documents, including birth certificates, CURP, and biometric data. The CURP—a unique 18-character alphanumeric code—is the key identifier linked to RENAPO records.

RENAPO vs. CURP: Understanding the Relationship

Think of RENAPO as the national database of población (population) and CURP as the clave (key) to access that data. When you validate a CURP against RENAPO, you’re confirming that the person exists, their identity documents are consistent, and the data hasn’t been tampered with. This validation is critical for regulated industries: fintechs use it for KYC, insurers for policy underwriting, and HR departments for employee registration with IMSS (Instituto Mexicano del Seguro Social).

RENAPO also supports trámites (procedures) like issuing passport copies, marriage certificates, and proof of identity. For any trámite requiring official identity verification, querying RENAPO ensures you’re working with the oficial government record.

Key takeaway: RENAPO is the source of truth for Mexican identity. CURP is the query key. Using a CURP API that connects directly to RENAPO gives you real-time, authoritative data.

How to Access RENAPO Data via a CURP API

A CURP API acts as a gateway to RENAPO. Instead of building a custom integration with the government’s internal systems (which are not publicly available as REST endpoints), you use a provider that has a direct connection to RENAPO.

The CURP API as the Gateway to RENAPO

The integration is simple: you send a valid CURP string, and the API returns the associated RENAPO-validated identity data. The response typically includes:

• Full name (first, middle, last, second last)
• Date of birth
• Gender
• State of birth
• Verification status (matches RENAPO or not)

What You Send and What You Get Back

Here’s a conceptual example of what a CURP API request/response looks like (using API Pull’s CURP API as the reference):

For the exact endpoint path, parameter names, and response fields, refer to the official API Pull documentation. Do not rely on hypothetical endpoints—always use the documented API.

Key Use Cases for RENAPO API Integration

KYC and Onboarding for Fintechs

Fintechs in Mexico must verify customer identities before opening accounts or disbursing loans. By querying RENAPO via a CURP API, you can:

• Confirm the customer’s identity matches government records.
• Reduce fraud from synthetic identities.
• Speed up onboarding (responses under 500ms).

For AML compliance, combine CURP data with the AML API Mexico to screen against SAT 69-B, OFAC, and PEP lists.

Employment Verification with NSS and CURP

HR teams need to verify that employees are registered with IMSS. The NSS (Número de Seguridad Social) is linked to CURP. By using a CURP API that also provides NSS lookup (via the NSS API), you can confirm social security enrollment and avoid duplicate registrations.

AML Screening and PEP Checks

For regulated entities, you must screen customers against the SAT 69-B list (fake invoice issuers) and international sanctions lists. The CURP provides the identity base; the AML API Mexico cross-references it against these lists. This is critical for servicios in banking, insurance, and legal services.

Data Enrichment with Geographic (AGEB) and Demographic Data

RENAPO data can be enriched with INEGI census data to derive AGEB-level (Área Geoestadística Básica) information, such as income level, population density, and fraud risk scores. This is useful for risk-based pricing in microinsurance or lending.

AFORE and Retirement Account Opening

Afores (Administradoras de Fondos para el Retiro) must verify identity before opening retirement accounts. A CURP API connected to RENAPO provides the necessary identity proof, often combined with biometric validation (though RENAPO itself does not provide biometric data—see limitations below).

Compliance and Regulatory Considerations for RENAPO Data

Audit Trails and Data Integrity

Regulated institutions (e.g., those supervised by CNBV) must maintain audit trails for identity verification. A compliant CURP API should return a signed response or a verification hash that proves the data came from RENAPO unchanged. This ensures that if a regulator like the CNBV (Comisión Nacional Bancaria y de Valores) asks for proof of verification, you can produce it.

CNBV and SAT Requirements

• CNBV: Requires financial institutions to verify customer identity against official registries. RENAPO is the primary source for individuals.
• SAT: For tax compliance, the CURP must match the RFC (Registro Federal de Contribuyentes). The RFC API (bundled with CURP) helps satisfy SAT requirements.

Fraud detection signals—such as velocity checks (multiple queries for the same CURP in a short time) and cross-client data—are essential to prevent identity theft. The API should provide these signals.

When This Is the Wrong Tool: Limitations of RENAPO API Access

RENAPO is not a biometric database. It does not provide facial recognition, fingerprints, or iris scans. If your use case requires curp biométrica verification, you need a separate service (e.g., INE’s biometric database). Also, RENAPO only covers Mexican citizens and residents. For international identities, you must use other sources.

Additionally, RENAPO does not include registro civil event data (marriage, divorce, death) beyond what is linked to the CURP. For those, you may need a separate civil registry API.

Getting Started with API Pull’s RENAPO-Connected CURP API

API Pull’s CURP API connects directly to RENAPO for real-time validation. Here’s how to start:

Sandbox Environment for Testing

Use the sandbox with synthetic test cases to simulate RENAPO responses. This allows you to build and test your integration without affecting production data.

Webhook Notifications for Async Workflows

If your system processes verifications asynchronously (e.g., batch employee checks), enable webhook notifications. The API will POST results to your endpoint when ready.

Bulk Validation for High-Volume Operations

For bulk checks (e.g., onboarding 100 new employees), use the bulk endpoint that accepts up to 100 CURPs per request. This reduces latency and API calls.

To get started, sign up for a free trial on the API Pull platform and explore the documentation.

FAQ

What is the difference between RENAPO and CURP?

RENAPO is the national population registry; CURP is the unique identifier issued by RENAPO. CURP is the key to query RENAPO data.

Can I access RENAPO directly via a government API?

No, the Mexican government does not expose a public REST API for RENAPO. You must use a trusted third-party provider like API Pull that has a direct connection to RENAPO.

Does RENAPO include biometric data?

No. RENAPO stores identity documents and demographic data but not biometrics (fingerprints, facial images). For biometric verification, use INE (Instituto Nacional Electoral) data.

What compliance standards does a CURP API need to meet?

For CNBV-regulated entities, the API must provide signed responses, audit trails, and fraud detection. It should also support AML screening via SAT 69-B, OFAC, and PEP lists.

How fast is a RENAPO query?

API Pull’s CURP API returns responses in under 500ms, suitable for mobile and web flows.