Thibitisha kampuni yoyote kikamilifu: vuta rejista, onyesha kila UBO (mmiliki halisi wa mwisho), chunguza huluki na kila UBO dhidi ya vikwazo, na fanya ukaguzi wa KYC (know your customer) kwa kila mmoja. $2.00 kwa kila biashara, mamlaka 220+.
Robinhood Ventures
Inaaminika na mashirika 2,000+ duniani kote.
KYB iliyofungwa
Simu moja inasuluhisha kampuni, inatoa wamiliki na maafisa, inachunguza kila mmoja dhidi ya orodha 1,300+ za vikwazo, na inafanya ukaguzi wa KYC unaoweza kutumika tena kwa kila UBO, bila gharama ya ziada.
Chagua ukaguzi unaotaka, kitambulisho, liveness, kulinganisha uso, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko kwenye dashibodi, au tuma mtiririko huo huo kwenye API yetu. Panga masharti, fanya majaribio ya A/B, hakuna code inayohitajika.
Pachika asili na SDK yetu ya Web, iOS, Android, React Native, au Flutter. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu mtumiaji wako kiungo, kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa stack yako.
Didit inasimamia kamera, ishara za mwanga, uhamishaji wa simu, na ufikiaji. Wakati mtumiaji yuko kwenye mtiririko, tunapima ishara 200+ za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya kuaminika. Matokeo chini ya sekunde mbili.
Webhooks zilizosainiwa kwa wakati halisi huweka database yako sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Uliza API inapohitajika. Au fungua console kukagua kila kipindi, kila ishara, na kudhibiti kesi kwa njia yako.
$ curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"workflow_id": "wf_kyb_es",
"vendor_data": "biz-acme-001"
}'{ "session_id": "bs_01H...", "url": "verify.didit.me/..." }$ curl https://verification.didit.me/v3/session/bs_01H.../decision/ \
-H "x-api-key: $DIDIT_API_KEY"{ "status": "APPROVED", "session_kind": "biashara" }# Didit Business Verification (KYB) — integrate in 5 minutes
You are integrating Didit's Business Verification (Know Your Business / KYB)
module into <my_stack>. Follow these steps exactly. Every URL, header, and
workflow-type value below is canonical — do not paraphrase or "improve" them.
## 1. Provision an account
- Sign up: https://business.didit.me (no credit card required).
- Or provision programmatically: POST https://apx.didit.me/auth/v2/programmatic/register/
(returns an API key bound to the workspace + application).
## 2. Create a KYB workflow
In the Business Console: Workflows -> Create workflow -> select
"Business Verification" as the workflow type. Enable the features you need:
- Company registry lookup (required)
- Company Anti-Money Laundering (AML) (recommended)
- Key People (required for most regulated industries)
- Documents (optional - configure which document types)
Save and copy the workflow_id. KYB workflows automatically create
business sessions - there is no extra "business" flag to set on the
session create call.
## 3. Create a business session via the API
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your-api-key> (lowercase, hyphenated)
Content-Type: application/json
Body:
{
"workflow_id": "<your-kyb-workflow-id>",
"vendor_data": "biz-acme-001"
}
Response:
- session_id (e.g. bs_01H...)
- session_number (sequential)
- url (hosted verification link)
Deliver the url to the business administrator via your own channel.
They open it, confirm registry data, add Ultimate Beneficial Owners
(UBOs) and officers, upload documents, and submit.
## 4. Webhooks
Register a webhook destination once via
POST https://verification.didit.me/v3/webhook/destinations/
with subscribed_events:
status.updated, data.updated,
business.status.updated, business.data.updated
Every delivery carries an X-Signature-V2 header you MUST verify before
trusting the payload. HMAC-SHA256 verification MUST run against the raw body bytes (the raw payload as Didit sent it) BEFORE any JSON parsing — re-serialising the parsed body changes whitespace and key order, which invalidates the signature.Algorithm:
1. sortKeys(payload) recursively
2. shortenFloats (truncate trailing zeros after the decimal point)
3. JSON.stringify the result
4. HMAC-SHA256 with the secret_shared_key
5. Hex-encode, compare to the X-Signature-V2 header.
Business-session events carry session_kind: "business" inside data and
the business_session_id. Route on session_kind to your KYB handler.
Example status.updated payload:
{
"event": "status.updated",
"application_id": "app_abc123",
"timestamp": "2026-04-18T12:30:00Z",
"data": {
"session_id": "bs_01H...",
"session_kind": "business",
"vendor_data": "biz-acme-001",
"status": "APPROVED",
"previous_status": "IN_PROGRESS"
}
}
## 5. Fetch the decision (optional - the webhook already carries it)
GET https://verification.didit.me/v3/session/{session_id}/decision/
Headers:
x-api-key: <your-api-key>
Top-level shape:
- status "APPROVED" | "DECLINED" | "IN_REVIEW" | "RESUBMITTED" | "IN_PROGRESS" | "NOT_STARTED"
- session_kind "business"
- registry_checks[] per-jurisdiction company registry payloads
- company_aml_checks[] entity AML hits (sanctions, PEP, adverse media)
- key_people_checks[] registry-disclosed + user-submitted UBOs / shareholders / directors / representatives, plus ubo_kyc_summary
- document_verifications[] uploaded documents with Optical Character Recognition (OCR) fields
- business_session_id mirrors session_id
Each key_people entry includes role tags (ubo, shareholder, director,
representative, authorized_signatory, etc.), ownership_percentage, voting
percentage, and - if Know Your Customer (KYC) is required for that role - a linked_kyc_session_id
pointing at a child User Verification session.
## 6. Hard rules - do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- KYB is workflow-typed - there is no standalone POST /v3/business-verification/.
Set the workflow type to "Business Verification" in the console; the
session created against that workflow_id is automatically a business session.
- Auth header is x-api-key (lowercase, hyphenated).
- Webhook signature header is X-Signature-V2 (NOT X-Signature).
- Session status casing: APPROVED, DECLINED, IN_REVIEW, RESUBMITTED, IN_PROGRESS, NOT_STARTED (uppercase, underscore).
- Always verify webhook signatures before trusting payload data.
## 7. Pricing reference (public)
- Business Verification core (registry + UBO + officers + Key People): $2.00 per check
- Company AML screening: $0.20 per check
- Each linked KYC session spawned for a UBO / officer: $0.33 per KYC bundle
- KYB document collection (per-document OCR + tamper check): $0.20 per document
- 500 free verifications every month, forever, on every account.
## 8. Verify your integration
- Sandbox starts on signup at https://business.didit.me - no separate flag.
- Test companies (mocked registry responses) available in sandbox mode.
- Switch to live: flip the application's environment toggle in console.
When in doubt: https://docs.didit.me/business-verification/overview
$0 / mwezi. Hakuna kadi ya mkopo inayohitajika.
Lipa tu kwa unachotumia. Moduli 25+. Bei za umma kwa kila moduli, hakuna ada ya chini ya kila mwezi.
MSA & SLA maalum. Kwa idadi kubwa na programu zilizodhibitiwa.
Anza bure → lipa tu wakati ukaguzi unafanyika → fungua Enterprise kwa mkataba maalum, SLA, au uhifadhi wa data.
Didit ni miundombinu ya utambulisho na udanganyifu, jukwaa ambalo tulitamani lingekuwepo tulipokuwa tukijenga bidhaa sisi wenyewe: wazi, rahisi, na rafiki kwa waendelezaji, ili lifanye kazi kama sehemu halisi ya stack yako badala ya sanduku jeusi unalounganisha kuzunguka.
API moja inashughulikia kuthibitisha watu (KYC, know your customer), kuthibitisha biashara (KYB, know your business), kuchunguza pochi za crypto (KYT, know your transaction), na kufuatilia miamala kwa wakati halisi, kwenye stack iliyojengwa kuwa:
Alama ya chini: aina 14,000+ za hati katika lugha 48+, vyanzo vya data 1,000+, na ishara za udanganyifu 200+ kwenye kila kipindi. Miundombinu ya Didit hujifunza kwa nguvu kutoka kila kipindi na inaboresha kila siku.
US_CA, US_NY, US_DE kwenye sehemu ya country_code), na maeneo makuu ya Amerika Kusini yanaangukia kwenye kiwango cha Full (kampuni, maafisa, wanahisa, UBOs, nyaraka, fedha). Nchi zingine huangukia kwenye viwango vya Standard, Partial, au Manual kulingana na kile rejista inafichua. Matrix kamili ya nchi inapatikana kwenye docs.didit.me/business-verification/supported-countries.GET /v3/session/[id]/decision/. status ya kiwango cha juu ni mojawapo ya APPROVED, DECLINED, IN_REVIEW, RESUBMITTED, IN_PROGRESS, au NOT_STARTED. session_kind ni business. Kitu hicho kinajumuisha registry_checks[] (jina la kisheria, namba ya usajili, aina, tarehe ya kuanzishwa, hali, anwani iliyosajiliwa, namba ya kodi, pamoja na payload isiyobadilika ya registry_data na user_provided_data iliyounganishwa), key_people_checks[] (UBOs, wanahisa, wakurugenzi, wawakilishi, imegawanywa katika registry na submitted buckets, na ubo_kyc_summary ikijumuisha maendeleo ya KYC yaliyounganishwa), company_aml_checks[], na document_verifications[]. Marejeleo kamili yanapatikana kwenye docs.didit.me/business-verification/response-schema.Mtiririko kamili kwa kawaida huchukua chini ya sekunde 30 kuanzia mwanzo hadi mwisho, chukua kitambulisho, piga picha hati, piga selfie, umemaliza. Hiyo ndiyo kasi zaidi sokoni. Watoa huduma wa zamani wa KYC kwa kawaida huchukua zaidi ya sekunde 90 kwa mtiririko huo huo.
Kwa upande wa nyuma, Didit inarudisha matokeo katika chini ya sekunde mbili kwa p99, ikipimwa kuanzia wakati mtumiaji anamaliza selfie hadi wakati webhook yako inawaka. Upigaji picha wa simu umeboreshwa kwa simu za polepole na mitandao ya polepole: ukandamizaji wa picha unaoendelea, upakiaji wa polepole wa SDK, na uhamishaji wa kugusa mara moja kutoka kompyuta hadi simu kupitia msimbo wa QR ikiwa mtumiaji anaanza kwenye wavuti.
ubo_kyc_summary ya mzazi na hurithi mtiririko wa kazi uliouwekea. Hali ya kipengele cha Watu Muhimu inabaki Awaiting User hadi kila mtoto anayehitajika atatue; kisha inajumuisha kuwa Approved, Declined, au In Review. UBOs za kampuni huunda kipindi kidogo cha KYB wakati KYB iliyowekwa ndani imewezeshwa. Mratibu mmoja. Njia moja ya ukaguzi. Hakuna mtiririko sambamba wa mikono.Kila kipindi huangukia kwenye mojawapo ya hali saba zilizo wazi, kwa hivyo msimbo wako unajua nini cha kufanya:
Approved, kila ukaguzi umefaulu. Endeleza mtumiaji.Declined, ukaguzi mmoja au zaidi umeshindwa. Unaweza kumruhusu mtumiaji kuwasilisha tena hatua maalum iliyoshindwa (kwa mfano, piga tena selfie) bila kuendesha tena mtiririko mzima.In Review, imewekwa alama kwa ukaguzi wa kufuata. Fungua kesi kwenye koni, angalia kila ishara, amua kuidhinisha au kukataa.In Progress, mtumiaji yuko katikati ya mtiririko.Not Started, kiungo kimetumwa, mtumiaji bado hajafungua. Tuma ukumbusho ikiwa inakaa muda mrefu sana.Abandoned, mtumiaji alifungua kiungo lakini hakumaliza kwa wakati. Rudisha au muda wake uishe.Expired, kiungo cha kipindi kimepitwa na wakati. Unda kipindi kipya.Webhook iliyosainiwa inawaka kwenye kila mabadiliko ya hali, kwa hivyo hifadhidata yako inabaki sawa. Vipindi vilivyoachwa na vilivyokataliwa ni bure.
Data ya uzalishaji inachakatwa na kuhifadhiwa katika Umoja wa Ulaya kwa chaguo-msingi, kwenye Amazon Web Services. Mikataba ya biashara inaweza kuomba maeneo mbadala kwa maeneo ambayo wadhibiti wao wanahitaji.
Usimbaji fiche kila mahali. AES-256 wakati wa kupumzika kwenye kila hifadhidata, hifadhi ya vitu, na chelezo. Usalama wa Tabaka la Usafirishaji 1.3 wakati wa usafirishaji kwenye kila simu ya API, webhook, na kipindi cha Business Console. Data ya kibayometriki imesimbwa kwa ufunguo tofauti wa Mteja Mkuu.
Uhifadhi ni wako kudhibiti. Uhifadhi chaguomsingi ni usio na kikomo (unlimited) isipokuwa ukisanidi mfupi, kati ya siku 30 na miaka 10 kwa kila programu, na unaweza kufuta kipindi chochote cha kibinafsi wakati wowote kutoka kwenye dashibodi au API.
Vyeti: SOC 2 Type 1 (ukaguzi wa Type 2 unaendelea), ISO/IEC 27001:2022, iBeta Level 1 PAD, na uthibitisho wa umma kutoka Tesoro / SEPBLAC / CNMV ya Uhispania kwamba uhakiki wa utambulisho wa mbali wa Didit ni salama zaidi kuliko kumthibitisha mtu ana kwa ana. Ripoti kamili inapatikana kwenye /security-compliance.
Didit inatii sheria kwa chaguo-msingi kwa wadhibiti muhimu kwa miundombinu ya utambulisho:
Memo ya kina, kila cheti, kila barua ya mdhibiti: /security-compliance.
Njia tatu za ujumuishaji, chagua inayofaa stack yako:
Dashibodi sawa, bili sawa, bei sawa ya kulipa kwa mafanikio kwa zote tatu. Mwongozo wa hatua kwa hatua unapatikana kwenye docs.didit.me/integration/integration-prompt.
API moja kwa KYC, KYB, Ufuatiliaji wa Miamala, na Uchunguzi wa Wallet. Unganisha ndani ya dakika 5.