한 번의 호출로 모든 판매자를 확인하세요. 등록, 소유주, AML을 한 번에.

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.

Know Your Business (KYB) is the process of verifying that a company is real, that it's still trading, and that you know who actually owns and controls it. For a marketplace it has three pieces:

• Verify the company, name, registration number, status, and incorporation date pulled from the country's official registry
• Find the beneficial owners, every person owning 25% or more of the company
• Run KYC on each owner, same identity check you'd run on a consumer signup, just multiplied by the number of owners

It's the business-side equivalent of KYC (Know Your Customer). On a marketplace that lists third-party sellers, you owe it before any listing goes live. Didit ships the whole recipe as one workflow for $2.00 per seller + $0.33 per owner.

Any marketplace that lets a third party offer goods or services to consumers and takes payment for it. That covers:

• Goods marketplaces, Etsy, Shopify, Faire, Amazon Handmade, OnBuy archetype
• Service marketplaces, Fiverr, Upwork, Bark, ClassPass for studios
• Travel and stays, Booking, Airbnb hosts who operate as businesses
• Food and delivery, restaurant partners on Uber Eats, DoorDash, Deliveroo
• Mobility, drivers and operators on Uber, Bolt, Cabify

In the European Union the Digital Services Act (the EU's online-platform rulebook) makes seller verification a hard requirement, with material fines for non-compliance. The UK, US, and most of Latin America have parallel obligations under their own consumer-protection and anti-money-laundering rules.

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.

Three things, in order of how often they bite a marketplace:

• Fraud sellers, fake businesses listing real goods they don't have, collecting payment, vanishing. The marketplace eats the chargebacks and the brand damage.
• Sanctioned counterparties, selling on behalf of a designated entity or person. In the EU and US this is strict liability; the marketplace owes the fines regardless of intent.
• Regulator enforcement, under the EU Digital Services Act the European Commission can fine a very-large online platform up to 6% of global turnover. National regulators have parallel enforcement under consumer-protection law.

The historical record on this is unforgiving. Almost every major marketplace has been fined for letting unverified sellers operate. KYB is the standard control.

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 enum sets, one per session kind:

• KYB session, APPROVED, IN_REVIEW, DECLINED, AWAITING_USER, plus the resubmitted / abandoned / expired states the docs cover
• Linked KYC session per owner, Approved, In Review, Declined, Resubmitted, Expired, Not Finished, Kyc Expired, Abandoned

The casing difference is deliberate, UPPER_SNAKE for the KYB session, Title Case for the KYC session. They sit in different APIs; don't mix them in the same code branch.

For a webhook handler, switch on the parent KYB status. AWAITING_USER is the most common interim state, it usually means the seller still has to submit the owner list or re-upload a document. The state transitions to IN_REVIEW or APPROVED automatically once they do.

Verification at signup is necessary but not sufficient, sellers change over time, owners move in and out, and sanctions lists update daily. Didit's ongoing monitoring catches all of it:

• Ongoing AML on the company and every owner, daily delta refresh at $0.07 per user per year
• Registry status watch, dissolutions, strike-offs, and adverse filings trigger a webhook the day they hit the source
• Ownership change detection, if a new UBO crosses the 25% threshold, the seller is automatically queued for re-KYB
• Document expiry, passport, ID card, and address proof expirations fire a 30-day-out reminder

Everything flows through the same status.updated webhook you already wired for onboarding. No new endpoint, no extra integration.

Most KYB providers price between $8 and $50 per check, often with floor commits in the thousands of dollars per month and per-country surcharges. The Middesk / Persona KYB / Onfido Business archetype.

Didit's published price is $2.00 per KYB session + $0.33 per linked KYC. No floor, no commit, no per-country surcharge, no hidden registry fees. Pay only for what runs.

That's 3–5× cheaper than the incumbent stack on the same regulatory output. The economics matter because seller verification is a per-listing cost, at scale the difference between $2 and $25 is the difference between accepting a seller and refusing them. Full pricing at /pricing.