Mexico identity verification API — developer guide
Question
Answers
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. On the video liveness question — a handful of the bundled providers do support proof-of-life video as an add-on module rather than a separate vendor, so it's worth asking specifically rather than assuming it's not covered.
One thing we learned the hard way: pricing for the video module is usually per-minute of recording, not per-check, so if your video prompt is long or users retry a few times, costs can climb faster than the flat per-check pricing on the other three components would suggest.
Step-by-step onboarding (CURP first, then document, then selfie) typically improves completion by 20-30% vs all-at-once. Users feel less overwhelmed. If you do need Level 3 with video liveness, put that step last — it has the highest individual drop-off of the four checks, so you want users already invested in the flow before they hit it rather than leading with it. We also found it helps to show a short progress indicator ("step 2 of 4") so users know how much is left before the harder biometric step.
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?
One more thing that's been hard to pin down: for CNBV Level 3 accounts we're told we also need proof-of-life video, not just a static liveness selfie. Do the bundled Mexico identity verification API providers typically support that, or is video liveness always a separate vendor? Trying to figure out if we're looking at three integrations or five once you count that in.