인증된 신원을 파트너와 공유하세요.
서버 간 연동으로.

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.

B2B Reusable KYC lets one business hand a verified user or company to another business, so the partner onboards the same person without running the verification again.

It works in two steps:

• Mint a share token. Pick a finished verification in your app, ask Didit for a one-time token tied to one named partner. Default lifetime is one hour; you can stretch it from one minute to a full day. Nobody else can ever redeem it.
• Your partner imports the session. They redeem the token and Didit clones the full record into their workspace, documents, selfie, face match, AML hits, registry data, Ultimate Beneficial Owners (UBOs). Same shape as a fresh verification, with a clean audit trail back to the original.

Your partner picks the onboarding speed. Trust your decision and approve the user instantly, or pull the data raw and let their compliance team make the call.

Works for both Know Your Customer (KYC) and Know Your Business (KYB), same call, both shapes.

Full reference: docs.didit.me/sessions-api/share-session.

Any business model where one platform onboards a user once and several partner platforms need that same verification:

• Banking-as-a-Service (BaaS), your sponsor bank or BIN sponsor needs the same Know Your Customer (KYC) data you already collected. Mint a share token from your application, the sponsor imports it.
• Multi-brand financial groups, a single user onboards into Brand A and the same group needs them in Brand B (neobank + broker, fintech + lending arm, e-money + crypto on-ramp).
• Embedded finance / Software-as-a-Service (SaaS) marketplaces, a vertical Software-as-a-Service offers payments or lending through partner banks; share the verification with whichever bank routes the user.
• Marketplaces with sub-platforms, a parent marketplace verifies sellers once and downstream regional / vertical marketplaces inherit the verification.
• On-ramps and exchanges, a fiat on-ramp shares the verified user with the exchange that lists assets; no second selfie capture.
• B2B Know Your Business (KYB) ecosystems, verify a business once (registry + UBOs + AML + documents) and share that record across every partner that onboards the same legal entity.

If you can write a data-sharing agreement with your partner, this API ships the technical half.

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.

POST /v3/session/import-shared/ returns 201 Created with a brand-new session in your application, fresh session_id and session_number, full payload cloned from the source.

Key fields:

• status, Approved / Declined / In Review (preserved when trust_review: true, forced to In Review when trust_review: false).
• session_kind, user (KYC) or business (KYB).
• shared_from_session, points at the original session in the source application. Canonical signal that this session was imported, not freshly captured.
• vendor_data, the internal user / business id YOU passed on the import call.
• KYC relations cloned: id_verifications, liveness_checks, face_matches, aml_screenings, database_validations, proof_of_address, location_checks, phone_verifications, email_verifications.
• KYB relations cloned: registry_checks, key_people_checks (with their nested KYCs), document_verifications, aml_screenings, questionnaires.

Identical shape to a fresh session, your existing webhook handler reads it the same way.

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.