कंपनी को जानें। जानें कि उसका मालिक कौन है। लिस्टिंग लाइव होने से पहले।
EU डिजिटल सेवा अधिनियम और नया AML पैकेज विक्रेता सत्यापन को एक कानूनी दायित्व बनाते हैं। Didit इसे एक ही वर्कफ़्लो के रूप में शिप करता है: रजिस्ट्री लुकअप, मालिक एक्सट्रैक्शन, हर मालिक पर KYC, और दस्तावेज़ OCR, सभी एक ही विक्रेता रिकॉर्ड से जुड़े हुए हैं। प्रति विक्रेता $2.00, प्रति मालिक $0.33। हर महीने 500 सत्यापन मुफ्त।
यह कैसे काम करता है
साइन-अप से लेकर सत्यापित उपयोगकर्ता तक, चार चरणों में।
चरण 01
वर्कफ़्लो बनाएँ
आप जो चेक चाहते हैं उन्हें चुनें, ID, लाइवनेस, फेस मैच, प्रतिबंध, पता, आयु, फ़ोन, ईमेल, कस्टम प्रश्न। उन्हें डैशबोर्ड में एक फ़्लो में ड्रैग करें, या उसी फ़्लो को हमारे API पर पोस्ट करें। शर्तों पर ब्रांच करें, A/B टेस्ट चलाएँ, किसी कोड की आवश्यकता नहीं है।
चरण 02
इंटीग्रेट करें
हमारे वेब, iOS, Android, React Native, या Flutter SDK के साथ मूल रूप से एम्बेड करें। एक होस्ट किए गए पेज पर रीडायरेक्ट करें। या बस अपने उपयोगकर्ता को एक लिंक भेजें, ईमेल, SMS, WhatsApp, कहीं भी। चुनें कि आपके स्टैक के लिए क्या उपयुक्त है।
चरण 03
उपयोगकर्ता फ़्लो से गुज़रता है
Didit कैमरा, लाइटिंग क्यू, मोबाइल हैंड-ऑफ और एक्सेसिबिलिटी को होस्ट करता है। जब उपयोगकर्ता फ़्लो में होता है, तो हम वास्तविक समय में 200+ धोखाधड़ी संकेतों को स्कोर करते हैं और आधिकारिक डेटा स्रोतों के विरुद्ध हर फ़ील्ड को सत्यापित करते हैं। दो सेकंड से भी कम समय में परिणाम।
चरण 04
आपको परिणाम मिलते हैं
रियल-टाइम हस्ताक्षरित वेबहुक आपके डेटाबेस को उस क्षण सिंक में रखते हैं जब कोई उपयोगकर्ता स्वीकृत, अस्वीकृत होता है, या समीक्षा के लिए भेजा जाता है। मांग पर API को पोल करें। या हर सत्र, हर सिग्नल का निरीक्षण करने और अपने तरीके से मामलों को प्रबंधित करने के लिए कंसोल खोलें।
मार्केटप्लेस के लिए निर्मित · इंफ्रास्ट्रक्चर की तरह मूल्यवान
एक वर्कफ़्लो। प्रति विक्रेता $2.00।
एक विनियमित मार्केटप्लेस विक्रेता सत्यापन एक एकल चेक नहीं है, यह रजिस्ट्री लुकअप, मालिक एक्सट्रैक्शन, प्रति मालिक KYC, AML स्क्रीनिंग, दस्तावेज़ OCR, और निरंतर निगरानी का एक संयोजन है। प्रत्येक वर्कफ़्लो के अनुसार प्रत्येक मॉड्यूल को टॉगल करें।
देश के आधिकारिक स्रोत से सीधे प्राप्त किया गया, कंपनीज़ हाउस (यूके), मर्केंटिल (ईएस), हैंडल्सरजिस्टर (डीई), जुंटा कमर्शियल (बीआर), और 200+ अन्य रजिस्ट्रियां। कानूनी नाम, पंजीकरण संख्या, स्थिति, निगमन तिथि। कोई स्क्रैपिंग नहीं, कोई पुराना डेटा नहीं।
Government registries direct, no scraping.$2.00 per KYB
02 · लाभकारी मालिक एक्सट्रैक्शन
25% से अधिक का हर मालिक।
अंतिम लाभकारी मालिक (UBO) एक्सट्रैक्शन हर उस व्यक्ति को सामने लाता है जिसके पास विक्रेता का एक चौथाई या उससे अधिक हिस्सा है, जो क्लोज्ड-लूप KYC के लिए तैयार है। रजिस्ट्री स्रोत से निदेशकों और शेयरधारकों को खींचता है ताकि सूची सिद्ध हो सके, न कि स्व-प्रमाणित।
Each UBO gets a linked /v3/session/ for KYC at $0.33.
03 · प्रति मालिक KYC
हर मालिक पर क्लोज्ड-लूप आइडेंटिटी।
प्रत्येक लाभकारी मालिक को एक होस्टेड KYC सत्र मिलता है, ID सत्यापन, पैसिव लाइवनेस, फेस मैच 1:1, डिवाइस + IP विश्लेषण, AML, प्रति मालिक $0.33 पर। परिणाम मूल KYB रिकॉर्ड में वापस जुड़ जाता है ताकि एक ही अनुमोदन पूरे विक्रेता को उठा सके।
प्रतिबंध, राजनीतिक रूप से उजागर व्यक्ति (PEP), और प्रतिकूल-मीडिया सूचियाँ, दैनिक रूप से ताज़ा की जाती हैं, 14 भाषाओं में। हिट स्वचालित रूप से एक मामला खोलते हैं और मंजूरी से पहले विक्रेता को रोकते हैं। कंपनी और हर मालिक को कवर करता है।
14 languages · daily delta refresh$0.20 / individual
05 · दस्तावेज़ संग्रह + OCR
एक एविडेंस पैक, हस्ताक्षरित।
निगमन का प्रमाण पत्र, कर पंजीकरण, व्यावसायिक पते का प्रमाण, होस्टेड फ़्लो के माध्यम से एकत्र किया गया और OCR के साथ पढ़ा गया। रजिस्ट्री रिकॉर्ड के विरुद्ध क्रॉस-चेक किया गया ताकि एक छेड़छाड़ किया गया अपलोड आपके ऑडिट लॉग में आने से पहले विफल हो जाए।
Certificate of incorporationAuto-OCR · registry match
Tax / VAT registrationNumber validated against authority
Proof of business addressUtility, bank, registry letter
Bank statement (last 90d)Optional · owner verification
One evidence pack, signed and timestamped.
06 · निरंतर निगरानी
ऑनबोर्डिंग के बाद भी वेरिफाइड रहें।
विक्रेता और हर मालिक पर दैनिक चल रहा AML ($0.07/उपयोगकर्ता/वर्ष), विघटन के लिए रजिस्ट्री-स्थिति निगरानी, जब कोई मालिक 25% सीमा से ऊपर बदलता है तो अलर्ट, दस्तावेज़-समाप्ति अनुस्मारक। विक्रेता तब तक अनुपालन में रहता है जब तक वे बेचते हैं।
प्रत्येक मालिक का kyc_session_url पैरेंट KYB से जुड़ा होता है।डॉक्स →
एजेंट-रेडी इंटीग्रेशन
एक ही प्रॉम्प्ट में मार्केटप्लेस सेलर KYB शिप करें।
इसे Claude Code, Cursor, Codex, Devin, Aider, या Replit Agent में पेस्ट करें। अपना स्टैक भरें। एजेंट वर्कफ़्लो बनाएगा, प्रति विक्रेता सेशन शुरू करेगा, प्रति मालिक लिंक्ड KYC चलाएगा, और वेबहुक को वायर करेगा।
didit-integration-prompt.md
You are integrating Didit into a marketplace that lists third-party sellers (Etsy, Shopify, Faire, Amazon Handmade, OnBuy archetype). EU Digital Services Act Article 30 and the new EU Anti-Money Laundering (AML) package require you to verify the seller (KYB) before any listing goes live, and to keep that verification fresh while they sell.
Four obligations on every seller:
1. Pull the company's registry record (legal name, registration number, status, incorporation date) from the authoritative government source.
2. Extract every Ultimate Beneficial Owner (UBO) — anyone owning 25% or more — and run a closed-loop KYC on each one.
3. Screen the company AND every UBO against sanctions, Politically Exposed Persons (PEP), and adverse-media lists.
4. Collect the corporate evidence (certificate of incorporation, tax registration, proof of business address) and watch the seller continuously for status changes, UBO turnover, AML hits, and document expiry.
Pricing (verified live):
- KYB session (registry + company AML + documents + key-people flow): $2.00 per seller, pay-per-call
- Linked KYC per UBO: $0.33 per UBO (ID + Passive Liveness + Face Match + IP + AML)
- Ongoing AML monitoring: $0.07 per user per year
- First 500 KYC verifications free every month, forever
PRE-REQUISITES
- Production API key from https://business.didit.me (sandbox key in 60s, no card).
- Webhook endpoint with HMAC SHA-256 verification using the X-Signature-V2 header and your webhook secret.
- A workflow_id for KYB from the Workflow Builder. The workflow's type (KYC or KYB) drives the session shape — no explicit business flag is needed on the request.
- A workflow_id for KYC bundled with ID + Passive Liveness + Face Match + IP + AML, used for the linked UBO sessions.
STEP 1 — Create the KYB session
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<your KYB workflow id>",
"vendor_data": "<your seller id, max 256 chars>",
"callback_url": "https://<your-app>/sellers/kyb/callback",
"expected_country": "GB",
"metadata": {
"seller_id": "<your internal seller id>",
"marketplace_segment": "handmade"
}
}
Response: 201 Created with the hosted session URL. Email it to the seller or embed it in your onboarding UI. Behind the scenes, Didit runs:
- kyb_registry — live registry lookup against the country's authoritative source
- kyb_company_aml — sanctions / PEP / adverse media on the company
- kyb_documents — document collection + Optical Character Recognition (OCR) (incorporation, TIN, proof of address)
- kyb_key_people — UBO + director extraction with linked-KYC sessions
STEP 2 — Read the signed webhook on KYB completion
Didit POSTs to your callback. KYB SESSION statuses are UPPER_SNAKE_CASE:
Body (excerpted):
{
"session_id": "<uuid>",
"session_kind": "business",
"vendor_data": "<your seller id>",
"status": "APPROVED",
"decision": {
"company": {
"legal_name": "Maker Goods Ltd.",
"registration_number": "1029847",
"country_code": "GB",
"registry_status": "ACTIVE"
},
"features": [
{ "node_id": "kyb_registry", "status": "APPROVED" },
{ "node_id": "kyb_company_aml", "status": "APPROVED", "total_hits": 0 },
{ "node_id": "kyb_documents", "status": "APPROVED" },
{ "node_id": "kyb_key_people", "status": "APPROVED",
"key_people": [
{ "uuid": "<uuid>", "name": "Sara Ortega", "role": "director", "is_ubo": true, "ownership_percentage": 60, "kyc_status": "Approved", "kyc_session_url": "https://verify.didit.me/..." },
{ "uuid": "<uuid>", "name": "Niels Janssen", "role": "shareholder", "is_ubo": true, "ownership_percentage": 30, "kyc_status": "Approved", "kyc_session_url": "https://verify.didit.me/..." }
]
}
]
}
}
SESSION status enum (KYB · UPPER_SNAKE_CASE):
NOT_STARTED | IN_PROGRESS | AWAITING_USER | APPROVED | DECLINED | IN_REVIEW | RESUBMITTED | ABANDONED | EXPIRED
FEATURE status enum (inside decision.features[].status · UPPER_SNAKE_CASE):
NOT_FINISHED | APPROVED | DECLINED | IN_REVIEW | RESUB_REQUESTED | AWAITING_USER
Note: kyc_status on key_people IS Title Case ("Approved" / "Declined" / "Pending") — those are KYC sessions linked from inside the KYB feature, not KYB features themselves.
Verify the X-Signature-V2 header BEFORE reading the body — HMAC SHA-256 of the raw bytes with your webhook secret.
STEP 3 — Linked KYC on each UBO is automatic
When the seller completes the hosted KYB flow and submits the UBO list, Didit spawns a child KYC session per UBO using the KYC workflow you configured on the KYB workflow. Each child session has its own session_id and its own hosted URL on the kyc_session_url field inside the key-people block.
You don't need to call POST /v3/session/ again for the UBOs — they're stitched to the parent KYB session automatically. You DO need to drive each UBO through their hosted KYC URL (email it, SMS it, embed it in your seller dashboard).
Per-UBO KYC session status is Title Case With Spaces (KYC convention):
Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned
Linked-KYC pricing: $0.33 per UBO.
STEP 4 — Retrieve the decision
GET https://verification.didit.me/v3/session/{sessionId}/decision/
Headers:
x-api-key: <your api key>
Returns the full KYB decision payload — company block, AML hits, document OCR, every UBO with their kyc_status and kyc_session_url. Use this for audit-pack export and for re-rendering the seller status in your admin UI.
STEP 5 — Decide
Branch logic:
APPROVED → activate the seller, allow listings.
IN_REVIEW → keep listings off, wait for analyst webhook update.
DECLINED → refuse onboarding, log the decision_reason_code.
AWAITING_USER → nudge the seller to complete the pending step (typically UBO list submission).
Pre-DSA Article 30: store the trader information (legal name, registration number, address, contact) in your trader-information record alongside the decision payload.
STEP 6 — Ongoing monitoring is automatic when enabled
Enable Ongoing AML on the seller and on each UBO ($0.07/user/year). The session status updates automatically as new sanctions hits land, dissolutions are filed in the registry, or document expirations approach. Your webhook fires on every state change.
No separate endpoint to call — the same workflow drives it.
WEBHOOK EVENT NAMES
- status.updated — session status changed (filter on data.session_kind === "business" for KYB).
- data.updated — session data changed (registry refresh, key-people submission, document upload, ongoing AML hit).
- business.status.updated — the linked Business entity changed.
- business.data.updated — Business entity data changed.
Verify X-Signature-V2 on every payload. The webhook secret is per-environment — sandbox key is separate from production.
CONSTRAINTS
- KYB session statuses use UPPER_SNAKE_CASE (APPROVED, IN_REVIEW, DECLINED). KYC session statuses use Title Case (Approved, In Review, Declined). They live in different APIs — don't mix them in the same code path.
- Default record retention is 5 years post-relationship per the EU AML package; some jurisdictions go higher.
- You cannot replace the registry lookup with a self-attested form — DSA Article 30 requires the data to come from an authoritative source.
Read the docs:
- https://docs.didit.me/business-verification/integration-guide
- https://docs.didit.me/business-verification/statuses
- https://docs.didit.me/business-verification/webhooks
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/sessions-api/retrieve-session
- https://docs.didit.me/integration/webhooks
Start free at https://business.didit.me — sandbox key in 60 seconds, 500 KYC verifications free every month, no credit card.
एक क्लिक में एक नया देश खोलें। हम मुश्किल काम करते हैं।
हम स्थानीय सहायक कंपनियाँ खोलते हैं, लाइसेंस सुरक्षित करते हैं, पेनेट्रेशन टेस्ट चलाते हैं, सर्टिफिकेशन हासिल करते हैं, और हर नए रेगुलेशन के साथ अलाइन करते हैं। एक नए देश में वेरिफिकेशन शिप करने के लिए, बस एक टॉगल फ्लिप करें। 220+ देश लाइव, हर तिमाही ऑडिट और पेन-टेस्टेड, एकमात्र आइडेंटिटी प्रोवाइडर जिसे EU सदस्य-राज्य सरकार ने औपचारिक रूप से इन-पर्सन वेरिफिकेशन से ज़्यादा सुरक्षित बताया है।
प्रति KYB सेशन, रजिस्ट्री, AML, दस्तावेज़, प्रमुख-लोगों का फ़्लो।
$0.00
25% से अधिक के प्रत्येक लाभकारी मालिक पर प्रति लिंक्ड KYC।
0+
लाइव सरकारी रजिस्ट्री कवरेज वाले देश।
0
हर महीने, हर अकाउंट पर मुफ़्त KYC वेरिफिकेशन।
तीन टियर, एक मूल्य सूची
मुफ़्त में शुरू करें। उपयोग के अनुसार भुगतान करें। एंटरप्राइज़ तक स्केल करें।
हर महीने 500 मुफ़्त वेरिफिकेशन, हमेशा के लिए। प्रोडक्शन के लिए पे-एज़-यू-गो। एंटरप्राइज़ पर कस्टम कॉन्ट्रैक्ट, डेटा रेज़िडेंसी, और SLA (सर्विस लेवल एग्रीमेंट)।
मुफ़्त
मुफ़्त
$0 / महीना। क्रेडिट कार्ड की ज़रूरत नहीं।
मुफ़्त KYC बंडल (ID वेरिफिकेशन + पैसिव लाइवनेस + फेस मैच + डिवाइस और IP एनालिसिस), 500 / महीना, हर महीने
मुफ़्त में शुरू करें → केवल चेक चलने पर भुगतान करें → कस्टम कॉन्ट्रैक्ट, SLA, या डेटा रेज़िडेंसी के लिए एंटरप्राइज़ अनलॉक करें।
FAQ
अक्सर पूछे जाने वाले प्रश्न
What is 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.
What does KYB actually mean for a marketplace?
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.
Who actually has to do this?
Any marketplace that lets a third party offer goods or services to consumers and takes payment for it. That covers:
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.
How fast is the verification for my end user?
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.
What goes wrong if I skip KYB?
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.
What happens if a user fails, abandons, or expires?
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.
Where does my customer data live and how is it protected?
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.
Is Didit compliant for my industry?
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.
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.
What does ongoing monitoring look like?
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.
How does Didit compare on price?
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.