Ruka hadi maudhui makuu
Didit Yakusanya $2M na Kujiunga na Y Combinator (W26)
Didit
Usajili wa mgonjwa wa telehealth

Kitambulisho cha kuaminika — kabla ya miadi ya kwanza.

Thibitisha mgonjwa, pata idhini ya HIPAA, elekeza kwa umri, kisha uthibitishe upya kila unapojaza tena. Uthibitishaji 500 bila malipo kila mwezi, uamuzi wa chini ya sekunde 2.

Inaungwa mkono na
Y Combinator
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

Inaaminika na mashirika 2,000+ duniani kote.

Mchoro wa sinema wa giza usioeleweka wa telehealth — paneli nne za glasi zinazoelea, zinazopitisha mwanga kwenye uzi mweusi safi zilizounganishwa na mstari wa Didit Blue unaong'aa. Kila paneli hubeba motifu ndogo isiyo dhahiri (msalaba wa matibabu, stethoskopu, kadi ya kitambulisho, umbo la wimbi la mapigo ya moyo).

Kile ambacho jukwaa la telehealth linadaiwa

Mjue mgonjwa. Jua ni mtu yule yule kila anapojaza tena dawa. Bila kupunguza kasi ya ziara.

Usalama wa kimatibabu na udhibiti wa ubadilishaji wa duka la dawa zote hutegemea kitambulisho cha mgonjwa kinachoaminika. Didit husafirisha KYC ya usajili na uthibitishaji upya wa kibayometriki kwa kila ujazaji kama mtiririko miwili mifupi iliyopangishwa — $0.33 kwa usajili, $0.10 kwa kila ujazaji. Uthibitishaji 500 bila malipo kila mwezi, SOC 2 Aina ya 1 na ISO/IEC 27001 imethibitishwa, violezo vya kibayometriki pekee.

Jinsi inavyofanya kazi

Kutoka kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.

  1. Hatua 01

    Unda mtiririko wa kazi

    Chagua ukaguzi unaotaka — Kitambulisho, uhai, ulinganishaji wa uso, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko kwenye dashibodi, au chapisha mtiririko huo huo kwenye API yetu. Tawi kwenye masharti, endesha majaribio ya A/B, hakuna msimbo unaohitajika.

  2. Hatua 02

    Unganisha

    Pachika kiasili na SDK yetu ya Wavuti, iOS, Android, React Native, au Flutter. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu kiungo kwa mtumiaji wako — kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa stack yako.

  3. Hatua 03

    Mtumiaji hupitia mtiririko

    Didit huandaa kamera, vidokezo vya mwanga, uhamishaji wa simu, na ufikiaji. Wakati mtumiaji yuko kwenye mtiririko, tunapata alama za udanganyifu 200+ kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vyenye mamlaka. Matokeo yanapatikana chini ya sekunde mbili.

  4. Hatua 04

    Unapokea matokeo

    Webhooks zilizotiwa saini kwa wakati halisi huweka hifadhidata yako ikisawazishwa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Uliza API inapohitajika. Au fungua koni ili kukagua kila kipindi, kila ishara, na kudhibiti kesi kwa njia yako.

Imejengwa kwa ajili ya telehealth · Bei kama miundombinu

Uwezo sita. $0.33 kwa kuingiza. $0.10 kwa kila kujaza tena.

Usajili wa mgonjwa ni utambulisho + umri + idhini + (hiari) bima — kila kujaza upya ni uthibitisho wa haraka wa kibayometriki. Washa kila moduli kwa kila mtiririko wa kazi.
01 · Kifurushi cha KYC cha Mgonjwa

Thibitisha mgonjwa kwa simu moja.

Kitambulisho + uhai + kulinganisha uso — vimeunganishwa kwa $0.33. Imethibitishwa na iBeta Level 1 dhidi ya udanganyifu, uamuzi wa chini ya sekunde mbili. Hunasa kiolezo cha kibayometriki kinachofunga ambacho huendesha kila uthibitisho wa kujaza upya wa baadaye.
Moduli ya Uthibitishaji wa Mtumiaji
02 · Uelekezaji wa umri

Elekeza kwa umri bila kuonyesha tarehe ya kuzaliwa.

Ukadiriaji wa Umri ($0.10) hurejesha kundi la mgonjwa — mtu mzima, kijana, balehe, mtoto — ili mtiririko wako wa kazi wa kimatibabu uelekeze kwenye njia sahihi bila kuvujisha tarehe ya kuzaliwa kwa kila huduma ya chini. Kitambulisho-fallback wakati ukadiriaji uko mpakani.
Moduli ya Ukadiriaji wa Umri
03 · Uthibitishaji wa bima

Soma kadi. Thibitisha mlipaji.

Nodi ya Hiari ya Uthibitishaji wa Hifadhidata hu-OCR kadi ya bima (kitambulisho cha mwanachama, kikundi, mlipaji) na hutafuta mlipaji dhidi ya hifadhidata ya walipaji ya Marekani (Aetna, BCBS, UHC, Cigna, Kaiser) au mfumo wa bima ya afya ya kitaifa wa EU. Picha ya kadi hutupwa baada ya kuchambua.
Moduli ya Uthibitishaji wa Hifadhidata
04 · Lango la Dawa Zinazodhibitiwa

Lango thabiti la utambulisho kabla ya maagizo ya kielektroniki ya Ratiba II.

Utoaji wa Dawa Zinazodhibitiwa na Utawala wa Utekelezaji wa Dawa za Marekani (DEA) Ratiba II/III/IV/V unahitaji udhibiti wa kuzuia ubadhirifu chini ya Sheria ya SUPPORT. Mtiririko wa kazi wa kujaza upya wa Didit unatekeleza: kitambulisho kilichotolewa na serikali, alama ya kulinganisha uso ≥ 0.85 dhidi ya kiolezo kinachofunga, uhai uliothibitishwa na iBeta, uthibitisho mpya kwa kila kujaza upya.
Moduli ya Uthibitishaji wa Kibayometriki
05 · Idhini + Kunasa HIPAA

Idhini, ulaji, HIPAA — zimenaswa katika mtiririko.

Maswali Maalum ($0.10) hunasa uthibitisho wa Notisi ya HIPAA ya Mazoea ya Faragha, idhini ya kimatibabu ya telehealth + e-prescription, na historia ya ulaji — yote katika kipindi kimoja kilichopangishwa. Imewekwa toleo na muhuri wa muda kwa rekodi ya mgonjwa.
Moduli ya Maswali Maalum
06 · Uthibitishaji upya wa kibayometriki

Mgonjwa yule yule kwa kila kujaza upya.

Selfie ya chini ya sekunde 1 + uhai uliolinganishwa dhidi ya kiolezo kinachofunga. $0.10 kwa uthibitisho. Hubadilisha jina la mtumiaji + nenosiri wakati wa kuingia kwa miadi na huzuia utoaji wa dawa zinazodhibitiwa. Kiolezo cha kibayometriki pekee — hakuna selfie mbichi iliyohifadhiwa.
Moduli ya Uthibitishaji wa Kibayometriki
Unganisha

Vipindi viwili. Kiolezo kimoja. Kila kujaza upya salama.

Fungua kipindi cha usajili. Dumisha kiolezo. Thibitisha upya kwa kila kujaza upya.
POST /v3/session/Sajili
$ 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_patient_onboarding",
    "vendor_data": "mgonjwa-42"
  }'
201Imeundwakiolezo cha kufunga kimehifadhiwa kwenye Imeidhinishwa.
HIPAA + idhini ya kimatibabu imenaswa katika mtiririko uleule.nyaraka →
POST /v3/session/Thibitisha upya
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_biometric_reauth",
    "vendor_data": "mgonjwa-42",
    "metadata": { "context": "controlled_substance_refill" },
    // base64 enrolment selfie, ≤ 1MB
    "portrait_image": "/9j/4AAQSkZJRgABAQE..."
  }'
201Imeundwahali Imeidhinishwa → washa e-prescription.
Ulinganishaji wa uso chini ya sekunde 1 dhidi ya kiolezo cha kufunga.nyaraka →
Ujumuishaji tayari kwa wakala

Anzisha usajili wa mgonjwa wa telehealth kwa haraka.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Wakala huunda mtiririko miwili, huwasha kipindi cha usajili, huendeleza kiolezo cha kufunga, na huunganisha uthibitishaji upya wa kibayometriki kwa kila ujazaji + webhook.
didit-integration-prompt.md
You are integrating Didit into a telehealth platform (Doctolib / Teladoc / Hims & Hers / Ro / Tessa Health archetype). You owe the clinical and pharmacy layers a trustworthy patient identity at onboarding and at every refill of a controlled prescription.

Three obligations at onboarding:

  1. Verify the patient's identity — government ID + liveness + face match.
  2. Confirm age — adult, adolescent, or pediatric — to route to the correct clinical pathway without surfacing date of birth on every downstream call.
  3. Capture consent — HIPAA Notice of Privacy Practices acknowledgement, clinical consent (telemedicine + electronic health record + e-prescription), intake history.

One obligation at every refill or new appointment:

  4. Biometric reauthentication — a 1-second selfie matched to the binding template established at onboarding. Anti-diversion control for US Drug Enforcement Administration (DEA) Schedule II-V medications.

Optional but recommended:

  5. Insurance card capture + payer validation — OCR the card, look up the payer, ping eligibility if your stack supports 270/271 EDI.

Pricing (verified live):
  - Onboarding Know Your Customer (KYC) bundle (ID + Liveness + Face Match + IP + AML): $0.33 per patient
  - Age Estimation: $0.10 per patient
  - Custom Questionnaire (HIPAA + clinical consent): $0.10 per submission
  - Biometric Authentication (refill / new visit): $0.10 per auth
  - 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 patient onboarding that bundles ID Verification + Passive Liveness + Face Match 1:1 + Age Estimation + Custom Questionnaire.
  - A workflow_id for biometric reauthentication (selfie + liveness + 1:1 face match against the binding template).

STEP 1 — Create the patient onboarding session

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<your patient onboarding workflow id>",
      "vendor_data": "<your patient id, max 256 chars>",
      "callback_url": "https://<your-app>/patients/kyc/callback",
      "metadata": {
        "patient_id": "<your internal id>",
        "scheduling_context": "new_visit"
      }
    }

  Response: 201 Created with the hosted session URL. Send it to the patient through your booking flow; they complete identity + consent on their phone in under five minutes.

STEP 2 — Read the signed webhook on onboarding completion

  Didit POSTs to your callback. Session statuses are Title Case With Spaces:

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your patient id>",
      "status": "Approved",
      "id_verification": { "status": "Approved", "document_type": "drivers_license", "country_code": "US" },
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94 },
      "age_estimation": { "status": "Approved", "estimated_age_bucket": "ADULT" },
      "questionnaire": { "status": "Approved", "responses": { "hipaa_ack": true, "telehealth_consent": true } }
    }

  Session status enum (exact case):
    Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned

  Verify the X-Signature-V2 header BEFORE reading the body — HMAC SHA-256 of the raw bytes with your webhook secret.

STEP 3 — Persist the binding biometric template

  When the onboarding session is Approved, Didit stores a biometric template under the patient's vendor_data automatically. You don't need to fetch or store the raw selfie — it's discarded after the template is generated. The template lives in EU data centres and is used for every future face-match against this patient.

STEP 4 — Biometric reauthentication at refill / new appointment

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<your biometric reauth workflow id>",
      "vendor_data": "<the same patient id as onboarding>",
      "callback_url": "https://<your-app>/patients/reauth/callback",
      "metadata": {
        "context": "controlled_substance_refill",
        "prescription_id": "<your rx reference>"
      }
    }

  The reauth workflow runs Passive Liveness + Face Match 1:1 against the binding template. Sub-1-second median verdict. $0.10 per auth. Use this BEFORE every controlled-substance e-prescription fires.

STEP 5 — Decide

  Branch logic on the parent session status:
    Approved    → onboard the patient, allow scheduling.
    In Review   → hold the visit, wait for analyst webhook update.
    Declined    → refuse onboarding, log the decline reason.
    Resubmitted → patient updated something; re-read the decision.

  On the reauth session:
    Approved    → fire the e-prescription / book the visit.
    Declined    → refuse the refill, require in-person identity check.

STEP 6 — Insurance card capture (optional)

  Add a Database Validation node to your onboarding workflow against the US payer database (Aetna, BCBS, UnitedHealthcare, Cigna, Kaiser) or the EU national health-insurance system (ES Seguridad Social, DE GKV, FR CPAM, IT SSN). The patient uploads the card; Didit OCRs the member id, group, and payer name, then validates against the payer database. The card image is discarded after parse — only the validated payload is retained.

WEBHOOK EVENT NAMES
  - status.updated — session status changed.
  - data.updated — session data changed (resubmission, consent re-collection).

  Verify X-Signature-V2 on every payload. The webhook secret is per-environment — sandbox key is separate from production.

CONSTRAINTS
  - Session statuses use Title Case With Spaces (Approved, In Review).
  - The biometric template is the binding identity — once a patient is onboarded, every future reauth references it. If you delete the patient, delete the template too via the Business Console (GDPR / HIPAA right-to-deletion compliance).
  - HIPAA-protected information (PHI) and biometric templates are stored in EU data centres for EU patients; US-specific deployments can request a US tenant.
  - For controlled-substance dispense, run a fresh biometric reauth on every refill — this is the anti-diversion control US DEA Schedule II / III requires under the SUPPORT Act.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/sessions-api/retrieve-session
  - https://docs.didit.me/core-technology/face-match/overview
  - https://docs.didit.me/core-technology/age-estimation/overview
  - https://docs.didit.me/integration/webhooks

Start free at https://business.didit.me — sandbox key in 60 seconds, 500 verifications free every month, no credit card.
Unahitaji maelezo zaidi? Tazama nyaraka kamili za moduli.docs.didit.me →
Inatii kwa muundo

Fungua nchi mpya kwa kubofya mara moja. Tunafanya kazi ngumu.

Tunafungua kampuni tanzu za ndani, tunapata leseni, tunafanya majaribio ya kupenya, tunapata vyeti, na tunalingana na kila kanuni mpya. Ili kusafirisha uthibitishaji katika nchi mpya, geuza swichi. Nchi 220+ zinafanya kazi, zinakaguliwa na kujaribiwa kila robo mwaka — mtoa huduma pekee wa utambulisho ambaye serikali ya nchi mwanachama wa EU imemwita rasmi kuwa salama zaidi kuliko uthibitishaji wa ana kwa ana.
Soma jalada la usalama na utiifu
Sanduku la majaribio la kifedha la EU
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
Usalama wa habari · 2026
SOC 2 · Type I
AICPA · 2026
iBeta Level 1 PAD
NIST / NIAP · 2026
GDPR
EU 2016/679
DORA
EU 2022/2554
MiCA
EU 2023/1114
AMLD6 · eIDAS 2.0
Inalingana na EU kwa muundo

Nambari za uthibitisho

Nambari za uthibitisho
  • $0.00
    Usajili wa kila mgonjwa — kifurushi cha KYC + kiolezo cha kufunga.
  • $0.00
    Uthibitishaji upya wa kibayometriki kwa kila ujazaji au ziara mpya.
  • <0s
    Uamuzi wa wastani wa ulinganishaji wa uso kwenye Android ya kiwango cha chini.
  • 0
    Uthibitishaji wa bure kila mwezi, kwenye kila akaunti.
Ngazi tatu, orodha moja ya bei

Anza bure. Lipa kwa matumizi. Panua hadi Biashara.

Uthibitishaji 500 bila malipo kila mwezi, milele. Lipa kadri unavyotumia kwa uzalishaji. Mikataba maalum, makazi ya data, na SLA (Mikataba ya Kiwango cha Huduma) kwenye Biashara.
Bure

Bure

$0 / mwezi. Hakuna kadi ya mkopo inayohitajika.

  • Kifurushi cha KYC cha bure (Uthibitishaji wa Kitambulisho + Uhai Usio na Kazi + Kulinganisha Uso + Uchambuzi wa Kifaa na IP) — 500 / mwezi, kila mwezi
  • Watumiaji Waliozuiliwa
  • Kugundua Marudio
  • Ishara 200+ za udanganyifu kwenye kila kipindi
  • KYC inayoweza kutumika tena kwenye mtandao wa Didit
  • Jukwaa la Usimamizi wa Kesi
  • Mjenzi wa Mtiririko wa Kazi
  • Hati za umma, sandbox, SDKs, seva ya MCP (Model Context Protocol)
  • Usaidizi wa jamii
Maarufu zaidi
Lipa kwa matumizi

Kulingana na Matumizi

Lipa tu kwa kile unachotumia. Moduli 25+. Bei ya umma kwa kila moduli, hakuna ada ya chini ya kila mwezi.

  • KYC kamili kwa $0.33 (Kitambulisho + Biometriska + IP / Kifaa)
  • Hifadhidata 10,000+ za AML — vikwazo, PEPs, vyombo vya habari hasi
  • Vyanzo 1,000+ vya data ya serikali kwa Uthibitishaji wa Hifadhidata
  • Ufuatiliaji wa Miamala kwa $0.02 kwa kila muamala
  • KYB ya Moja kwa Moja kwa $2.00 kwa kila biashara
  • Uchunguzi wa Wallet kwa $0.15 kwa kila ukaguzi
  • Mtiririko wa uthibitishaji wa Whitelabel — chapa yako, miundombinu yetu
Biashara

Biashara

MSA & SLA maalum. Kwa idadi kubwa na programu zilizodhibitiwa.

  • Mikataba ya kila mwaka
  • MSA, DPA, na SLA maalum
  • Kituo maalum cha Slack na WhatsApp
  • Wakaguzi wa mikono kwa mahitaji
  • Masharti ya muuzaji na white-label
  • Vipengele vya kipekee na ushirikiano wa washirika
  • CSM aliyetajwa, ukaguzi wa usalama, usaidizi wa kufuata

Anza bure → lipa tu wakati ukaguzi unafanyika → fungua Biashara kwa mkataba maalum, SLA, au makazi ya data.

FAQ

Maswali ya kawaida

Miundombinu ya utambulisho na udanganyifu.

API moja kwa KYC, KYB, Ufuatiliaji wa Miamala, na Uchunguzi wa Wallet. Unganisha kwa dakika 5.

Uliza AI ifupishe ukurasa huu