Mexico identity verification API — developer guide
Question
D
Answers
S
Most mature Mexico identity verification API providers bundle document + CURP/RFC + liveness. Single integration is cleaner but check if each component meets CNBV's specific technical requirements.
R
Step-by-step onboarding (CURP first, then document, then selfie) typically improves completion by 20-30% vs all-at-once. Users feel less overwhelmed.
● Thread open · 2 replies
We're building a CNBV-regulated digital bank and need a robust Mexico identity verification API stack. We need to verify: government-issued ID (INE/IFE), CURP, RFC, and liveness check — all as part of our KYC flow.
The question is: do any Mexico identity verification API providers bundle all four into a single integration? Or is the industry standard to use separate providers for document verification vs government data vs biometrics?
Also — what's the typical conversion rate hit when you require all four checks at onboarding? Does breaking them into steps improve completion rates?