Ruka hadi maudhui makuu
Didit Yakusanya $2M na Kujiunga na Y Combinator (W26)
Didit
Usajili wa e-pasipoti ya NFC

Kitambulisho cha kiwango cha benki kwa kugonga chip ya pasipoti ya kielektroniki.

Mtumiaji anagonga pasipoti kwenye simu. Saini ya serikali inathibitishwa, picha ya chip inashinda selfie. Kiwango cha benki chini ya sekunde tano. $0.15 kwa usomaji wa chip.

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

Inaaminika na mashirika 2,000+ duniani kote.

Mchoro wa sinema, giza, usioeleweka wa pasipoti ya kielektroniki ya NFC — paneli nne za glasi zinazoelea, zinazopitisha mwanga kwenye uzi mweusi safi uliounganishwa na mstari wa Didit Blue unaong'aa. Kila paneli hubeba motifu ndogo isiyoeleweka (muhtasari wa kitabu cha pasipoti, arcs za NFC, kitanzi cha alama ya vidole, mstatili wa chipu na pedi za mawasiliano).

Jukwaa lililodhibitiwa linadai nini

Soma chip. Thibitisha saini. Shinda uchanganuzi wa hati.

Data kwenye chipu ya pasipoti ya kielektroniki imetiwa saini kwa njia fiche na nchi iliyotoa. Kuthibitisha mnyororo huo wa saini — na kulinganisha picha ya kujipiga na picha ya chipu yenye ubora wa juu — kunakupa uhakika wa kiwango cha benki kwamba hati ni halisi. Mtiririko wa NFC wa Didit huendeshwa chini ya sekunde tano, hurudi kwenye OCR wakati NFC haipatikani, na huja na SDK asili za iOS, Android, React Native, na Flutter.

Jinsi inavyofanya kazi

Kutoka kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.

  1. Hatua 01

    Unda mtiririko wa kazi

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

  2. Hatua 02

    Unganisha

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

  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 ishara 200+ za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya mamlaka. Matokeo chini ya sekunde mbili.

  4. Hatua 04

    Unapokea matokeo

    Webhooks zilizotiwa saini kwa wakati halisi huweka hifadhidata yako ikiwa sawa 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.

Imeundwa kwa kiwango cha benki · Bei kama miundombinu

Ukaguzi tano. $0.50 kwa kila mtumiaji aliyeingizwa.

Usomaji wa chipu ya NFC huinua uwekaji wa wateja kutoka kiwango cha skani ya hati hadi kiwango cha benki kwa hatua moja ya ziada kwenye simu ya mtumiaji. Mtiririko wa kazi hurudi kwenye MRZ + OCR kiotomatiki wakati NFC haipatikani.
01 · Usomaji wa chipu ya NFC

Gonga pasipoti. Soma chip.

Mtumiaji husoma ukurasa wa kuona (MRZ hupata ufunguo wa chipu), hugonga hati kwenye simu, na chipu hurejesha Kundi la Data 1 (data ya kibinafsi), Kundi la Data 2 (picha yenye ubora wa juu), Kundi la Data 11 (maelezo ya kibinafsi). $0.15 kwa usomaji wa chipu. Sekunde 2-4 mwisho hadi mwisho.
Moduli ya Uthibitishaji wa NFC
02 · Mnyororo wa saini wa ICAO

Saini ya serikali, imethibitishwa.

Uthibitishaji Tulivu unathibitisha Cheti cha Kusaini Hati cha chip dhidi ya CA ya kusaini ya nchi kupitia Saraka ya Funguo za Umma ya ICAO. Uthibitishaji wa Chip na Uthibitishaji Amilifu hufanya kazi pale inapoungwa mkono. Inalingana na ICAO Doc 9303.
Moduli ya Uthibitishaji wa NFC
03 · Kulinganisha uso na picha ya chipu

Selfie imelinganishwa na picha ya chip.

Picha ya DG2 kwenye chip ina azimio la juu zaidi kuliko picha iliyochapishwa kwenye ukurasa unaoonekana — kulinganisha selfie ya moja kwa moja dhidi yake ni sahihi zaidi. Ulinganifu wa Cosine ≥ 0.85 → Imefaulu, ≥ 0.92 → kiwango cha benki. $0.05 kwa kila kulinganisha.
Moduli ya Kulinganisha Nyuso 1:1
04 · Uhai usio na shughuli

Kuzuia udanganyifu kwenye selfie.

Imethibitishwa na iBeta Level 1 Presentation Attack Detection (PAD). Inashinda picha zilizochapishwa, marudio ya skrini, barakoa za silikoni, na deepfakes — selfie moja tuli, hakuna vidokezo vya changamoto. $0.10 kwa kila ukaguzi.
Moduli ya Uhai Tulivu
05 · Uchunguzi wa AML

Chunguza utambulisho uliothibitishwa na chip.

Vikwazo, Watu Walio Wazi Kisiasa (PEP), vyombo vya habari hasi katika orodha 1,300+ — husasishwa kila siku, katika lugha 14. Hits hufungua kesi kiotomatiki na kuzuia usajili kabla ya idhini.
Moduli ya Uchunguzi wa AML
06 · Rudi kwenye MRZ + OCR

Kurejea kwa upole wakati NFC haipatikani.

Simu zisizo na NFC, hati zisizo na chip, au kukataa ruhusa ya NFC — mtiririko huo wa kazi hurudi kwenye Uthibitishaji wa Kitambulisho ($0.15) na MRZ sahihi sana + OCR kwenye ukurasa unaoonekana. URL hiyo hiyo iliyopangishwa, webhook hiyo hiyo, hali hizo hizo.
Moduli ya Uthibitishaji wa Kitambulisho
Unganisha

Kipindi kimoja. SDK asili. Kiwango cha benki kwa sekunde.

Fungua kipindi cha NFC. SDK huendesha usomaji wa chipu. Soma uamuzi uliotiwa saini.
POST /v3/session/NFC
$ 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_nfc_onboarding",
    "vendor_data": "user-42",
    "expected_country": "ES"
  }'
201Imeundwafungua URL katika SDK asili · NFC inaanza.
SDK za iOS / Android / React Native / Flutter zote zinaunga mkono NFC.nyaraka →
GET /v3/session/{id}/decision/Uamuzi
$ curl https://verification.didit.me/v3/session/$SESSION/decision/ \
  -H "x-api-key: $DIDIT_API_KEY"

# Decision payload (excerpted):
{ "nfc_verification": { "passive_authentication": "Imeidhinishwa" },
  "uso": { "imelinganishwa_dhidi_ya": "picha_ya_chip", "alama_ya_kufanana": 0.94 } }
200OKimefananishwa na picha_ya_chip → uhakikisho wa kiwango cha eIDAS.
Mtiririko wa kazi unarudi kwenye MRZ + OCR wakati NFC haipatikani.nyaraka →
Ujumuishaji tayari kwa wakala

Anzisha usajili wa e-pasipoti ya NFC kwa haraka.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Wakala huunda mtiririko wa kazi wa NFC, huunganisha SDK asili, hurudi kwenye MRZ + OCR wakati NFC haipatikani, na husoma webhook iliyosainiwa.
didit-integration-prompt.md
You are integrating Didit's NFC e-passport reading into a regulated onboarding flow (bank, fintech, crypto exchange, eIDAS-grade public service). NFC chip reading lifts onboarding from document-scan-grade to bank-grade in one extra step on the user's phone.

Five obligations on every onboarding:

  1. Read the e-passport / e-ID chip via NFC — DG1 (MRZ), DG2 (portrait), DG11 (personal details).
  2. Verify the government signature chain — Passive Authentication (PA) against the ICAO Public Key Directory, Chip Authentication (CA), Active Authentication (AA).
  3. Match the live selfie to the high-resolution DG2 portrait extracted from the chip.
  4. Run Passive Liveness on the selfie — iBeta Level 1 anti-spoof certified, defeats printed photos, screen replays, masks, and deepfakes.
  5. Screen the chip-verified identity against sanctions, Politically Exposed Persons (PEP), and adverse-media lists.

Fallback automatically when NFC is unavailable (no chip, NFC blocked by iOS or by user permission, chip damaged): the workflow drops to high-accuracy MRZ + OCR on the visual page using ID Verification.

Pricing (verified live):
  - NFC Reading: $0.15 per chip read
  - ID Verification (fallback or always-on belt-and-braces): $0.15 per check
  - Passive Liveness: $0.10 per check
  - Face Match 1:1: $0.05 per match
  - AML Screening: $0.20 per check
  - Bundle (NFC + Liveness + Face Match + AML): $0.50 per onboarded user when NFC succeeds; $0.50 also when the workflow falls back to ID Verification
  - 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 from the Workflow Builder bundling NFC Reading + ID Verification (fallback) + Passive Liveness + Face Match 1:1 + AML Screening.
  - The Didit hosted flow or the native SDKs (web SDK, iOS, Android, React Native, Flutter) — NFC chip reading requires the native NFC stack, so plain web-only deployments fall back to MRZ + OCR automatically.

STEP 1 — Create the NFC session

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<your nfc onboarding workflow id>",
      "vendor_data": "<your user id, max 256 chars>",
      "callback_url": "https://<your-app>/onboarding/kyc/callback",
      "expected_country": "ES",
      "metadata": {
        "channel": "native_ios",
        "purpose": "high_assurance_onboarding"
      }
    }

  Response: 201 Created with the hosted session URL. Open it via the native SDK (iOS NFC requires CoreNFC entitlement) or in the hosted webview; the user taps the e-passport against the phone's NFC reader, the chip data is read in 2-4 seconds.

STEP 2 — The chip-read sequence (handled by the SDK / hosted flow)

  Inside the hosted flow, in this order:
    a. The user presents the data page so the device camera reads the Machine-Readable Zone (MRZ). The MRZ provides the BAC / PACE key needed to handshake with the chip.
    b. The user taps the passport to the phone. PACE (preferred) or BAC handshake establishes a secure session with the chip.
    c. The chip returns Data Group 1 (MRZ data — name, DOB, expiry, document number), Data Group 2 (the high-resolution portrait), and Data Group 11 (personal details where available).
    d. Passive Authentication verifies the Document Signer Certificate against the country's Country Signing CA via the ICAO Public Key Directory. Chip Authentication and Active Authentication run if supported by the issuing country.
    e. The user takes a single selfie (Passive Liveness, no challenge prompts).
    f. The selfie is matched 1:1 against the DG2 portrait.

STEP 3 — Read the signed webhook on completion

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

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your user id>",
      "status": "Approved",
      "nfc_verification": {
        "status": "Approved",
        "passive_authentication": "Approved",
        "chip_authentication": "Approved",
        "active_authentication": "Approved",
        "data_groups_read": [1, 2, 11]
      },
      "id_verification": { "status": "Approved", "document_type": "passport", "country_code": "ES" },
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94, "matched_against": "chip_portrait" },
      "aml": { "status": "Approved", "hits": [] }
    }

  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 4 — Decide

  Branch logic:
    Approved    → onboard the user with bank-grade assurance.
    In Review   → hold the account, wait for analyst webhook update.
    Declined    → refuse onboarding, log the decline reason.
    Resubmitted → user updated something; re-read the decision.

  When face.matched_against === "chip_portrait", you can mark the identity as eIDAS High-grade (Substantial / High depending on your local regulator's reading). When it falls back to "id_document_portrait" (the visual page), it's still bank-grade by document-scan standards but not chip-anchored.

STEP 5 — Fallback paths

  iPhones below iPhone 7, or any phone with NFC disabled, or a document without a chip (pre-2014 in some countries) → the workflow surfaces "NFC unavailable" and routes to the ID Verification + MRZ + OCR path. Same hosted URL, same webhook, same statuses. The fallback is configured in the Workflow Builder, not in your code.

  Some Android devices won't read every chip due to NFC antenna placement — Didit's iOS / Android SDKs surface a graceful retry hint before failing over to OCR.

STEP 6 — Ongoing monitoring

  Enable Ongoing AML at $0.07/user/year to keep the identity fresh. NFC re-reads aren't required for ongoing — the chip data was captured at onboarding and the binding is permanent for the document's validity period.

WEBHOOK EVENT NAMES
  - status.updated — session status changed.
  - data.updated — session data changed (resubmission, NFC retry, ongoing AML hit).

  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).
  - NFC chip reading requires the native NFC stack — iOS, Android, React Native, Flutter SDKs handle it; pure web falls back to MRZ + OCR.
  - The chip portrait (DG2) is far higher-resolution than the visual page — matching the selfie to it is meaningfully more accurate than matching to a phone-camera-captured ID photo.
  - Document Signer Certificate trust is anchored to the ICAO Public Key Directory; some countries (eg. small island states) do not publish to the PKD and will return a Passive Authentication warning rather than Approved.
  - Default record retention is 5 years post-relationship per the EU AML package.

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/nfc-verification/overview
  - https://docs.didit.me/core-technology/face-match/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

Namba za uthibitisho

Namba za uthibitisho
  • $0.00
    Kwa kila usomaji wa chip ya NFC — saini ya serikali imethibitishwa.
  • 2-4s
    Muda wa kusoma chip kutoka kugusa hadi uamuzi kwenye Android ya kiwango cha chini.
  • <0s
    Kufananisha uso wa selfie dhidi ya picha ya chip.
  • 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