귀사의 브랜드. 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.

It's an identity-verification product that runs under your brand, your colours, your logo, your domain, but uses someone else's verification stack under the hood. The end-user never sees the underlying vendor.

Two flavours you can ship:

• Reseller, your business is identity verification (or a vertical wrapper of it). You charge customers a per-check rate that's higher than your cost, and the margin is the business model. Common for SaaS aggregators, niche compliance plays, regional resellers in markets the big vendors don't serve well.
• Embedded, you're a SaaS / fintech / platform whose product includes KYC as one feature among many. You don't want your end-users to bounce into a Didit-branded flow mid-onboarding; you want the verification to feel like part of your product.

The Didit recipe handles both with the same Style Editor + per-workflow toggle.

Six categories, all no-code via the Business Console Style Editor:

• Colours, buttons, text, panels, backgrounds. Every colour element is a token.
• Typography, fonts that match your brand. Upload custom font files or pick from a curated list.
• Logos, square and rectangular logo uploads. Used on hosted screens, in-app SDK headers, and email confirmations.
• Layout, border radius for panels and buttons. Match your design language (sharp corners or rounded).
• Login screen, show or skip the Didit login screen at session start.
• Custom domain, host on verify.yourbrand.com instead of verify.didit.me. CNAME + TLS handled inside the Console.

The Style Editor previews live as you change tokens. Once you save, toggle Include custom style on the workflow you want branded, that's the activation gate.

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.

Yes. The same Style Editor configuration applies across all five Didit SDKs, Web (React, Vue, vanilla JS), iOS (Swift), Android (Kotlin), React Native (TurboModules), and Flutter (Dart). The SDKs are free; the white-label fee covers branding across every surface.

In practice: you set colours, type, logos, and radius once. The SDK reads the same brand config from your account, the hosted flow reads the same config, and your end-user gets a consistent branded experience whether they're in a mobile app, a webview, or a desktop browser.

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.

Yes. Swapping the brand does not change the underlying compliance posture:

• iBeta Level 1 PAD, Didit's Passive Liveness is iBeta Level 1 certified, meaning it has been independently tested against printed photos, screen replays, masks, and deepfakes
• Tesoro / SEPBLAC, Didit is the only identity provider formally attested by Spain's Tesoro (under SEPBLAC, Spain's financial-intelligence unit) as a safer-than-in-person verification mechanism, for purposes of the EU Anti-Money-Laundering package
• SOC 2 Type 1, independent audit of Didit's security controls
• ISO/IEC 27001, international security-management standard
• GDPR alignment, General Data Protection Regulation by design (data minimisation, lawful basis, DSAR support)

Under your white-label, all of these flow through to your customer. Didit provides sub-processor disclosure on request for your DPA (Data Processing Agreement).

Both are free, both work with the white-label add-on.

• Workflow Builder, drag-and-drop composer for KYC + AML + KYB + Wallet Screening modules. Per-workflow Include custom style toggle lives here. Edit rules and module selection without redeploying your app.
• Didit MCP (Model Context Protocol) server, exposes the same Didit primitives to AI coding agents (Claude Code, Cursor, Codex, Replit Agent, Devin, Aider). Useful for a small reseller team that wants to automate per-tenant workflow provisioning, branded-flow templating, or scripted onboarding tests.

The net: you don't need a large engineering team to ship a white-label KYC product. The Style Editor handles brand, the Workflow Builder handles modules, the MCP server handles automation, and the /v3/ API handles the verification itself.

Four wires, one afternoon for a vertical-slice; a week for production:

• Open business.didit.me, sandbox key in 60 seconds, no credit card
• Enable the white-label add-on (talk to sales) and open the Style Editor, configure brand, upload logos, add custom domain (CNAME at your DNS provider)
• Build the workflow in the Workflow Builder with the modules you ship (typically ID + Liveness + Face Match + AML), toggle Include custom style ON
• Wire POST /v3/session/ + the signed webhook (X-Signature-V2 HMAC SHA-256) into your onboarding flow

For a multi-tenant reseller, add: one workflow per end-customer brand, per-tenant Style Editor configuration, a routing layer that picks the right workflow_id per inbound request. The MCP server scripts these end-to-end.