Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Urejeshaji wa akaunti

Rejesha akaunti iliyopotea kwa ukaguzi wa uso.

Badilisha maswali ya usalama na nambari za mara moja za SMS kwa kulinganisha tena biometriska dhidi ya selfie ya usajili. Uamuzi wa chini ya sekunde 2, ~$0.15 kwa urejeshaji, iBeta Level 1 imethibitishwa.

Anza bureSoma nyaraka
Inaungwa mkono na
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

Inaaminika na mashirika 2,000+ duniani kote.

Mchoro wa sinema, giza, dhahania wa urejeshaji nenosiri, paneli nne za glasi zinazoelea, zinazopitisha mwanga katika mtazamo wa 3D kwenye nyeusi safi, zikipitishwa na mstari mweupe wa Didit Blue na zikizungukwa na mabano manne ya skana yanayong'aa. Kila paneli ina motifu ndogo, nyeupe-nyepesi, dhahania (muhtasari wa kufuli, mviringo wa uso, kitanzi cha mshale wa kuonyesha upya, ufunguo).

Kwa nini ukaguzi wa uso unashinda SMS

Thibitisha tena utambulisho. Sio maarifa. Ndani ya sekunde mbili.

SIM-swap inashinda nambari za SMS za mara moja. Phishing inashinda maswali ya usalama. Wawakilishi wa usaidizi wanajishinda wenyewe chini ya shinikizo. Ulinganishaji wa uso wa moja kwa moja dhidi ya selfie ya usajili inashinda zote tatu, kwa $0.15 kwa urejeshaji, uamuzi wa chini ya sekunde mbili, 500 bure kila mwezi.

Jinsi inavyofanya kazi

Kuanzia kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.

  1. Hatua 01

    Unda mtiririko wa kazi

    Chagua ukaguzi unaotaka, ID, liveness, ulinganishaji wa uso, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko kwenye dashibodi, au tuma mtiririko huo huo kwenye API yetu. Panga masharti, fanya majaribio ya A/B, hakuna code inayohitajika.

  2. Hatua 02

    Unganisha

    Pachika asili na SDK yetu ya Web, iOS, Android, React Native, au Flutter. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu mtumiaji wako kiungo, kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa stack yako.

  3. Hatua 03

    Mtumiaji anapitia mtiririko

    Didit inasimamia kamera, ishara za mwanga, uhamishaji wa simu, na ufikiaji. Wakati mtumiaji yuko kwenye mtiririko, tunapima ishara 200+ za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya mamlaka. Matokeo chini ya sekunde mbili.

  4. Hatua 04

    Unapokea matokeo

    Webhooks zilizosainiwa kwa wakati halisi huweka database yako sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Piga API inapohitajika. Au fungua console kukagua kila session, kila ishara, na kudhibiti kesi kwa njia yako.

Imejengwa kwa usalama · Bei kama miundombinu

Ukaguzi mbili. Simu moja. $0.15 kwa urejeshaji.

Urejeshaji si ukaguzi mmoja, ni mapishi. Liveness inakataa shambulio, Face Match inaidhinisha mtumiaji, njia mbadala huweka watumiaji wasio na kamera salama. Yote kwenye simu moja ya /v3/session/.
Soma nyarakaPata API key
01 · Uthibitishaji upya wa Selfie

Linganisha selfie ya kurejesha. Idhinisha mtumiaji.

Face Match 1:1 inalinganisha selfie ya moja kwa moja na selfie ya usajili ya mtumiaji iliyohifadhiwa. Alama ya kufanana juu ya kizingiti kilichosanidiwa (chaguomsingi 0.85) inaidhinisha urejeshaji. $0.05 kwa ulinganishaji, uamuzi wa chini ya sekunde mbili.
Moduli ya Face Match 1:1
02 · Ukaguzi wa Liveness

Kataa chapa, skrini, barakoa, deepfakes.

Passive Liveness inatumia ishara za Presentation Attack Detection (PAD), hakuna vidokezo vya kuinamisha kichwa, hakuna usumbufu. Imethibitishwa na iBeta Level 1. $0.10 kwa ukaguzi. Liveness hai ($0.15) inapatikana kwa programu zenye uhakikisho wa juu.
Moduli ya Liveness
03 · Vianzisha vya kuongeza usalama

Anzisha urejeshaji kwa ishara sahihi ya hatari.

Umesahau nenosiri, kuingia kwa kifaa kipya, kuingia kwa nchi mpya ya IP, kutotumika, hatua nyeti. Sanidi kwa kila hali katika Workflow Builder isiyo na code, vianzisha vya hatari kubwa huenda moja kwa moja kwenye uso + liveness, vianzisha vya hatari ndogo huenda kwenye uso pekee.
Mratibu wa Mtiririko wa Kazi (Workflow Orchestrator)
04 · Njia mbadala

Wakati selfie haiwezekani.

Hakuna kamera, mwanga hafifu, ruhusa ya maunzi imekataliwa, rudi nyuma kwa upole. Uthibitishaji wa Simu (Short Message Service / WhatsApp / Telegram One-Time Passcode) kwa $0.03 kwa OTP, kiungo cha barua pepe cha uchawi, programu ya Time-based One-Time Password (TOTP) authenticator. Selfie daima ni ya msingi.
Moduli ya Uthibitishaji wa Simu
05 · Rekodi ya ukaguzi

Kila urejeshaji kwenye rekodi.

vendor_data, alama ya kidole ya kifaa, nchi ya IP, alama ya kufanana, uamuzi, kila jaribio la urejeshaji linaweza kutafutwa kwenye Business Console, linaweza kusafirishwa kwa kila kesi. Udhibiti wa SOC 2 Type 1 + ISO 27001.
Dashibodi ya Biashara
06 · Sera ya Session

Mzunguko wa uthibitishaji upya, kwa kila programu.

Kila kuingia, kila baada ya siku 7, kwenye hatua nyeti, kwenye kasoro ya ishara, chagua mzunguko kwa kila programu ya Didit. Uthibitishaji wa Biometric ($0.10 kwa uthibitishaji) unaongeza Face Match primitive hiyo hiyo kwenye mtiririko wa kuingia mara kwa mara.
Moduli ya Uthibitishaji wa Kibayometriki
Unganisha

Session moja. Webhook moja. Urejeshaji umefunguliwa.

Fungua session ya urejeshaji kwenye trigger sahihi. Soma uamuzi uliosainiwa. Fungua au panda ngazi.
POST /v3/session/Urejeshaji
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflow_id": "wf_account_recovery",
    "vendor_data": "user-7382",
    "metadata": { "trigger": "forgot_password" },
    // base64 enrolment selfie, ≤ 1MB
    "portrait_image": "/9j/4AAQSkZJRgABAQE..."
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
Zuia urejeshaji hadi webhook iseme status: Approved.nyaraka →
POST /webhooks/diditUamuzi
// X-Signature-V2 verified upstream
if (payload.status === "Imeidhinishwa") {
  tumaBaruaPepeYaKurejeshaNenosiri(payload.vendor_data);
  sajiliKifaaKipya(payload.metadata);
} vinginevyo ikiwa (payload.status === "Imekataliwa") {
  security.logRecoveryAttack(payload);
}
200OKhali Imeidhinishwa · Imekataliwa · Inapitiwa · KYC Imeisha Muda
Thibitisha X-Signature-V2 kabla ya kusoma payload.nyaraka →
Ujumuishaji tayari kwa agent

Weka mfumo wa kurejesha akaunti kwa amri moja.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent huunganisha trigger, hufungua session, husoma uamuzi, na hufungua au kupandisha suala.
didit-integration-prompt.md
You are integrating Didit into an account-recovery flow. Replace knowledge-based recovery (security questions, SMS OTP, support-rep verification) with a biometric re-match against the user's enrolment selfie. ONE Didit session, two checks:

  - Passive Liveness — make sure the recovery selfie is a real human, not a print / screen / mask / deepfake.
  - Face Match 1:1 — match the recovery selfie against the user's enrolment selfie. If similarity is above your threshold, the recovery is approved.

Bundle pricing (verified live, 2026-05-16):
  - Passive Liveness: $0.10 per recovery
  - Face Match 1:1: $0.05 per recovery
  - Total: ~$0.15 per recovery — public price, no minimums
  - First 500 verifications free every month, forever
  - SMS / WhatsApp One-Time Passcode (OTP) fallback: $0.03 per OTP (when biometric isn't possible)

PRE-REQUISITES
  - Production API key from https://business.didit.me (sandbox key in 60s, no card).
  - Webhook endpoint with HMAC SHA-256 verification using the X-Signature-V2 header.
  - User's enrolment selfie on file — captured during initial KYC via a previous /v3/session/. Stored under your tenant in encrypted form.
  - A workflow_id from the Workflow Builder that runs Passive Liveness + Face Match 1:1 against the stored reference.

STEP 1 — Trigger recovery on the right signal

  Recovery is gated by your risk policy. Typical triggers:

  - User clicks "Forgot password" — always.
  - Sign-in from a new device + new IP country at the same time.
  - Sign-in after account dormancy (e.g. 180+ days).
  - Sensitive action: large withdrawal, payout to a new beneficiary, account-settings change.

  Each trigger opens a Didit session.

STEP 2 — Open the recovery session

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<wf id with Passive Liveness + Face Match against enrolment selfie>",
      "vendor_data": "<your user id, max 256 chars>",
      "callback": "https://<your-app>/account/recovery/callback",
      "metadata": {
        "trigger": "forgot_password",
        "device_fingerprint": "<your device fingerprint>",
        "ip_country": "ES"
      },
      "portrait_image": "<base64 JPEG of the user's enrolment selfie, ≤ 1 MB — REQUIRED when the workflow has FACE_MATCH active; the recovery flow matches the new live selfie against this stored reference>"
    }

  Response: 201 Created with a hosted session URL. Redirect the user (web or in-app webview) to the URL. Sub-2-second median verdict on completion.

STEP 3 — Read the signed webhook on the verdict

  Didit POSTs to your callback. Session statuses are Title Case With Spaces:

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your user id>",
      "status": "Approved",
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94 }
    }

  Status enum (exact case): Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned.

  Verify the X-Signature-V2 header BEFORE reading the body — HMAC SHA-256 of the raw bytes with your webhook secret.

STEP 4 — Branch on the verdict

  Approved          → unlock recovery: send the password-reset email, register the new device, complete the sensitive action.
  In Review         → soft-fail the recovery, route to support for human review.
  Declined          → block the recovery; log the hit. Could be a printed-photo or screen-replay attack — surface to security.
  Resubmitted       → user retried after a soft rejection — re-read.
  Kyc Expired       → reference selfie has aged out (per your retention policy) — fall back to documented recovery flow.

STEP 5 — Fallback for users who can't take a selfie

  Camera missing, low light, hardware refused permission. Two graceful fallbacks:

  - SMS / WhatsApp / Telegram One-Time Passcode (OTP) via Didit Phone Verification, $0.03 per OTP.
  - Email magic link via your existing transactional email provider, $0.03 per email.
  - Authenticator app — Time-based One-Time Password (TOTP) or FIDO2 hardware key, free.

  Configure the fallback chain in the Workflow Builder. Selfie always tried first.

WEBHOOK EVENT NAMES
  - Sessions: status changes flow through the standard session webhook.

  Verify X-Signature-V2 on every payload.

CONSTRAINTS
  - Session statuses use Title Case With Spaces (Approved, In Review). Do not lowercase or snake_case them.
  - The recovery similarity threshold is configurable per app — start at 0.85, tune up for high-assurance apps (banks, brokerages) and down for low-friction consumer apps.
  - Liveness is a Presentation Attack Detection (PAD) Level 1 model — defeats prints, screens, masks, deepfakes on consumer cameras. Active liveness (head-tilt prompts) is available for higher-friction higher-assurance flows at $0.15.
  - The user's enrolment selfie must have been captured by Didit (any prior /v3/session/ with face capture). Bring-your-own enrolment image is roadmap.
  - Default audit retention is 5 years configurable in the Business Console.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/core-technology/face-match/overview
  - https://docs.didit.me/core-technology/liveness/overview
  - https://docs.didit.me/integration/webhooks

Start free at https://business.didit.me — sandbox key in 60 seconds, 500 verifications free every month, no credit card.
Unahitaji maelezo zaidi? Tazama nyaraka kamili za moduli.docs.didit.me →
Inatii kwa muundo

Fungua nchi mpya kwa kubofya mara moja. Tunafanya kazi ngumu.

Tunafungua kampuni tanzu za ndani, tunapata leseni, tunafanya majaribio ya kupenya, tunapata vyeti, na tunalingana na kila kanuni mpya. Ili kusafirisha uthibitishaji katika nchi mpya, geuza swichi. Nchi 220+ ziko hewani, zinakaguliwa na kupimwa kila robo mwaka, mtoa huduma pekee wa utambulisho ambaye serikali ya nchi mwanachama wa EU imemwita rasmi kuwa salama zaidi kuliko uthibitishaji wa ana kwa ana.
Soma faili ya usalama na utiifu
EU financial sandbox
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
Usalama wa habari · 2026
SOC 2 · Type I
AICPA · 2026
iBeta Level 1 PAD
NIST / NIAP · 2026
GDPR
EU 2016/679
DORA
EU 2022/2554
MiCA
EU 2023/1114
AMLD6 · eIDAS 2.0
EU-aligned kwa muundo

Namba zinazothibitisha

Namba zinazothibitisha
  • ~$0.15
    Kwa kila urejeshaji uliokaguliwa kikamilifu, Passive Liveness + Face Match 1:1.
  • <0s
    Uamuzi kamili kwa kila session, kwenye Android ya kiwango cha chini.
  • iBeta L1
    Uthibitisho wa Presentation Attack Detection (PAD), hushinda alama za vidole, skrini, barakoa, deepfakes.
  • 0
    Uthibitishaji wa bure kila mwezi, kwenye kila akaunti.
Ngazi tatu, orodha moja ya bei

Anza bure. Lipa kulingana na matumizi. Panua hadi Enterprise.

Uthibitishaji 500 bila malipo kila mwezi, milele. Lipa kadri unavyotumia kwa uzalishaji. Mikataba maalum, uhifadhi wa data, na SLA (Service Level Agreements) kwenye Enterprise.
Bure

Bure

$0 / mwezi. Hakuna kadi ya mkopo inayohitajika.

  • Kifurushi cha bure cha KYC (Uthibitishaji wa Kitambulisho + Passive Liveness + Face Match + Uchambuzi wa Kifaa & IP), 500 / mwezi, kila mwezi
  • Watumiaji Waliozuiwa
  • Utambuzi wa Marudio
  • Ishara 200+ za udanganyifu kwenye kila session
  • KYC inayoweza kutumika tena kwenye mtandao wa Didit
  • Jukwaa la Usimamizi wa Kesi
  • Workflow Builder
  • Nyaraka za umma, sandbox, SDKs, server ya MCP (Model Context Protocol)
  • Usaidizi wa jamii
Anza bure
Maarufu zaidi
Lipa kulingana na matumizi

Kulingana na Matumizi

Lipa tu kwa unachotumia. Moduli 25+. Bei za umma kwa kila moduli, hakuna ada ya chini ya kila mwezi.

  • KYC kamili kwa $0.33 (Kitambulisho + Biometric + IP / Kifaa)
  • Data za AML 10,000+, vikwazo, PEPs, habari hasi
  • Vyanzo vya data vya serikali 1,000+ kwa Uthibitishaji wa Database
  • Ufuatiliaji wa Miamala kwa $0.02 kwa kila muamala
  • KYB ya moja kwa moja kwa $2.00 kwa kila biashara
  • Uchunguzi wa Wallet kwa $0.15 kwa kila ukaguzi
  • Mtiririko wa uthibitishaji wa Whitelabel, brand yako, miundombinu yetu
Tazama orodha kamili ya beiAnza bure
Biashara Kubwa

Biashara Kubwa

MSA & SLA maalum. Kwa idadi kubwa na programu zilizodhibitiwa.

  • Mikataba ya kila mwaka
  • MSA, DPA, na SLA maalum
  • Kituo maalum cha Slack na WhatsApp
  • Wakaguzi wa mikono wanapohitajika
  • Masharti ya muuzaji na white-label
  • Vipengele vya kipekee na ushirikiano wa washirika
  • CSM aliyetajwa, ukaguzi wa usalama, usaidizi wa kufuata
Wasiliana nasi

Anza bure → lipa tu wakati ukaguzi unafanyika → fungua Enterprise kwa mkataba maalum, SLA, au uhifadhi wa data.

FAQ

Maswali ya kawaida

What is Didit?

Didit is infrastructure for identity and fraud, the platform we wished existed when we were building products ourselves: open, flexible, and developer-friendly, so it works as a real part of your stack instead of a black box you integrate around.

One API covers verifying people (KYC, know your customer), verifying businesses (KYB, know your business), screening crypto wallets (KYT, know your transaction), and monitoring transactions in real time, on a stack built to be:

  • Fast, sub-2-second p99 on every session
  • Reliable, in production with 1,500+ companies across 220+ countries
  • Secure, SOC 2 Type 1, ISO 27001, GDPR-native, and formally attested by Spain's financial regulator as safer than verifying someone in person

The footprint underneath: 14,000+ document types in 48+ languages, 1,000+ data sources, and 200+ fraud signals on every session. The Didit infrastructure dynamically learns from every session and gets better every day.

Why is password recovery a security weak point?

Because the recovery flow is the easiest place to bypass authentication. The user has forgotten the password, by definition you can't ask for it. Most apps fall back to:

  • Short Message Service (SMS) one-time codes, defeated by SIM-swap, signalling-protocol (SS7) interception, and rogue mobile operators.
  • Security questions, defeated by phishing, social-media research, and data-breach hashes.
  • Email magic links, defeated when the email account itself has been taken over.
  • Support-rep human verification, defeated by social engineering and pressure tactics on a tired agent.

A live face match against the enrolment selfie defeats all four.

What's wrong with SMS one-time codes specifically?

Three structural problems that won't go away:

  • SIM-swap attacks, an attacker convinces the carrier to port the number to a new SIM. Then the one-time codes arrive at the attacker.
  • Signalling-protocol (SS7) interception, telecom infrastructure flaws let attackers see SMS traffic for any number from anywhere in the world. Documented since 2014.
  • Two-Factor Authentication (2FA) prompt fatigue, the user gets so many codes that they approve attacker-initiated ones by reflex.

The US National Institute of Standards and Technology (NIST) has explicitly recommended against SMS for high-assurance recovery since 2017 (SP 800-63B).

How fast is the verification for my end user?

The full flow normally takes under 30 seconds end-to-end, pick up the ID, snap the document, snap the selfie, done. That is the fastest in the market. Legacy KYC providers usually take more than 90 seconds for the same flow.

On the back end, Didit returns the result in under two seconds at p99, measured from the moment the user finishes the selfie to the moment your webhook fires. Mobile capture is tuned for slow phones and slow networks: progressive image compression, lazy software development kit load, and a one-tap hand-off from desktop to phone via QR code if the user starts on web.

What if the user doesn't have an enrolment selfie on file?

Two scenarios:

  • Pre-existing users with no selfie, run a one-time enrolment flow first. Open a /v3/session/ with ID Verification + Face Match + Liveness, store the verified selfie on the user record. Cost: $0.33 (full KYC bundle).
  • New users, the enrolment selfie is captured during the standard KYC onboarding. Recovery is then automatic from the user's second sign-in onwards.

Bring-your-own enrolment image, your existing selfie corpus, is on the roadmap.

What happens if a user fails, abandons, or expires?

Every session lands on one of seven clear statuses, so your code always knows what to do:

  • Approved, every check passed. Move the user forward.
  • Declined, one or more checks failed. You can allow the user to resubmit the specific failed step (for example, re-take the selfie) without re-running the whole flow.
  • In Review, flagged for compliance review. Open the case in the console, see every signal, decide approve or decline.
  • In Progress, user is mid-flow.
  • Not Started, link sent, user has not opened it yet. Send a reminder if it sits too long.
  • Abandoned, user opened the link but did not finish in time. Re-engage or expire.
  • Expired, the session link aged out. Create a new session.

A signed webhook fires on every status change, so your database always stays in sync. Abandoned and declined sessions are free.

Where does my customer data live and how is it protected?

Production data is processed and stored in the European Union by default, on Amazon Web Services. Enterprise contracts can request alternative regions for jurisdictions whose regulators require it.

Encryption everywhere. AES-256 at rest across every database, object store, and backup. Transport Layer Security 1.3 in transit on every API call, webhook, and Business Console session. Biometric data is encrypted under a separate Customer Master Key.

Retention is yours to control. Default retention is indefinite (unlimited) unless you configure shorter, between 30 days and 10 years per application, and you can delete any individual session at any time from the dashboard or the API.

Certifications: SOC 2 Type 1 (Type 2 audit in progress), ISO/IEC 27001:2022, iBeta Level 1 PAD, and a public attestation from Spain''s Tesoro / SEPBLAC / CNMV that Didit''s remote identity verification is safer than verifying someone in person. Full report at /security-compliance.

Is Didit compliant for my industry?

Didit ships compliant by default for the regulators that matter to identity infrastructure:

  • GDPR + UK GDPR, controller / processor split, full Data Processing Agreement published, lead supervisory authority named (Spain''s AEPD).
  • AMLD6 + EU AML Single Rulebook, 1,300+ sanctions, politically exposed person, and adverse-media lists screened in real time.
  • eIDAS 2.0, EU Digital Identity Wallet aligned; reusable-identity ready.
  • MiCA (Markets in Crypto-Assets), ready for crypto on-ramps, exchanges, and custodians.
  • DORA, Digital Operational Resilience Act, EU financial-services operational resilience.
  • BIPA, CUBI, Washington HB 1493, CCPA / CPRA, US biometric privacy (Illinois, Texas, Washington) and California consumer privacy.
  • UK Online Safety Act, age-gating and child-safety obligations.
  • FATF Travel Rule, originator and beneficiary data on crypto transfers, IVMS-101 interoperable.

Detailed memo, every certificate, every regulator letter: /security-compliance.

How fast can I integrate and start verifying users?
  • 60 seconds to a sandbox account at business.didit.me, no credit card.
  • 5 minutes to a working verification through Claude Code, Cursor, or any coding agent via our Model Context Protocol (MCP) server.
  • A weekend to a production-ready integration with signed-webhook verification, retries, and a remediation flow when a user is declined.

Three integration paths, pick whichever fits your stack:

  • Embed natively with our Web, iOS, Android, React Native, or Flutter SDK.
  • Redirect the user to the hosted verification page, zero SDK.
  • Send a link by email, SMS, WhatsApp, or any channel, zero front-end work.

Same dashboard, same billing, same pay-per-success price for all three. Step-by-step guide at docs.didit.me/integration/integration-prompt.

What about deepfakes, can someone defeat the recovery with an AI-generated face?

Passive Liveness defeats consumer-grade deepfakes today. The Presentation Attack Detection (PAD) model looks for:

  • Texture artefacts, screen sub-pixel patterns, print halftone, latex specular highlights.
  • Motion-temporal cues, micro-expressions, micro-saccades, natural eye-blink timing.
  • Geometric inconsistencies, lighting that doesn't match the depicted environment, perspective skew.

Didit's PAD model is iBeta Level 1 certified. Active Liveness ($0.15) adds head-tilt prompts for higher assurance against the rare professional-grade real-time deepfake.

Deepfake defence is an arms race, Didit retrains the PAD model on a quarterly cadence against the latest attack corpora.

Can I use recovery on every sign-in (true biometric login)?

Yes, that's Biometric Authentication, a recurring re-auth pattern. $0.10 per auth:

  • User signs in with their normal username (no password, they forgot it last week anyway).
  • A Face Match against the enrolment selfie runs in 2 seconds.
  • Approved → in. Declined → fall back to recovery + password reset.

Same /v3/session/ contract, different workflow_id. Common for crypto exchanges, banking apps, and high-assurance consumer products. See /products/biometric-authentication for the recurring-auth pattern.

How is the recovery flow audited?

Every recovery attempt logs:

  • The vendor_data (your user identifier) and Didit session_id.
  • The device fingerprint and Internet Protocol (IP) country.
  • The trigger you passed in metadata (forgot_password / new_device / dormancy / sensitive_action).
  • The Passive Liveness verdict and confidence.
  • The Face Match similarity score and verdict.
  • The webhook delivery confirmation.

Searchable from the Business Console, exportable per user, 5-year retention configurable. SOC 2 Type 1 + ISO 27001 controls govern the storage.

Related

Moduli zinazohusiana + mifumo ya kazi

Miundombinu ya utambulisho na udanganyifu.

API moja kwa KYC, KYB, Ufuatiliaji wa Miamala, na Uchunguzi wa Wallet. Unganisha ndani ya dakika 5.

Anza bila malipoZungumza nasi
Uliza AI ifupishe ukurasa huu