Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Usajili wa wagonjwa wa telehealth

Utambulisho wa kuaminika, kabla ya miadi ya kwanza.

Thibitisha mgonjwa, pata idhini ya HIPAA, elekeza kwa umri, kisha uthibitishe upya kila anapojaza tena dawa. Uthibitishaji 500 bure kila mwezi, uamuzi chini ya sekunde 2.

Anza bureSoma nyaraka
Inaungwa mkono na
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

Inaaminika na mashirika 2,000+ duniani kote.

Mchoro wa telehealth wa kisanii, giza, na usioeleweka, paneli nne za kioo zinazoelea, zinazopitisha mwanga kwenye mandhari nyeusi kabisa zikipitishwa na mstari mweupe wa Didit Blue. Kila paneli ina motifu ndogo isiyoeleweka (mshale wa matibabu, stethoskopu, kadi ya kitambulisho, wimbi la mapigo ya moyo).

Kile ambacho jukwaa la telehealth linadaiwa

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

Usalama wa kliniki na udhibiti wa ubadilishaji wa dawa zote hutegemea utambulisho wa mgonjwa unaoweza kuaminika. Didit inatoa KYC ya usajili na uthibitishaji upya wa biometriska kwa kila kujaza tena kama mtiririko mfupi miwili iliyopangishwa, $0.33 kwa usajili, $0.10 kwa kila kujaza tena. Uthibitishaji 500 bure kila mwezi, SOC 2 Aina ya 1 na ISO/IEC 27001 imethibitishwa, template za biometriska pekee.

Jinsi inavyofanya kazi

Kutoka kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.

  1. Hatua 01

    Unda mtiririko wa kazi

    Chagua ukaguzi unaotaka, Kitambulisho, liveness, face match, 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 msimbo unaohitajika.

  2. Hatua 02

    Unganisha

    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.

  3. Hatua 03

    Mtumiaji anapitia mtiririko

    Didit huendesha kamera, ishara za mwanga, uhamishaji wa simu, na ufikiaji. Mtumiaji anapoendelea, tunachunguza zaidi ya ishara 200 za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vinavyoaminika. Matokeo yanapatikana chini ya sekunde mbili.

  4. Hatua 04

    Unapokea matokeo

    Webhooks zilizotiwa saini kwa wakati halisi huweka database yako ikiwa imesawazishwa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Uliza API inapohitajika. Au fungua console kukagua kila session, kila ishara, na kudhibiti kesi kwa njia yako.

Imeundwa kwa ajili ya telehealth · Bei kama miundombinu

Uwezo sita. $0.33 kwa usajili. $0.10 kwa kila ujazaji.

Usajili wa mgonjwa ni utambulisho + umri + ridhaa + (hiari) bima, kila ujazaji upya ni uthibitisho wa haraka wa kibayometriki. Washa kila moduli kulingana na mtiririko wa kazi.
Soma nyarakaPata API key
01 · Kifurushi cha KYC cha Mgonjwa

Thibitisha mgonjwa kwa simu moja.

Kitambulisho + uhai + kulinganisha uso, vimeunganishwa kwa $0.33. Imethibitishwa na iBeta Level 1 anti-spoof, uamuzi chini ya sekunde mbili. Hunasa template ya kibayometriki inayounganisha ambayo huendesha kila uthibitisho wa ujazaji wa baadaye.
Moduli ya Uthibitishaji wa Mtumiaji
02 · Uelekezaji kwa Umri

Elekeza kwa umri bila kufichua 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 inayofuata. ID-fallback wakati ukadiriaji uko mpakani.
Moduli ya Ukadiriaji wa Umri
03 · Uthibitishaji wa Bima

Soma kadi. Thibitisha mlipaji.

Node ya Hiari ya Uthibitishaji wa Database hu-OCR kadi ya bima (kitambulisho cha mwanachama, kikundi, mlipaji) na hutafuta mlipaji dhidi ya database ya walipaji ya Marekani (Aetna, BCBS, UHC, Cigna, Kaiser) au mfumo wa bima ya afya wa kitaifa wa EU. Picha ya kadi hutupwa baada ya kuchambuliwa.
Moduli ya Uthibitishaji wa Database
04 · Lango la Dawa za Kudhibitiwa

Lango thabiti la utambulisho kabla ya e-prescriptions za Schedule II.

Utoaji wa Dawa za Kudhibitiwa za US Drug Enforcement Administration (DEA) Schedule II/III/IV/V unahitaji udhibiti wa kuzuia ubadhirifu chini ya Sheria ya SUPPORT. Mtiririko wa kazi wa ujazaji wa Didit unatekeleza: kitambulisho kilichotolewa na serikali, alama ya kulinganisha uso ≥ 0.85 dhidi ya template inayounganisha, uhai uliothibitishwa na iBeta, uthibitisho mpya kwa kila ujazaji.
Moduli ya Uthibitishaji wa Kibayometriki
05 · Ridhaa + Kunasa HIPAA

Ridhaa, ulaji, HIPAA, zimenaswa ndani ya mtiririko.

Maswali Maalum ($0.10) hunasa uthibitisho wa Notisi ya HIPAA ya Mazoea ya Faragha, ridhaa ya kimatibabu ya telehealth + e-prescription, na historia ya ulaji, yote katika session moja iliyopangishwa. Imewekwa toleo na muhuri wa muda kwa rekodi ya mgonjwa.
Moduli ya Maswali Maalum
06 · Uthibitishaji Upya wa Kibayometriki

Mgonjwa yule yule kwa kila ujazaji.

Selfie ya chini ya sekunde 1 + uhai uliolinganishwa dhidi ya template inayounganisha. $0.10 kwa kila uthibitisho. Inachukua nafasi ya jina la mtumiaji + nenosiri wakati wa kuingia miadi na kudhibiti utoaji wa dawa za kudhibitiwa. Template ya kibayometriki pekee, hakuna selfie mbichi inayohifadhiwa.
Moduli ya Uthibitishaji wa Kibayometriki
Unganisha

Session mbili. Template moja. Kila ujazaji salama.

Fungua session ya usajili. Hifadhi template. Thibitisha upya kila ujazaji.
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": "patient-42"
  }'
201Imeundwatemplate ya kufunga imehifadhiwa kwenye Approved.
Idhini ya HIPAA + kliniki imenaswa katika mtiririko mmoja.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": "patient-42",
    "metadata": { "context": "controlled_substance_refill" },
    // base64 enrolment selfie, ≤ 1MB
    "portrait_image": "/9j/4AAQSkZJRgABAQE..."
  }'
201Imeundwahali Imeidhinishwa → tuma e-prescription.
Ulinganishaji wa uso chini ya sekunde 1 dhidi ya template ya kufunga.nyaraka →
Ujumuishaji tayari kwa agent

Anzisha usajili wa wagonjwa wa telehealth kwa amri moja.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent huunda workflows mbili, huanzisha session ya usajili, huhifadhi template ya kufunga, na huunganisha uthibitishaji upya wa biometric 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+ ziko hewani, zinakaguliwa na kupimwa 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 faili ya usalama na utiifu
EU financial sandbox
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
EU-aligned kwa muundo

Namba za uthibitisho

Namba za uthibitisho
  • $0.00
    Kwa kila usajili wa mgonjwa, kifurushi cha KYC + template ya kufunga.
  • $0.00
    Kwa kila ujazaji au uthibitishaji upya wa biometric wa ziara mpya.
  • <0s
    Uamuzi wa wastani wa ulinganishaji wa uso kwenye Android za kiwango cha chini.
  • 0
    Uthibitishaji wa bure kila mwezi, kwenye kila akaunti.
Ngazi tatu, orodha moja ya bei

Anza bure. Lipa kulingana na matumizi. Panua hadi Enterprise.

Uthibitishaji 500 bila malipo kila mwezi, milele. Lipa kadri unavyotumia kwa uzalishaji. Mikataba maalum, uhifadhi wa data, na SLA (Service Level Agreements) kwenye Enterprise.
Bure

Bure

$0 / mwezi. Hakuna kadi ya mkopo inayohitajika.

  • Kifurushi cha bure cha KYC (Uthibitishaji wa Kitambulisho + Passive Liveness + Face Match + Uchambuzi wa Kifaa & IP), 500 / mwezi, kila mwezi
  • Watumiaji Waliozuiwa
  • Utambuzi wa Marudio
  • Ishara 200+ za udanganyifu kwenye kila session
  • KYC inayoweza kutumika tena kwenye mtandao wa Didit
  • Jukwaa la Usimamizi wa Kesi
  • Workflow Builder
  • Nyaraka za umma, sandbox, SDKs, server ya MCP (Model Context Protocol)
  • Usaidizi wa jamii
Anza bure
Maarufu zaidi
Lipa kulingana na matumizi

Kulingana na Matumizi

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

  • KYC kamili kwa $0.33 (Kitambulisho + Biometric + IP / Kifaa)
  • Data za AML 10,000+, vikwazo, PEPs, habari hasi
  • Vyanzo vya data vya serikali 1,000+ kwa Uthibitishaji wa Database
  • 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, brand yako, miundombinu yetu
Tazama orodha kamili ya beiAnza bure
Biashara Kubwa

Biashara Kubwa

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 wanapohitajika
  • Masharti ya muuzaji na white-label
  • Vipengele vya kipekee na ushirikiano wa washirika
  • CSM aliyetajwa, ukaguzi wa usalama, usaidizi wa kufuata
Wasiliana nasi

Anza bure → lipa tu wakati ukaguzi unafanyika → fungua Enterprise kwa mkataba maalum, SLA, au uhifadhi wa data.

FAQ

Maswali ya kawaida

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.

Why does a telehealth visit need identity verification at all?

Three reasons that the in-person clinic gets for free:

  • Clinical safety, the prescriber has to know the person on camera is the person on the chart. Wrong-patient prescriptions are a top safety event in remote care.
  • Pharmacy diversion, prescription resale, especially for controlled substances, depends on identity slippage between the patient and the person collecting the script.
  • Payer fraud, insurance billing for a member who isn't the one being treated is the largest single line of healthcare fraud in the US.

The in-person clinic asks for a driver's licence at check-in. Telehealth has to replace that with a remote identity check that's at least as strong. Didit ships it as a hosted flow the patient finishes on their phone in under five minutes, at $0.33 per patient.

What's HIPAA and how does it affect identity verification?

HIPAA is the US Health Insurance Portability and Accountability Act. The Privacy Rule and the Security Rule together require that protected health information (PHI) is handled with administrative, physical, and technical safeguards.

For identity verification specifically:

  • Patient identity data is PHI the moment it's tied to a clinical record
  • The vendor that does the verification is a Business Associate and needs a Business Associate Agreement (BAA) with your platform
  • Biometric templates count as PHI under most state interpretations (Illinois BIPA, Texas CUBI, Washington Biometric Privacy Act)
  • The patient's HIPAA Notice of Privacy Practices acknowledgement has to be on record before treatment

Didit ships a BAA with every paid plan and stores biometric templates only, the raw selfie is discarded after the template is generated. SOC 2 Type 1 and ISO/IEC 27001 attestations cover the security baseline. EU patients can request EU-only storage; US-specific deployments can request a US tenant.

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.

How does Age Estimation help in healthcare?

Age routes care. A 14-year-old asking for a contraceptive consult triggers a different clinical and consent pathway than a 28-year-old. A 70-year-old asking for cognitive-decline screening triggers another. Surfacing the patient's date of birth on every downstream call leaks more than the routing decision needs.

Age Estimation returns the patient's cohort, adult, young adult, adolescent, pediatric, from the same selfie used for liveness, without exposing the date of birth. The clinical layer routes on the cohort; the audit trail keeps the date of birth in the patient record where it belongs.

$0.10 per check. Backed by an ID-fallback when the estimation is borderline. For pediatric patients, the workflow can branch to a guardian-consent flow automatically.

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.

Detailed memo, every certificate, every regulator letter: /security-compliance.

How fast can I integrate and start verifying users?
  • 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.

Can the same identity work across providers?

Yes, Reusable KYC is a free distribution layer on top of the verification stack. Once a patient is onboarded, that identity can be presented to any other Didit-integrated provider with the patient's consent, eliminating re-verification fatigue.

Where this matters in healthcare:

  • Multi-tenant pharmacy chains, one onboarding covers every pharmacy under the same parent
  • Specialty referrals, primary care passes the verified identity to the specialist without re-onboarding
  • Medicare / Medicaid networks, share verified identity across in-network providers without storing biometrics on each platform
  • Cross-platform clinical research, the patient consents to share the verified identity with a registered trial

Reusable KYC is free forever. The patient owns the consent and can revoke per-provider sharing at any time via the Didit identity wallet.

How does Didit compare on price?

Most healthcare-identity providers price between $3 and $8 per check, often with minimums in the thousands per month and per-state surcharges for HIPAA tenancy. Add $0.30-$1.00 per biometric reauth.

Didit's published price is $0.33 per onboarding KYC bundle + $0.10 per biometric reauth. No floor, no minimum, no per-state surcharge. The first 500 verifications free every month absorbs most pilot and low-volume practices entirely.

That's roughly 10× cheaper than the incumbent stack on the same regulatory output. At a 5,000-patient telehealth practice with two refills per patient per year, the saving is around $12,000 per year, and the patient experience is faster, with the same selfie working across every refill. Full pricing at /pricing.

What records do I need to keep?

Healthcare retention is one of the longest of any vertical:

  • US HIPAA, 6 years from creation or last effective date, whichever is later
  • US state retention rules, typically 7-10 years for adult records, longer for pediatric (some states require until the patient is 21+)
  • EU GDPR + national health rules, 10 years for clinical records; biometric templates only for as long as the patient is active
  • DEA controlled-substance records, 2 years minimum, often longer per state

How Didit handles it:

  • All evidence stored in the European Union by default, regulated EU data centres, no cross-border transfer for EU patients. US tenant available for US-only deployments.
  • Every payload is signed and timestamped so chain-of-custody is provable for an examiner
  • Retained indefinitely while your subscription is active, no per-record retention bill, no expiry surprises
  • Configurable per workflow if your supervisor mandates a specific duration
  • Patient deletion endpoint deletes the identity record AND the biometric template (HIPAA right to access + GDPR right to erasure)

ISO 27001, SOC 2 Type 1, and iBeta Level 1 anti-spoof certifications are all downloadable from /security-compliance. Business Associate Agreement (BAA) included with every paid plan.

Related

Moduli zinazohusiana + workflows

Miundombinu ya utambulisho na udanganyifu.

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

Anza bila malipoZungumza nasi
Uliza AI ifupishe ukurasa huu