Mexican telcos integrated Veridas' architecture into WhatsApp to meet the Guidelines for the Identification of Mobile Phone Lines.
Regulatory Compliance and Digital Identity Verification on WhatsApp ↗
What happened
- The article reports that the solution runs four validation stages: document verification, active liveness, 1:1 facial biometrics and INE database check.
- The article states that clients carried out more than 100 million online identity verifications in 9 months to comply with the Guidelines.
- The article states the system handled peaks of over 6,000 verifications per minute.
Why it matters to Signicat
- The case shows a competitor in Latin American telco identity verification embedded in a messaging channel, an area outside Signicat's listed core markets.
- The article's WebView-versus-native-capture argument targets in-chat document capture, a counter-positioning point relevant to Signicat's document IDV offering.
Evidence from the source (5 quotes)
- “4. Official Validation (INE Check):** Real-time security query against INE databases to confirm the validity of the document.” source ↗
- “Clients have carried out more than 100 million online identity verification processes in just 9 months to comply with the mandate of the Guidelines” source ↗
- “Proven capacity to absorb traffic peaks of over 6,000 verifications per minute” source ↗
- “Mexico’s leading telcos understood that the key was not only in their web, app, or physical store channels” source ↗
- “Unlike native capture within the chat—which exposes images to phone galleries, application history, and Meta backups—Veridas’ WebView architecture isolates the biometric process completely.” source ↗
Document IDV biometricsFraud deepfake injectionDeveloper experienceCase studyGlobal
4 of 4 facts verified against the source · confidence medium · claude-haiku-5-5