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"
}'$ curl https://verification.didit.me/v3/session/bs_01H.../decision/ \
-H "x-api-key: $DIDIT_API_KEY"# 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 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:
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.
US_CA, US_NY, US_DE in the country_code field), and major Latin American jurisdictions land in the Full coverage tier (company, officers, shareholders, UBOs, documents, financials). Other countries fall into Standard, Partial, or Manual tiers depending on what the registry exposes. The full per-country matrix lives at docs.didit.me/business-verification/supported-countries.GET /v3/session/[id]/decision/. Top-level status is one of APPROVED, DECLINED, IN_REVIEW, RESUBMITTED, IN_PROGRESS, or NOT_STARTED. session_kind is business. The object includes registry_checks[] (legal name, registration number, type, incorporation date, status, registered address, tax number, plus the immutable registry_data payload and the merged user_provided_data), key_people_checks[] (UBOs, shareholders, directors, representatives, split into registry and submitted buckets, with ubo_kyc_summary rolling up the linked KYC progress), company_aml_checks[], and document_verifications[]. Full reference at docs.didit.me/business-verification/response-schema.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.
ubo_kyc_summary and inherits the workflow you mapped it to. The Key People feature status stays Awaiting User until every required child resolves; it then aggregates to Approved, Declined, or In Review. Corporate UBOs spawn a nested KYB sub-session when nested KYB is enabled. One orchestrator. One audit trail. No parallel manual flow.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:
Detailed memo, every certificate, every regulator letter: /security-compliance.
Three integration paths, pick whichever fits your stack:
Same dashboard, same billing, same pay-per-success price for all three. Step-by-step guide at docs.didit.me/integration/integration-prompt.
API moja kwa KYC, KYB, Ufuatiliaji wa Miamala, na Uchunguzi wa Wallet. Unganisha ndani ya dakika 5.