Best approach for CURP KYC API integration in a neobank onboarding flow?
Question
Answers
We run about 800 CURP KYC validations daily through a provider we found on apipull.com API Hub. Response times average around 280ms and the match rate against RENAPO is consistently above 99%. They return the full demographic payload including both paternal and maternal surnames, which is critical for proper name matching.
For data freshness — our provider syncs with RENAPO every 6 hours for their cache layer, but real-time validations actually hit RENAPO directly through their authorized channel. So new CURPs show up almost immediately. The cache is only used as a fallback when RENAPO is temporarily unavailable.
One thing to watch: make sure the provider differentiates between "CURP not found" and "RENAPO temporarily unavailable." Some cheaper providers return the same error for both, which creates false rejections in your onboarding funnel.
Make sure your CURP KYC API provider returns the full demographic payload — name, DOB, gender, state of birth. Some only return a boolean valid/invalid which isn't enough for CNBV compliance. You need to show your auditors that you verified the person's identity against an authoritative source, not just that "a CURP exists."
We combined CURP + INE in a two-step flow: first validate the CURP via API, then use OCR on the INE to extract the CURP printed on it. Cross-reference both. If they match, high confidence. If they don't, flag for manual review. Added about 2 seconds total to onboarding but our fraud rate dropped significantly.
We're building a neobank product targeting Mexico and need a solid CURP KYC API integration for our customer onboarding pipeline. The regulatory environment here requires us to verify identity documents before allowing account creation, and CURP is the most universal identifier for Mexican nationals.
Our current flow asks users to enter their 18-character CURP code during registration. We then need to validate that CURP against the official RENAPO database and pull back demographic information to cross-reference against what the user provided. This is a critical compliance step — if the CURP doesn't match or returns invalid data, we can't proceed with account opening.
What we specifically need from a CURP KYC API provider:
We evaluated scraping RENAPO's public consultation page but that approach is fragile, violates their ToS, and doesn't scale past a few hundred queries. We also looked at the official RENAPO SOAP interface but documentation is minimal and the endpoint stability is questionable based on what I've read in other forums.
Has anyone implemented a CURP KYC API through a third-party provider? I'm particularly interested in knowing about data freshness — how quickly do these providers reflect updates when someone gets a new CURP issued (name change, correction, etc)? For our compliance team, stale data is almost as bad as no data.
We're processing about 300 signups per day currently, expecting to scale to 2,000+ within the quarter. Need something that handles that volume without degradation. Budget is flexible but we prefer pay-per-query since our volumes are still growing.
Also curious if anyone has combined CURP KYC API validation with INE verification in a single pipeline — would love to hear about multi-step identity verification architectures for Mexico.