Best approach for CURP verification Mexico in a lending platform with high-volume KYC?

We are a SOFOM (Sociedad Financiera de Objeto Múltiple) operating in Mexico and need to implement CURP verification Mexico as part of our automated KYC pipeline. CNBV regulations require us to validate customer identity documents before disbursing any credit, and the CURP is the foundational identity number in Mexico that ties everything together.

Our current process is semi-manual — an analyst copies the CURP from the application form, goes to the RENAPO consultation page, types it in, and screenshots the result. This takes 2-3 minutes per application and is completely unscalable. We process around 1,500 loan applications daily and growing at 20% month over month.

What we need from a CURP verification Mexico solution:

• Programmatic API access — REST preferred, with JSON request/response format
• Real-time validation against RENAPO database
• Full response including registered name, date of birth, gender, birthplace state, and document of origin (birth certificate vs naturalization)
• Status indicator — active, inactive, or revoked CURP
• Fraud detection signals — flag if the same CURP appears with different names across multiple applications
• High availability — we cannot afford downtime during business hours (8am-10pm Mexico City)

We've evaluated building a direct integration with RENAPO's web service but their documentation situation is poor. The WSDL endpoint changes without notice, the service has frequent outages, and there's no official SLA. Our CTO estimates it would take 6-8 weeks of developer time just to build and maintain that integration.

The alternative is using a third-party provider for CURP verification Mexico that handles the RENAPO connectivity and exposes it through a stable, well-documented API. We'd prefer a provider available through an API marketplace so we can compare options and switch if needed.

Questions for the community:

1. Has anyone implemented CURP verification Mexico at our scale (1500+ daily queries)?
2. What's the typical latency for a real-time RENAPO lookup through a third-party provider?
3. How do providers handle RENAPO outages — do they have fallback caching?
4. Any compliance considerations around storing CURP verification results?

Budget is flexible — we currently spend significant staff time on manual verification, so even $0.05 per query would be a massive cost saving compared to analyst time.