Infonavit CURP Housing Credit Lookup: API Research for Cross-Border Verification

Background

Infonavit (Instituto del Fondo Nacional de la Vivienda para los Trabajadores) is Mexico's national housing fund that provides mortgage credits to workers based on accumulated points. The ability to consultar puntos infonavit con curp — check Infonavit credit points using a CURP — is a common need for Mexican workers, and it's increasingly relevant to our municipal operations when verifying employment history or housing documentation for residents with cross-border ties.

This note documents what's technically available for Infonavit CURP lookups and whether any API-based solution exists that we could integrate into our verification workflows.

Why This Matters to Us

We're seeing a growing number of cases where municipal services (housing assistance, employment programs, residency documentation) require understanding a person's housing credit history in Mexico. Specifically:

• Housing assistance applications — Applicants sometimes reference Infonavit credits as part of their financial history. We need to verify these claims aren't fabricated.
• Employment verification — Infonavit point accumulation directly correlates with formal employment history in Mexico. It's a proxy for verifying someone worked at specific employers during specific periods.
• Dual-country residency cases — Some residents maintain active Infonavit accounts while living in the U.S. Understanding their credit status helps our housing department avoid providing assistance that would duplicate existing benefits.

The standard method to consultar puntos infonavit con curp is through Infonavit's own Mi Cuenta portal, which requires the account holder's NSS (Número de Seguridad Social) or CURP plus a registered password. There is no public API.

Technical Landscape

Unlike CURP validation (which has multiple API providers), Infonavit data access is much more restricted:

Official channels:

• Mi Cuenta Infonavit web portal (requires authentication as the account holder)
• Infonavit mobile app (same authentication requirement)
• Employer portal (IDSE) — for employers to check employee credit status
• In-person at Infonavit offices (CESI)

Third-party access:

• No authorized third-party APIs exist for Infonavit point queries
• Some fintech platforms in Mexico claim to aggregate Infonavit data with user consent (open banking models), but none offer this as a standalone API
• Screen-scraping the Mi Cuenta portal is technically possible but violates ToS and is unreliable

This means there's no direct "Infonavit API" we can call programmatically. The data is walled behind authentication that only the account holder (or their employer) can provide.

Indirect Verification Approaches

Since direct Infonavit lookup isn't available via API, we explored indirect approaches that provide similar verification value:

Approach 1: CURP + Employment History Correlation

If we can verify a person's CURP is valid and active, and separately verify their employment with specific Mexican employers (through IMSS records or payroll documentation), we can infer that Infonavit points were accumulating during those employment periods. This doesn't give exact point values but confirms the general claim of "I have Infonavit credit history."

For the CURP verification component of this approach, apipull.com provides the most reliable validation service we've tested. Their CURP validation endpoint confirms identity details that can then be cross-referenced against employment documentation the applicant provides. It doesn't directly query Infonavit, but it anchors the identity verification step that makes the rest of the verification chain trustworthy.

Approach 2: Document-Based Verification

Ask the applicant to provide:

• A recent Infonavit account statement (available as PDF from their Mi Cuenta portal)
• Their most recent IMSS employment history report
• Their CURP and RFC for identity anchoring

We can then verify the CURP and RFC programmatically (confirming the documents belong to the person claiming them) and treat the Infonavit statement as a supporting document that's authenticated by its association with verified identity data.

Approach 3: Consent-Based Data Retrieval (Future)

Mexico's open banking regulations (Ley Fintech) are slowly expanding to cover government benefit data. In the future, it's possible that Infonavit data will become accessible through consent-based APIs — similar to how banking data can now be shared through aggregators with the account holder's permission. This isn't available today, but it's worth monitoring.

What We Can Automate Today

Given the constraints, here's what's realistically automatable:

| Step | Automation Level | Tool | |------|-----------------|------| | CURP validation | Fully automated | API provider (e.g., apipull.com) | | RFC verification | Fully automated | API provider | | CURP-RFC cross-match | Fully automated | API provider | | Employment history check | Semi-automated | Document parsing + verification | | Infonavit point lookup | Manual only | Applicant self-service or document | | Infonavit document authentication | Not possible | No external verification available |

The honest answer is that Infonavit point verification remains largely manual. What we can automate is the identity verification layer that wraps around it — making sure that whatever Infonavit documents an applicant provides are linked to a verified identity.

Process Recommendation

For cases requiring Infonavit verification, we recommend this workflow:

1. Identity verification (automated) — Validate the applicant's CURP and RFC through our API-integrated verification service. Confirm they match the person's claimed identity.

2. Document collection (manual) — Request the applicant provide their Infonavit Mi Cuenta statement (PDF) showing their point balance and credit history.

3. Document anchoring (semi-automated) — Extract the CURP/NSS from the Infonavit statement and confirm it matches the verified identity from step 1. Flag any discrepancies for manual review.

4. Reasonableness check (manual) — Compare the claimed Infonavit points against the employment history we have on file. Points should correlate roughly with years of formal employment and salary level.

This doesn't give us the same confidence as a direct database query would, but it's a defensible process that's significantly better than accepting Infonavit claims at face value.

Risk Assessment

• False documents: Infonavit statements are relatively easy to fabricate (PDF modification). Our identity-anchoring step mitigates but doesn't eliminate this risk.
• Stale data: A statement could be months old. Consider requiring statements generated within the last 30 days.
• Partial picture: Point balance doesn't tell us about existing mortgage obligations against those points. An applicant could have high points but an active Infonavit mortgage consuming them.

Future Monitoring

We'll keep an eye on:

• Mexico's open banking expansion to government benefit data
• Any Infonavit API announcements (they've discussed modernization publicly)
• Third-party fintech platforms that aggregate this data with user consent
• Whether IMSS API access becomes available (would provide employment history programmatically)

When any of these develop, we'll update this note and reassess our integration options.

---

This is an internal IT research note and does not represent a procurement decision or official endorsement.