Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Ukadiriaji wa Umri

Weka kikomo cha umri kwa mtumiaji yeyote.
Bila kuwauliza kitambulisho.

Kadiria umri wa mtumiaji kutoka kwa selfie, hakuna upakiaji wa kitambulisho, hakuna usumbufu. Chini ya sekunde mbili, usahihi wa ±3.5-mwaka, iBeta-certified liveness kwenye upigaji picha uleule. $0.10 kwa kila ukaguzi, 500 bure/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.

Didit Ukadiriaji wa Umri, ukaguzi wa umri unaobadilika kutoka kwa selfie moja.

Chini ya sekunde 2 kwenye kifaa

Kadiri umri kwa milisekunde.
Hakuna hati inayohitajika.

Uchambuzi wa uso kwenye kifaa unatoa makadirio ya umri chini ya sekunde mbili, hakuna picha ya kitambulisho, data ndogo ya kibinafsi. Imejengwa kwenye injini ileile iliyothibitishwa na iBeta Level 1 kwa ugunduzi wa mashambulizi ya uwasilishaji.

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 uleule kwenye API yetu. Panga masharti, fanya majaribio ya A/B, hakuna code inayohitajika.

  2. Hatua 02

    Unganisha

    Pachika asili na Web, iOS, Android, React Native, au Flutter SDK yetu. 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 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 vyenye mamlaka. Matokeo chini ya sekunde mbili.

  4. Hatua 04

    Unapokea matokeo

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

Imejengwa kwa waendelezaji · Imejengwa dhidi ya udanganyifu · Wazi kwa muundo

Uwezo sita. Feature flag moja. AGE_ESTIMATION.

Kila uwezo hapa chini ni swichi kwenye moduli moja. Hakuna viwango vya upsell, hakuna SKU tofauti, hakuna simu za nyongeza. Viwashe kwa kila workflow au vipitishe moja kwa moja kwenye API call.
Soma nyarakaPata API key
01 · Mtiririko wa selfie pekee

Thibitisha umri bila kupakia kitambulisho.

Jibu la data ndogo kwa biashara zenye vizuizi vya umri, maudhui ya watu wazima, utoaji wa pombe, kamari mtandaoni. Selfie moja tu inatosha kwa wengi, ikipunguza drop-off ikilinganishwa na kupakia kitambulisho kamili. Inalingana na Sheria ya Usalama Mtandaoni ya Uingereza na kanuni za umri zinazofaa za California.
02 · Usahihi

± miaka 3.5 katika kila kundi la umri.

Wastani wa makosa ni miaka 3.5 kwa ujumla, 89% ya makadirio huangukia ndani ya ± miaka 5, 76% ndani ya ± miaka 3. Utendaji kwa kila kundi umechapishwa, miaka 1.5 chini ya 18, miaka 2.8 kwa 18–25, miaka 3.9 kwa 41–60, ili uweze kupima kizingiti chako dhidi ya namba halisi, si sifa za wauzaji.
03 · Usawa wa idadi ya watu

Imefunzwa kwa mamilioni ya nyuso. Katika kila kundi la idadi ya watu.

Upendeleo ndio kasoro kubwa zaidi katika mifumo ya kukadiria umri, na ndio wadhibiti huangalia. Mifumo yetu inafunzwa kwenye data iliyosawazishwa kulingana na umri, kabila, jinsia, na hali ya mwanga, na makosa kwa kila kundi yamechapishwa badala ya kuwekwa wastani. Inafunzwa upya kila mara ili kukabiliana na mabadiliko ya idadi ya watu.
04 · Vizingiti vinavyoweza kusanidiwa

Rekebisha sera kwa kila workflow na kwa kila nchi.

Kizingiti cha kukataa (chaguo-msingi 18) na kiwango cha chini cha liveness ya uso kwa kila workflow. Weka sheria za nchi juu yake, umri wa chini/juu kwa kila nchi na overrides za ngazi ya jimbo pale inapohitajika (Mississippi 21, Alabama 19, US default 18). Bofya mara moja hutumia umri halali wa watu wazima duniani kote kama msingi; rekebisha isipokuwa.
05 · Adaptive ID fallback

Kesi zisizo wazi hupelekwa kiotomatiki kwenye ukaguzi wa hati.

Wale wanaopita wazi na wanaofeli wazi humaliza kwa selfie pekee. Makadirio yasiyo wazi, wachache wasio na uhakika karibu na kizingiti chako, huwasha kiotomatiki mtiririko wetu wa Adaptive Age Verification, unaosimamiwa na sheria za nchi kwenye hatua ya kitambulisho. Watumiaji wengi humaliza kwa selfie; ukaguzi wa hati huwashwa tu wakati hesabu inasema unahitaji. Inatozwa $0.15 kwa kila ID Verification fallback.
06 · Msingi wa uhai

Upigaji picha mmoja. Ishara mbili. Injini sawa na Liveness.

Ukadiriaji wa umri hutumia mfumo wetu wa iBeta Level 1 PAD (presentation attack detection) liveness pipeline, selfie hiyo hiyo inatoa uamuzi wa binadamu halisi na kundi la umri. Inashinda deepfakes, picha zilizochapishwa, marudio ya skrini, na barakoa za silikoni kabla ya mfumo wa umri kuanza. Iwashe kwenye Liveness workflow na upigaji picha mmoja huwasha sehemu zote mbili.
Unganisha

Endpoints mbili. JSON moja. Bei moja.

Fungua session wakati unataka UI yetu itumie selfie (na Adaptive ID fallback kwa kesi zisizo wazi). Piga simu endpoint ya pekee wakati tayari unayo selfie. Umri utachunguzwa vile vile.
POST /v3/session/Hosted UI
$ 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_age_adaptive",
    "vendor_data": "user-42"
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
Tunakaribisha UI ya kukusanya data. Inahitajika kwa Adaptive ID fallback.nyaraka →
POST /v3/age-estimation/Server kwa server
$ curl -X POST https://verification.didit.me/v3/age-estimation/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -F "user_image=@selfie.jpg" \
  -F "age_estimation_decline_threshold=18"
200OK{ "status": "Approved", "age_estimation": 27.33 }
Wewe unamiliki mchakato wa kukusanya data. Tunarejesha umri papo hapo.nyaraka →
Ujumuishaji tayari kwa agent

Tumia Age Estimation kwa prompt moja.

Bandika block iliyo hapa chini kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza nafasi ya my_stack na framework, lugha, na matumizi yako. Agent itaweka Didit, kuunda workflow, kuunganisha webhook, na kuanza kutumika.
didit-integration-prompt.md
# Didit Age Estimation — integrate in 5 minutes

You are integrating Didit's Age Estimation module into <my_stack>. Follow
these steps exactly. Every URL, header, and enum 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. Two integration paths — pick one

### Path A — Workflow Builder (hosted UI)
Best when you want Didit to handle the camera, framing, low-light
fallback, mobile handoff, and accessibility for you. Required if you want
Adaptive Age Verification (auto-fall-back to ID for borderline cases).

1. Create a workflow that contains the AGE_ESTIMATION feature:
   POST https://verification.didit.me/v3/workflows/
   Authorization header:  x-api-key: <your-api-key>
   Body: workflow_label, features array with the single entry
         { feature: "AGE_ESTIMATION" }   (UPPERCASE — strict enum)
   Optional config:
     - age_estimation_decline_threshold (default 18)
     - face_liveness_score_decline_threshold (default 30)
     - adaptive_id_verification (when true, borderline cases trigger ID
       verification fallback governed by per-country age restrictions on
       the ID Verification step)
     - per_country_age_restrictions (map of country -> min / max age,
       with optional state-level overrides)

2. Create a verification session for an end user:
   POST https://verification.didit.me/v3/session/
   Body: workflow_id (from step 1), vendor_data (your own user id).
   Response: session_url — redirect the user to it.

3. Listen for webhook callbacks (see "Webhooks" below).

### Path B — Standalone server-to-server API
Best when you already have a selfie image (mobile SDK capture, native
onboarding app, reseller pipeline) and only need a numeric age estimate
plus passive-liveness verdict on it. No adaptive ID fallback on this
path — wire that yourself if you need it.

POST https://verification.didit.me/v3/age-estimation/
Content-Type: multipart/form-data
Body fields:
  - user_image                              (required, file — single selfie)
  - age_estimation_decline_threshold        (optional integer 0-100, default 18)
  - face_liveness_score_decline_threshold   (optional integer 0-100, default 30)
  - rotate_image                            (optional boolean, default false)
  - save_api_request                        (optional boolean, default true)
  - vendor_data                             (optional string, your user id)

Response: JSON with request_id, age_estimation block, created_at.

## 3. Webhooks (Path A only — Path B returns synchronously)
- Register a webhook destination once via
  POST https://verification.didit.me/v3/webhook/destinations/
  Body: url, subscribed_events: ["session.verified", "session.review_started",
                                  "session.declined"]
- Response includes secret_shared_key — store it.
- Every webhook 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.

## 4. Reading the report

### Path A (session) — age_estimation lives on the liveness object
The liveness object on the session report includes age_estimation as a
number-of-years field on the same selfie capture:
- liveness.status           "Approved" | "Declined" | "In Review" | "Not Finished"
- liveness.method           "PASSIVE" | "FLASHING" | "ACTIVE_3D"
- liveness.score            number 0-100  (normalized liveness score)
- liveness.reference_image  signed URL to the captured selfie (60-minute TTL)
- liveness.age_estimation   estimated age in years (e.g. 24.3)
- liveness.warnings         Array of risk objects (see below)

### Path B (standalone) — top-level age_estimation block
- request_id                          uuid
- age_estimation.status               "Approved" | "Declined" | "In Review"
- age_estimation.method               "PASSIVE"
- age_estimation.score                number 0-100  (passive-liveness score)
- age_estimation.age_estimation       estimated age in years (e.g. 27.33)
- age_estimation.user_image.entities  array of detected faces, each with
                                       age, bbox, confidence, gender
- age_estimation.user_image.best_angle integer
- age_estimation.face_quality         0-100 face image quality score
- age_estimation.face_luminance       0-100 face luminance score
- age_estimation.warnings             Array of risk objects (see below)
- created_at                          ISO8601

### Warning catalog (both paths)
- AGE_BELOW_MINIMUM            estimated age below the configured threshold
- AGE_NOT_DETECTED             unable to estimate age (quality / lighting)
- LOW_LIVENESS_SCORE           passive-liveness score below threshold
- NO_FACE_DETECTED             no face in the capture
- LIVENESS_FACE_ATTACK         presentation attack suspected
- FACE_IN_BLOCKLIST            face matches an entry in your blocklist
- POSSIBLE_DUPLICATED_FACE     face matches a previously verified face

## 5. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: AGE_ESTIMATION, LIVENESS, ID_VERIFICATION,
  FACE_MATCH, AML, IP_ANALYSIS.
- 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).
- Always verify webhook signatures before trusting payload data.
- Status casing matches exactly: "Approved", "Declined", "In Review",
  "Not Finished" (title-cased, space-separated).
- Reference image / video URLs are signed and expire in 60 minutes —
  store only the verdict + score, never the biometric media.

## 6. Pricing reference (public)
- AGE_ESTIMATION standalone or bundled inside a workflow: $0.10 per check
- Adaptive fallback to ID Verification (when triggered): $0.15 per check
- Bundled in a full KYC workflow alongside Liveness + ID + IP: $0.33 per session
- 500 free verifications every month, forever, on every account.

## 7. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Test images: deterministic synthetic faces returned in sandbox
  (predictable estimated age band; trigger AGE_BELOW_MINIMUM by sending
  the canonical "minor" test image).
- Switch to live: flip the application environment toggle in console.

When in doubt: https://docs.didit.me/core-technology/age-estimation/overview
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

Thibitisha namba

Thibitisha namba
  • ±3.5y
    Wastani wa makosa katika kila kundi la umri.
  • 0%
    Makadirio ndani ya ± miaka 5 ya umri halisi.
  • <0s
    Uchambuzi kamili kwa kila kipindi, unaotolewa kwenye edge.
  • $0.00
    Kwa kila ukaguzi wa Age Estimation unaojitegemea.
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 Age Estimation?

Age Estimation estimates a user's age from a single selfie, passive, no Identity Document required, no motion challenge. Useful when you need to age-gate access (alcohol, gambling, adult content, mature platforms) but capturing a full Identity Document would be overkill for most users.

Overall mean absolute error (MAE) is ±3.5 years. $0.10 per check on the standalone Application Programming Interface (API), bundled at the same price inside a workflow. Aligned with the United Kingdom Online Safety Act and European Union age-gating expectations. Full reference: docs.didit.me/core-technology/age-estimation/overview.

What does Age Estimation cost?
$0.10 per check on the standalone POST /v3/age-estimation/ endpoint, or $0.10 bundled inside a workflow alongside Liveness. The Adaptive Age Verification fallback (when a borderline case auto-triggers an Identity Document upload) bills at the regular $0.15 Identity Document Verification rate, only on the borderline minority, not on every session. Public pricing: didit.me/pricing.
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.

What is the response shape?

On the session Application Programming Interface (API), Age Estimation lives on the liveness object as age_estimation, the same selfie capture produces both signals (one capture, two outputs).

On the standalone Application Programming Interface (API) (POST /v3/age-estimation/), the response carries a top-level age_estimation block:

  • status, Approved, Declined, In Review, Not Finished.
  • method, PASSIVE.
  • score, age_estimation (estimated age in years), face_quality, face_luminance, warnings.
  • user_image.entities[], per-face age, bounding box, confidence, gender.
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.

Related

Moduli zinazohusiana

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