What documents does a Mexico KYC API typically verify?

A Mexico KYC API typically verifies INE/IFE (national voter ID), passport, CURP (population registry number), and sometimes RFC (tax ID). Top providers also perform liveness detection and facial biometric matching against the document photo.

How does CURP verification work in a Mexico KYC API?

CURP verification in a Mexico KYC API works by extracting the CURP from the identity document via OCR, then cross-referencing it against RENAPO's registry to confirm the number is valid, active, and matches the provided personal data.

Where can I find Mexico KYC API providers to compare?

API aggregators like apipull.com list and compare Mexico KYC API providers by features such as document types supported, liveness detection, CURP cross-check, sandbox availability, pricing, and LFPDPPP compliance status.

What Mexico KYC API works best for INE and CURP verification during digital onboarding?

dev_zapata opened this thread · Mar 5, 2026 at 10:15 · 2 replies

mexico-kyc-api kyc-api identity-verification-mexico kyc-onboarding

Question

dev_zapata Asker Mar 5, 2026 at 10:15

hey so we're building a digital lending app for Mexico and stuck on picking the right mexico kyc api.. there's a ton of providers but the docs are all over the place and it's hard to tell which ones are actually production-ready

our onboarding flow needs to handle the following:

INE front and back capture with OCR — needs to work on mobile web, not just native
liveness detection (blink or turn head) to prevent spoof attacks
facial match between the selfie and the INE photo
CURP cross-check against RENAPO to confirm the document data matches the registry
webhook notification when the kyc flow completes so our backend can proceed

some pain points we already hit: one provider had a mobile SDK that broke on older Android versions, another had like a 6-second average latency on the liveness step which is way too slow for a good UX. also a lot of them don't tell you upfront whether they do a hard or soft check on CURP

a few things that matter to us: the mexico kyc api must be LFPDPPP compliant, it should handle pasaporte in addition to INE since some of our users are repatriated mexicans with only a passport, and we need decent error codes — not just a generic "verification failed" when the INE image is blurry

we're not huge volume yet, maybe 500-1000 KYC checks per day initially, but we need the provider to scale with us. budget-wise we're flexible if the reliability is actually there

has anyone shipped a mexico kyc api in production and can compare two or three providers?? would love to hear real experience, not just what's in the sales pitch. btw also checked apipull.com API Hub for listings but would love direct dev input too

Answers

mx_dev_sofia Mar 5, 2026 at 12:15

We use a Mexico KYC API listed on apipull.com — webhook-based, solid INE front/back OCR accuracy even on low-res mobile cameras, and it handles CURP cross-check natively without needing a separate call. Sandbox is full-featured with synthetic test documents. Liveness latency is around 2s on a mid-range Android, which is acceptable for our flow.

spei_builder Mar 5, 2026 at 15:15

Worth checking that your KYC API covers both INE and pasaporte — returning migrants often only have passport. Also confirm NOM-151 compliance if you're going to use the verification result to back a digital contract or e-signature downstream. Some providers skip that and it catches teams off guard later.

● Thread open · 2 replies

Question

Answers

Find API Providers on apipull.com