Introduction
thibit is Mozambique-first KYC/KYB verification as a service. You send a
person to a hosted verification, and thibit reads their ID document, checks it
for tampering, matches their selfie to the document photo, and returns a
decision — accept, deny, or flag for review — with the per-check evidence.
It is engine-only and API-first. There is no case-management console and no workflow builder: compliance is served by webhooks plus a read-only verification log in the developer portal. You decide what a verification accepts; thibit runs it and tells you the result.
The two faces
thibit has exactly two integration surfaces:
- Integrator API (
/v1) — your backend creates a verification and gets back a hostedonboarding_url. You decide the accepted documents (country + type), send the link to your user, and receive the verdict by webhook or by polling. - Hosted onboarding — your user opens the link on their phone, captures the documents you allowed, and takes a selfie. They never need a thibit account.
The developer determines the surface; the applicant just follows the link.
Who it is for
- The integrator (primary) — a developer at a fintech, marketplace, lender,
or prop-tech app who wants a sandbox key, a clear
/v1API, and a working example in well under an hour. - The applicant — completes the hosted verification on their phone; no account.
What it verifies
- Documents — Mozambican Bilhete de Identidade and DIRE (format-aware templates), and passports + national IDs from ~any country via ICAO 9303 MRZ check-digits and per-country number validation.
- Authenticity — EXIF/metadata, Error-Level-Analysis, and pixel forensics.
- Liveness — selfie-to-document face match.
Next
- Quickstart — your first verification in a few curl calls.
- API reference — the full
/v1surface from the live OpenAPI. - Accepted documents — the allowlist model.