通过人脸识别恢复丢失的账户。

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.

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.

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).

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.

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.

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.

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.

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.

• 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.

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.

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.

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.