Multi-layered verification pipeline that combines document analysis, biometric matching, liveness detection, and fraud prevention into a single API call. 34 countries, OCR optimised for English and Swedish, typically under 60 seconds end-to-end.
Prevent fraud, ban evasion, and anonymous abuse on platforms where adults interact with children. Deployed on GCP Cloud Run in EU (europe-west1). Image processing runs on our own infrastructure and no document or selfie image is sent to any language model.
Countries with algorithmic document validation
UI languages supported
End-to-end pipeline
Three-step pipeline
Document scan
Users photograph the front (and optionally back) of their ID or passport. ICAO 9303 MRZ parsing, PDF417 barcode decoding, and multi-pass OCR extract structured data, with text recognition currently optimised for English and Swedish.
Face matching
128-dimensional face descriptor matching compares the document photo to a live selfie, confirming the document belongs to the person holding the phone.
Liveness challenge
HMAC-signed challenge-response with landmark motion tracking, texture analysis (Laplacian variance), depth-of-field cues, and cross-frame consistency. Catches photos, screens, masks, and deepfakes.
Document Intelligence
Fraud Detection
Biometric Verification
Why identity verification matters
On platforms where adults interact with children, knowing someone's age isn't enough. You need to know who they are.
Ban evasion prevention
Link accounts to verified identities. When a bad actor is banned, they can't just create a new account, their identity is already flagged.
Anonymous abuse deterrence
Require identity verification before users can send direct messages to minors, reducing anonymous harassment and predatory contact.
Risk-based step-up
Trigger additional identity verification when risk signals are detected, e.g., a user flagged for grooming patterns is asked to verify before continuing.
Trusted adult verification
On platforms where adults interact with children (tutoring, coaching, mentoring), verify the adult's identity before granting access.
What you get back
Architecture
Frequently asked questions
What is the difference between age verification and identity verification?
Age verification confirms only that the user meets a specific age threshold. Identity verification confirms who the user is, matching a government-issued document to a live face capture and returning a unique, persistent identity signal used to prevent ban evasion.
Which documents does Tuteliq's identity verification accept?
Tuteliq supports passports, national ID cards and driver's licences issued by 34 countries, with algorithmic document validation and ICAO 9303 MRZ parsing where available.
How does Tuteliq prevent ban evasion?
Verified identities are hashed and stored as an opaque identity signal. Repeat sign-ups from a banned identity are blocked without exposing the underlying document data to the platform.
How long does a verification take?
The full pipeline (document capture, OCR, liveness, face match, ban-evasion lookup) typically completes in under 60 seconds.
Is Tuteliq's identity verification GDPR compliant?
Yes. All processing happens inside the EU on our own GCP infrastructure, with zero content retention. Only the pass/fail decision and the identity hash are persisted.
Ready to verify?
Included on the Assure plan and above. 25 credits per verification.
Combine with grooming detection for the most complete child safety pipeline available.