Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Biometric 2FA

Badilisha nenosiri la mara moja la SMS. Fanya selfie iwe kipengele cha pili.

Imarisha mifumo nyeti kwa uthibitisho wa uso unaochukua chini ya sekunde 2 dhidi ya picha iliyosajiliwa. Inazuia phishing. Inazuia SIM-swap. $0.10 kwa uthibitisho. Uthibitishaji 500 bila malipo kila mwezi.

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.

Biometric 2FA ya giza, ya sinema, paneli nne za glasi zinazoelea, zinazopitisha mwanga katika mtazamo wa 3D kwenye nyeusi safi, zikipitishwa na mstari wa Didit Blue unaong'aa na kuwekewa fremu na mabano ya skana yanayong'aa. Kila paneli ina motifu ndogo nyeupe-nyepesi inayowakilisha kufuli, jozi ya mviringo ya kulinganisha uso, kifaa cha rununu, na kiputo cha SMS kilichovukwa.

Inazuia phishing · Inazuia SIM-swap

Hakuna code ya kuphish. Hakuna SIM ya kubadilisha.

Kipengele cha pili ni uso wa mtumiaji, unaolinganishwa 1:1 na picha waliyosajili wakati wa kujisajili. Liveness inazuia shambulio la kuchapisha / kucheza tena / barakoa / Generative Adversarial Network (GAN) kwenye fremu hiyo hiyo. Uamuzi wa chini ya sekunde 2 kwenye Android ya kiwango cha chini. $0.10 kwa uthibitisho. Uthibitishaji 500 bila malipo kila mwezi.

Jinsi inavyofanya kazi

Kutoka kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.

  1. Hatua 01

    Unda mtiririko wa kazi

    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 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 kiungo kwa mtumiaji wako, kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa stack yako.

  3. Hatua 03

    Mtumiaji anapitia mtiririko

    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 mamlaka. Matokeo chini ya sekunde mbili.

  4. Hatua 04

    Unapokea matokeo

    Webhooks zilizosainiwa kwa wakati halisi huweka database yako sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Piga API inapohitajika. Au fungua console kukagua kila kikao, kila ishara, na kudhibiti kesi zako mwenyewe.

Badilisha SMS OTP · Imeunganishwa na mtumiaji, si msimbo

Uwezo sita. $0.10 kwa uthibitisho.

Mtiririko mmoja unaobadilika, uamuzi mmoja uliosainiwa, umbo la callback sawa na mtiririko wako uliopo wa OAuth. Hakuna utegemezi wa mtoa huduma, hakuna uso wa SS7, hakuna hatari ya SIM-swap.
Soma nyarakaPata API key
01 · Mtiririko wa kugusa ili kuthibitisha

Gonga mara moja. Selfie ya chini ya sekunde 2. Imekamilika.

Fungua simu ya Sessions API, elekeza mtumiaji kwenye UI iliyopangishwa, piga fremu moja tulivu. Liveness + Kulinganisha Uso 1:1 + webhook iliyosainiwa inarudi ndani ya sekunde mbili hizo hizo. Hakuna usakinishaji wa programu, hakuna SDK, hakuna njia ya mtoa huduma.
Moduli ya Uthibitishaji wa Kibayometriki
02 · Kulinganisha Uso 1:1

Linganisha selfie ya moja kwa moja na picha iliyosajiliwa.

Picha iliyopigwa wakati wa kipindi cha awali cha KYC cha mtumiaji ndiyo template. Kila uthibitishaji unaofuata unalinganisha selfie mpya nayo na kurejesha similarity_score (0-1). Rekebisha kizingiti cha kujithibitisha kiotomatiki kwa kila workflow. $0.05 kwa kila simu ya Face Match inayojitegemea; $0.10 inapounganishwa na Liveness.
Moduli ya Face Match 1:1
03 · Inashinda mashambulizi ya SMS

SIM swap. OTP phishing. Smishing. SS7. Zote zimezuiwa.

Mashambulizi manne ambayo Shirika la Upelelezi la Marekani (FBI) na Kituo cha Kitaifa cha Usalama wa Mtandao cha Uingereza (NCSC) yanaonya kuhusu neno la siri la mara moja la SMS, SIM swap, OTP phishing, smishing kits, carrier interception, yote yanashinda SMS. Hakuna hata moja kati ya hayo yanayofanya kazi dhidi ya selfie ya moja kwa moja inayolingana na picha iliyosajiliwa. FIDO Alliance inaorodhesha uso kwenye kifaa kama sugu dhidi ya phishing.
Kwa nini SMS imevunjika
04 · Imarisha pale inapohitajika

Washa tu kwenye sehemu zinazostahili.

Ingia kutoka kifaa kipya, hamisha zaidi ya kizingiti chako cha hatari, nenosiri / mabadiliko ya mipangilio, urejeshaji wa akaunti. Unganisha na Device + IP Analysis ili uthibitishaji upya kwenye kifaa kipya kabisa + Internet Protocol (IP) mpya kabisa uongezeke kiotomatiki. Mtiririko uleule, vichochezi nadhifu zaidi.
Moduli ya Uchambuzi wa Kifaa na IP
05 · Payload moja iliyosainiwa

Mbadala rahisi wa callback yako ya OTP iliyopo.

Webhook inatoa status, similarity_score, method, na header ya X-Signature-V2 kwa uthibitishaji wa Hash-based Message Authentication Code (HMAC) SHA-256. Muundo uleule wa callback, muundo uleule wa kuelekeza upya. Timu nyingi hubadilisha SMS na uso ndani ya wiki moja.
Mkataba wa Webhook
06 · Nafuu kuliko SMS

$0.10 per auth, no carrier fees, no minimums.

Neno la siri la mara moja la SMS la Tier-1 la Marekani linagharimu kati ya $0.05 na $0.30 kwa kila kutuma kulingana na mtoa huduma, na unalipa hata kama mtumiaji hajawahi kupokea msimbo. Uthibitishaji wa kibayometriki wa Didit ni $0.10 tu na uthibitishaji 500 bila malipo kila mwezi. Hakuna utegemezi wa mtoa huduma, hakuna ushuru wa kila nchi, hakuna viwango vya chini vya mkataba.
Angalia bei
Unganisha

Kikao kimoja. Callback moja. Uamuzi mmoja.

Fungua kikao cha uthibitishaji wa kibayometriki, piga selfie kwenye UI iliyopangishwa, soma uamuzi uliosainiwa kwenye webhook yako.
POST /v3/session/Uthibitishaji upya
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_bio_2fa",
    "workflow_type": "biometric_authentication",
    "vendor_data": "user-42",
    // base64 reference selfie, ≤ 1MB (omit for liveness-only)
    "portrait_image": "/9j/4AAQSkZJRgABAQE..."
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
Inatumia LIVENESS + FACE_MATCH dhidi ya portrait_image iliyotolewa.nyaraka →
POST /v3/face-match/Seva kwa seva
$ curl -X POST https://verification.didit.me/v3/face-match/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -F "image_a=@live.jpg" \
  -F "image_b=@enrolled.jpg"
200Sawa{ "hali": "Imeidhinishwa", "alama_ya_kufanana": 0.96 }
Tumia tu unapomiliki mfumo wa kukamata data. Browser flows = hosted session.nyaraka →
Ujumuishaji tayari kwa agent

Badilisha SMS OTP kwa prompt moja.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent itaweka Didit, itajenga mfumo wa uthibitishaji wa biometriska, itabadilisha callback yako ya OTP iliyopo, na itakamilisha ndani ya wikiendi.
didit-integration-prompt.md
You are integrating Didit's Biometric 2FA into <my_stack>. Replace SMS one-time-password (OTP) on sensitive flows — login from a new device, large-value transfer, settings change, account recovery — with a sub-2-second face match against the user's enrolled portrait. Cheaper than SMS. Phishing-resistant. SIM-swap-proof.

  1. Enrol the user's portrait ONCE at sign-up via the standard Know Your Customer (KYC) session.
  2. On every sensitive action, open a Biometric Authentication session that runs Passive Liveness + Face Match 1:1 against the stored portrait. Verdict in sub-2-seconds.

Pricing (public):
  - Biometric Authentication: $0.10 per authentication (Sessions API)
  - Standalone Face Match 1:1: $0.05 per match (server-to-server)
  - First 500 verifications free every month, forever

PRE-REQUISITES
  - Production API key from https://business.didit.me (sandbox key in 60s, no card).
  - Webhook endpoint with Hash-based Message Authentication Code (HMAC) SHA-256 verification using the X-Signature-V2 header.
  - The user has previously enrolled — either via a full KYC session (recommended; the portrait is stored automatically and never leaves Didit) or via a portrait you supply on each re-auth.
  - A workflow_id from the Workflow Builder. The workflow MUST contain LIVENESS, and the session must be opened with workflow_type = "biometric_authentication" (or use a workflow that has FACE_MATCH and pass a portrait_image at session creation).

STEP 1 — Enrolment (one-time, at user sign-up)

  Run a standard KYC session at sign-up. Didit stores the portrait (the face captured during the liveness step) as the user's enrolled template, bound to vendor_data.

  POST https://verification.didit.me/v3/session/
  Body:
    {
      "workflow_id": "<your KYC workflow>",
      "vendor_data": "<your user id>"
    }

  No additional code — once the user passes KYC, their enrolled portrait is ready for every future re-auth.

STEP 2 — Re-authentication (on every sensitive action)

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<your biometric_authentication workflow>",
      "workflow_type": "biometric_authentication",
      "vendor_data": "<the same user id used at enrolment>",
      "callback": "https://<your-app>/2fa/callback",
      "metadata": {
        "reason": "<login_new_device | high_value_txn | settings_change | account_recovery>",
        "amount": "<optional, for large-value transfers>"
      },
      "portrait_image": "<base64 JPEG of the user's enrolment selfie, ≤ 1 MB — REQUIRED when the workflow has FACE_MATCH active; OMIT for liveness-only mode>"
    }

  Response: 201 Created with the hosted session_url. Redirect the user to it. The hosted UI:
    - Opens the front camera
    - Captures one passive frame
    - Runs Liveness + Face Match 1:1 against the user's enrolled portrait
    - Returns the verdict in sub-2-seconds

STEP 3 — Read the signed verdict on the webhook

  Body (excerpted for a passing re-auth):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your user id>",
      "status": "Approved",
      "liveness": { "status": "Approved", "method": "PASSIVE", "score": 96 },
      "face": {
        "status": "Approved",
        "similarity_score": 0.96
      }
    }

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

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

  Branch your application:
    Approved      → execute the action (sign in, release the transfer, save settings).
    Declined      → block the action, re-prompt with a higher-friction recovery path (support contact / KYC re-do).
    In Review     → hold; route to your operations queue.
    Not Finished  → user abandoned the capture; safe to re-prompt or fall back.

STEP 4 — Alternate path (server-to-server, when you already have the selfie)

  If you already captured the selfie locally (native mobile SDK, in-app camera):

  POST https://verification.didit.me/v3/face-match/
  Headers:
    x-api-key: <your api key>
  Body (multipart/form-data):
    image_a         <the live selfie>
    image_b         <the enrolled portrait>

  Response: similarity_score (0-1), status (Approved | Declined | In Review).

  Use the standalone path only when you trust your client-side capture pipeline. For browser flows or any surface where the SDK is not embedded, always prefer the hosted session — Didit's liveness check is harder to defeat than a raw camera grab.

WEBHOOK EVENT NAMES
  - Sessions: status changes flow through the standard session webhook.
  - Always verify X-Signature-V2 on every payload.

CONSTRAINTS
  - Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
  - Feature enum is UPPERCASE: LIVENESS, FACE_MATCH, ID_VERIFICATION, AML, IP_ANALYSIS, AGE_ESTIMATION.
  - Method enum is UPPERCASE: PASSIVE, FLASHING, ACTIVE_3D.
  - Auth header is x-api-key (lowercase, hyphenated).
  - Webhook signature header is X-Signature-V2 (NOT X-Signature).
  - Status casing matches exactly: Approved, Declined, In Review, Expired, Not Finished, Resubmitted, Kyc Expired, Abandoned.
  - The biometric template is irreversible (a one-way hash) and stored on Didit's infrastructure. You never receive the raw template. Standard data-subject-deletion rules apply.

PRO TIPS
  - Pair Biometric 2FA with Device & IP Analysis (bundled into the 200+ fraud-signal stack). A re-auth that originates from a brand-new device + a brand-new IP should always step up to face.
  - For the strongest possible surface, swap method PASSIVE for ACTIVE_3D — a short motion challenge — on transfers above your operational risk threshold.

Read the docs:
  - https://docs.didit.me/core-technology/biometric-auth/overview
  - https://docs.didit.me/sessions-api/create-session
  - 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 zinazothibitisha

Namba zinazothibitisha
  • $0.00
    Kwa kila uthibitishaji, bei tambarare. SMS OTP inatofautiana $0.05 hadi $0.30 nchini Marekani.
  • <0s
    Uthibitishaji upya kamili kwenye Android ya kiwango cha chini, kutoka kukamata hadi webhook iliyosainiwa.
  • 0
    Utegemezi wa watoa huduma, hatari ya SIM-swap, au mashambulizi ya SS7.
  • 0
    Uthibitishaji wa bure kila mwezi, milele.
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.

What is biometric 2FA?

Second-factor authentication using the user's face, not a code sent over a network. The first factor is what the user knows (password, passkey, magic link). The second factor is what the user is, a live selfie matched 1:1 against a portrait the user enrolled earlier.

It sits in the same place as SMS one-time-password (OTP) in your application flow, but with a different cost, security, and conversion profile.

Why is SMS one-time-password considered weak?

Four well-documented attack classes defeat it. The US Federal Bureau of Investigation (FBI) and UK National Cyber Security Centre (NCSC) have both published guidance steering organisations away from SMS for sensitive flows.

  • SIM swap. Attacker convinces the carrier to port the user's number to a new SIM. Every code now goes to the attacker.
  • OTP phishing. Attacker proxies the legitimate site, captures the code as the user types it, replays it before it expires.
  • Smishing kits. Pre-built kits run thousands of fake delivery / bank texts that capture codes at scale.
  • Signalling System 7 (SS7) interception. Adversaries with carrier access can passively read codes off the network.
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 is the user's face actually "enrolled"?

Most teams enrol during the user's original Know Your Customer (KYC) session. The portrait captured by the liveness step is stored bound to your vendor_data and used as the template for every subsequent re-authentication.

If you don't run KYC at sign-up, you can run a one-time enrolment session against a Didit workflow that contains only LIVENESS + FACE_MATCH. Either path costs $0.10 once, and the resulting template is reusable for every future authentication.

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.

What does the integration look like?

It's a drop-in for your existing one-time-password callback contract.

  • POST /v3/session/ with workflow_type: "biometric_authentication" and the same vendor_data you used at enrolment.
  • Redirect the user to the returned session_url.
  • Verify the X-Signature-V2 header on the webhook before trusting the body.
  • Branch on status, Approved (execute the action), Declined (block), In Review (queue), Not Finished (re-prompt).

Most teams swap SMS for face in a weekend. Full agent-pastable prompt is above; Model Context Protocol (MCP) server speaks both surfaces.

What if the user's face changed (haircut, beard, glasses)?

Face Match 1:1 is resilient to moderate appearance change, facial hair, glasses, hair colour, lighting. The similarity score returned per authentication reflects how confident the model is.

For users who drift outside the auto-approve threshold (typical case: dramatic weight change, surgery, ageing over many years), the verdict returns In Review and routes to your operations queue. The standard recovery path is a re-enrolment session, one KYC call refreshes the portrait, and the next authentication uses the new template.

Is this compliant with EU PSD2 strong customer authentication?

Yes for the inherence category. The European Banking Authority Regulatory Technical Standards on Strong Customer Authentication recognise biometric attributes (something you are) as a valid second factor when paired with one of the other two categories (knowledge or possession).

For a full PSD2 strong-customer-authentication flow, pair biometric 2FA with the user's password (knowledge) or a device-bound session (possession). The signed Didit verdict is the audit-pack evidence of the inherence factor.

Related

Moduli zinazohusiana + mifumo ya kazi

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