Mexico ID Card Verification: A Developer’s Guide

When you need to verify a person’s identity in Mexico, the most common approach is to start with their id card mexico — the official document that proves their identity and legal status. Whether you’re onboarding a customer for a fintech loan, verifying an employee’s credentials, or screening for AML compliance, programmatic verification of these ID cards is essential for a smooth, secure, and compliant workflow.

What Are the Main ID Cards in Mexico?

Mexico has several official identification documents, each serving a unique purpose. Understanding the differences is key to choosing the right verification approach.

CURP (Clave Única de Registro de Población)

The CURP is a unique alphanumeric code assigned to every Mexican citizen and resident. It is the most widely used identifier for government services, tax filings (RFC), social security (NSS), and many private-sector processes. The CURP card itself is a physical credential issued by RENAPO that includes the holder’s name, date of birth, gender, and a photograph. While the CURP number is public, the card serves as an official proof of identity.

INE (Instituto Nacional Electoral) Voter ID

The INE credential is the primary voting card in Mexico. It is also the most commonly accepted form of identification for financial and legal transactions. It includes a photograph, full name, address, date of birth, and a unique voter ID number. The INE is issued by the National Electoral Institute and is valid for 10 years for citizens aged 18 and older.

Mexican Passport

Issued by the Secretariat of Foreign Affairs (SRE), the Mexican passport is a travel document that also serves as a high-security ID. It contains the holder’s photograph, signature, and biometric data. Passports are often used for international verification and cross-border compliance.

Temporary or Permanent Resident Card

For foreigners living in Mexico, the resident card (issued by INM) is the official ID. It includes a photograph, fingerprint, and unique CURP number. This card is essential for verifying the legal status of non-citizens.

How to Verify a Mexican ID Card Programmatically

Programmatic verification allows you to validate the authenticity of an id card mexico in real time, without manual data entry or document scanning. The most effective approach is to use a CURP API that connects directly to the Mexican government’s population registry (RENAPO).

Using CURP API for Real-Time Validation

A CURP API typically accepts a CURP number as input. Some providers also accept additional fields such as full name and date of birth for stronger matching. The response includes:

• Validation status (e.g., valid, invalid, or not found)
• Full name (as registered with RENAPO)
• Date of birth, gender, and state of birth
• AGEB code (Área Geoestadística Básica) — a geographic code that identifies the exact neighborhood or block of the person’s registered address
• Fraud signals (velocity checks, cross-client duplicate detection)

For example, the CURP API at API Pull returns these fields in a standard JSON response, making it easy to integrate into any onboarding flow.

Cross-Referencing with INE and Passport Data

While CURP is the backbone, some use cases require verifying the INE credential number or passport number. Not all API providers support this, but those that do can cross-reference the CURP against the INE database or SRE passport records. This is especially useful for regulated industries like banking or insurance.

Demographic Enrichment: Getting AGEB and Geographic Data

The AGEB code returned by a CURP API can be used to enrich your understanding of the user’s location. By combining CURP data with INEGI’s census data, you can derive demographic insights such as income level, educational attainment, and access to services. This is valuable for risk assessment, marketing segmentation, and fraud detection.

Why ID Card Verification Matters for Compliance (AML and KYC)

Financial institutions and regulated entities in Mexico are required to comply with anti-money laundering (AML) and know-your-customer (KYC) regulations. These regulations often mandate the verification of official identification documents.

Understanding AML Screening Requirements in Mexico

AML screening in Mexico involves checking against multiple lists:

• SAT 69-B list — Mexican tax authority’s list of fake invoice issuers
• OFAC — U.S. Office of Foreign Assets Control sanctions list
• UN consolidated list — United Nations sanctions
• PEP databases — Politically Exposed Persons from Mexico and other countries

An AML API Mexico can automate these checks, often using the CURP as the primary identifier. This ensures that your onboarding process meets CNBV compliance guidelines.

Incorporating CURP Validation into KYC Flows

A typical KYC flow for a Mexican user might be:

1. User enters their CURP number.
2. The CURP API validates the number and returns the name and date of birth.
3. The user provides a selfie or scans their ID card to match the photo.
4. The system runs an AML check using the CURP.

This flow combines document verification with biometric matching and sanctions screening, giving you a robust identity assurance.

Respecting ARCO Rights: Data Privacy and User Control

ARCO rights (Access, Rectification, Cancellation, and Opposition) are part of Mexico’s Federal Law on Protection of Personal Data Held by Private Parties. When you collect and verify identity data, you must:

• Allow users to access their stored data.
• Enable corrections if the data is wrong.
• Delete data upon request (unless legally required to keep it).
• Allow users to oppose the processing.

Your API integration should include a way to log these requests and respond appropriately. The CURP API documentation provides guidance on data retention and audit trails.

Integrating Mexican ID Card Verification into Your Onboarding Flow

Integrating a CURP API is straightforward. Here’s a step-by-step overview.

Step-by-Step Integration with the CURP API

1. Sign up for a sandbox environment — Most providers offer a sandbox with synthetic test cases that mimic real responses.
2. Send a POST request with the CURP number and optional fields (name, date of birth).
3. Parse the response — validate the status, extract the citizen data, and store it in your system.
4. Handle errors — invalid CURP, network timeout, or data mismatch.

For example, using the API Pull sandbox, you can simulate both valid and invalid CURP responses to test your integration.

Handling Edge Cases: Expired IDs, Data Mismatch, and Fraud Signals

• Expired IDs: The CURP itself does not expire, but the card may be outdated. The API will still return the current data from RENAPO.
• Data mismatch: If the name or date of birth provided by the user does not match the CURP record, the API may return a warning. This is a red flag for identity theft.
• Fraud signals: Some APIs include velocity checks (e.g., multiple requests from the same IP in a short time) and cross-client duplicate detection. These alerts help you block fraudulent accounts.

Bulk Verification for High-Volume Operations

If you need to verify hundreds of CURPs at once, look for a provider that offers a bulk endpoint. For example, you can submit up to 100 CURPs in a single request and receive the results asynchronously via webhooks. This is ideal for HR onboarding, loan origination, or batch screening.

When ID Card Verification Is the Wrong Tool

While CURP and ID card verification is powerful, it’s not suitable for every scenario.

When You Need Biometric Verification (Face Matching)

If you need to confirm that the person presenting the ID is the same person in the photo, you need a biometric face-matching solution. CURP verification alone cannot do this. However, you can combine both: first verify the CURP, then use a third-party facial recognition API to compare the user’s selfie with the ID card photo.

When You Need Address Verification Only

If your only requirement is to confirm that a user lives at a specific address, a utility bill or bank statement may be more appropriate. CURP verification returns the registered address (via AGEB), but it may not be current. For address verification, consider using a document scanning API that extracts address text from official documents.

When You Need Payment Method or ACH Verification

Verifying an ID card does not verify the user’s bank account. For payment flows, you need a separate API for bank account validation (e.g., CLABE verification) or a payment gateway that handles ACH transfers.

Next Steps: Start Verifying Mexican IDs with API Pull

Now that you understand the landscape, it’s time to implement. Start by exploring the CURP API documentation to see the exact request/response format. You can sign up for a free sandbox environment and test with synthetic data.

If you need to bundle CURP verification with AML screening, check out the AML API Mexico for sanctions and PEP checks. For a broader view of available APIs, visit the API Hub to compare providers.

Our team is ready to help you design a custom integration for your specific use case — whether you’re a fintech, an insurance company, or a regulated entity. Contact us to discuss your requirements.

FAQ

What is the primary ID card in Mexico? The most common ID card is the CURP card, but the INE voter ID is also widely used for financial transactions.

Can I verify a Mexican ID card with an API? Yes, CURP APIs allow real-time validation of the CURP number against RENAPO, and some providers also support INE and passport verification.

Is CURP verification enough for AML compliance? No, you also need to screen against sanctions and PEP lists. An AML API that uses CURP as the identifier can automate this.

What is AGEB data? AGEB stands for Área Geoestadística Básica, a geographic code from INEGI that identifies neighborhoods. It can be used for demographic analysis.

How do I handle ARCO rights? Your system should allow users to request access, correction, deletion, or opposition to their data. Document these requests and respond within legal timeframes.