取代短信一次性密码。用自拍作为第二重认证。

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.

Second-factor authentication using the user's face, not a code sent over a network. The first factor is what the user knows (password, passkey, magic link). The second factor is what the user is, a live selfie matched 1:1 against a portrait the user enrolled earlier.

It sits in the same place as SMS one-time-password (OTP) in your application flow, but with a different cost, security, and conversion profile.

Four well-documented attack classes defeat it. The US Federal Bureau of Investigation (FBI) and UK National Cyber Security Centre (NCSC) have both published guidance steering organisations away from SMS for sensitive flows.

• SIM swap. Attacker convinces the carrier to port the user's number to a new SIM. Every code now goes to the attacker.
• OTP phishing. Attacker proxies the legitimate site, captures the code as the user types it, replays it before it expires.
• Smishing kits. Pre-built kits run thousands of fake delivery / bank texts that capture codes at scale.
• Signalling System 7 (SS7) interception. Adversaries with carrier access can passively read codes off the network.

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.

Most teams enrol during the user's original Know Your Customer (KYC) session. The portrait captured by the liveness step is stored bound to your vendor_data and used as the template for every subsequent re-authentication.

If you don't run KYC at sign-up, you can run a one-time enrolment session against a Didit workflow that contains only LIVENESS + FACE_MATCH. Either path costs $0.10 once, and the resulting template is reusable for every future authentication.

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.

It's a drop-in for your existing one-time-password callback contract.

• POST /v3/session/ with workflow_type: "biometric_authentication" and the same vendor_data you used at enrolment.
• Redirect the user to the returned session_url.
• Verify the X-Signature-V2 header on the webhook before trusting the body.
• Branch on status, Approved (execute the action), Declined (block), In Review (queue), Not Finished (re-prompt).

Most teams swap SMS for face in a weekend. Full agent-pastable prompt is above; Model Context Protocol (MCP) server speaks both surfaces.

Face Match 1:1 is resilient to moderate appearance change, facial hair, glasses, hair colour, lighting. The similarity score returned per authentication reflects how confident the model is.

For users who drift outside the auto-approve threshold (typical case: dramatic weight change, surgery, ageing over many years), the verdict returns In Review and routes to your operations queue. The standard recovery path is a re-enrolment session, one KYC call refreshes the portrait, and the next authentication uses the new template.

Yes for the inherence category. The European Banking Authority Regulatory Technical Standards on Strong Customer Authentication recognise biometric attributes (something you are) as a valid second factor when paired with one of the other two categories (knowledge or possession).

For a full PSD2 strong-customer-authentication flow, pair biometric 2FA with the user's password (knowledge) or a device-bound session (possession). The signed Didit verdict is the audit-pack evidence of the inherence factor.