한 번 인증. 영원히 재사용. 동일한 브랜드. 신뢰할 수 있는 파트너. 동일한 신원.

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.

It's an identity verification you do once, full document + face + AML, that the user can then re-present on every future service without redoing the document capture.

Two flavours:

• Same brand · second app, the user signs up to your savings product, then to your trading product. Same Didit verification, free selfie-only reauth on the second app via Reusable KYC.
• Trusted partner · fresh signup, the user is verified on Partner A and signs up to Partner B. Partner A mints a short-lived encrypted share token; Partner B imports it; the user lands fully onboarded with no re-capture.

The credential lives with the user, they consent to each reuse. The shape of the data they share is auditable, scoped, and time-bound.

Three things drop:

• Drop-off, every additional document re-capture loses 15-30% of conversions. Removing the friction recovers most of that.
• Cost, the second verification is free instead of another $0.33. At any meaningful scale this becomes a line item your CFO notices.
• Time-to-onboard, sub-2-second selfie reauth versus several minutes of re-capturing IDs from the start.

For the user, the benefit is just "I already did this". For the platform, it's higher activation, lower CAC (Cost of Acquisition), and a competitive moat against any flow that doesn't reuse.

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.

eIDAS 2 (officially Regulation (EU) 2024/1183) is the EU's updated digital-identity regulation, it mandates that every EU citizen gets access to a European Digital Identity Wallet by late 2026.

The wallet's defining property is exactly what reusable identity delivers: the user holds verified credentials in a wallet they control, and re-presents them on demand to public and private services. Didit's reusable-identity recipe is aligned with eIDAS 2, same shape, same user-ownership principle, so platforms building on it today are also building toward the EU's official-wallet world.

Outside the EU, the same recipe still works. The legal anchor is local (UK FCA, US state lender rules, etc.); the technical shape is the same.

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.

Two consent moments:

• At first verification, standard KYC consent: data processed for verification + screening, retention, sub-processors, etc. (the privacy notice you ship today)
• At reuse, for cross-partner shares, explicit consent before the share token is generated. Your UI shows: "You will be onboarded on Partner B using the identity you verified with Partner A. The shared data covers ID, face match, AML status. The share expires in 15 minutes."

Didit logs the consent against the session, purpose, audience, scope, expiry, and the log is exportable to your data-subject-access-request (DSAR) and audit tools. Default retention 5 years post-relationship per the EU Anti-Money-Laundering package. Aligned with the General Data Protection Regulation (GDPR), ISO/IEC 27001, and SOC 2 Type 1, all of which Didit holds.

Three load-bearing limits:

• Finished sessions only, a share token can only be generated for sessions with a terminal status (Approved, Declined, In Review). Pending sessions can't be shared.
• One import per partner, a specific session can be imported only once into a given partner application. Subsequent imports are rejected. (If the partner needs to re-import, the user must verify fresh or Partner A must mint a new token.)
• Short-lived + audience-bound, the token defaults to a 15-minute expiry and is only valid for the named audience. Stolen tokens can't be re-targeted at a different partner.

The token is signed and end-to-end encrypted. The only thing that travels between Partner A and Partner B is the opaque token; the underlying data fields stay inside Didit until Partner B's authenticated import call.

Pricing breakdown:

• First verification, $0.33 per user (Sessions API), paid by the verifier
• Same-platform Reusable KYC reauth, free, included
• Cross-partner import, Partner B pays the import fee, from `$0.30` per call, on Partner B's account
• Workflow Builder + MCP server, free, included
• 500 verifications free every month, forever, on every account

The model rewards reuse: the verifier pays once, the user re-uses many times on the same brand for free, and the only paid step at a partner is the import call, which is materially cheaper than the partner running fresh KYC themselves.