Ruka hadi maudhui makuu
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Uthibitishaji wa Hifadhidata

Linganisha kitambulisho chochote.
Dhidi ya chanzo kilichokitoa.

Linganisha jina, nambari ya kitambulisho, au anwani na chanzo kilichoitoa, sajili 1,000+, ofisi, na kampuni za simu kupitia simu moja. Kuanzia $0.05 kwa kila ukaguzi, 500 bila malipo/mwezi.

Anza bureSoma nyaraka
Inaungwa mkono na
Y CombinatorRobinhood Ventures
Firecrawl
Slash
Crnogorski Telekom
UCSF Neuroscape
Bit2Me
Shiply

Inaaminika na mashirika 2,000+ duniani kote.

Rejista za serikali

Thibitisha vitambulisho dhidi ya
hifadhidata hai za kitaifa.

Thibitisha mtu na kitambulisho chake dhidi ya rekodi rasmi, SSN, RFC, CPF, Aadhaar, NIN, na rejista nyingine 60+ za kitaifa. Bei imechapishwa kwa kila nchi.

Jinsi inavyofanya kazi

Kuanzia 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 chapisha 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. Mtumiaji anapokuwa kwenye mtiririko, tunapata alama za ishara 200+ za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vyenye mamlaka. Matokeo yanapatikana chini ya sekunde mbili.

  4. Hatua 04

    Unapokea matokeo

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

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

Uwezo sita. Bendera moja ya kipengele. DATABASE_VALIDATION.

Kila uwezo hapa chini ni swichi kwenye moduli moja. Hakuna viwango vya kuongeza mauzo, hakuna mipango tofauti, hakuna simu za nyongeza, washa huduma unazotaka kwa kila mtiririko wa kazi.
Soma nyarakaPata API key
01 · Katalogi ya vyanzo

Vyanzo 1,000+ vyenye mamlaka. Simu moja.

Rejista za kiraia, mamlaka za kodi, orodha za wapiga kura, ofisi za mikopo, kampuni za simu, rekodi za mahakama, na uthibitishaji wa anwani, zote zinafikiwa kupitia endpoint moja. Chanzo kipya huongezwa kila mwezi na huonekana kiotomatiki.
02 · Aina za vyanzo

Rejista. Ofisi. Kampuni za simu. Mahakama. Anwani.

Chagua eneo la data linalolingana na udanganyifu unaoupambana nao. Ukaguzi wa rejista za kiraia hushinda vitambulisho bandia. Ukaguzi wa ofisi za mikopo unathibitisha historia. Ukaguzi wa kampuni za simu unathibitisha laini inayotumika. Uthibitishaji wa anwani unathibitisha makazi.
03 · Uratibu wa kila chanzo

Endesha huduma sambamba. Uaminifu wa juu zaidi hushinda.

Washa idadi yoyote ya huduma kwa kila nchi na Didit huzianzisha sambamba. Chanzo kimoja kinachothibitisha ni ishara kali, vyanzo viwili huru vinavyothibitisha ni uamuzi wenye nguvu zaidi tunaoweza kurudisha.
04 · Muundo wa ripoti

Kulinganisha kwa kila sehemu. Data ya chanzo. Alama ya biometriska.

Kila chanzo kinarudisha uamuzi wa kila sehemu, msimbo wa matokeo, na rekodi safi ya rejista, jina kamili, tarehe, picha, saini, na alama ya kulinganisha uso kwenye huduma za biometriska kama RENAPER ya Argentina na Tribunal Electoral ya Panama.
05 · Ufikiaji wa kikanda

Amerika Kusini, Uhispania, na nchi 45+.

Rejista 19 za kiraia zilizounganishwa moja kwa moja kote Amerika Kusini na Uhispania. Hifadhidata 156 katika nchi nyingine 45 kupitia mtandao wa utambulisho wa kimataifa. Uunganishaji mpya kwa kawaida huenda hewani ndani ya wiki mbili hadi tatu kwa ombi.
06 · Malipo ya kutofautiana kwa kila simu

Kuanzia $0.05 kwa kila hundi. Hakuna kiwango cha chini. 500 bure.

Unatozwa tu kwa swala lililofanikiwa. Kiwango cha bei nafuu zaidi $0.05 (Jamhuri ya Dominika). Kiwango cha kawaida cha rejista ya serikali $0.20 (Argentina, Brazil, Mexico, Uhispania, Kolombia, Peru, Chile, na zaidi). Huduma zilizorukwa hazitozwi kamwe.
Unganisha

Endpoints mbili. JSON sawa. Katalogi sawa.

Acha Didit inase kitambulisho na kuvuta sehemu kiotomatiki, au tuma data ya utambulisho moja kwa moja ikiwa tayari unayo. Muundo sawa wa JSON unapotoka.
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_db_validation",
    "vendor_data": "user-42"
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
Didit inachukua ID, inavuta sehemu kiotomatiki, na kuendesha kila chanzo kilichowezeshwa.nyaraka →
POST /v3/database-validation/Seva kwa seva
$ curl -X POST https://verification.didit.me/v3/database-validation/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -F "issuing_state=BRA" \
  -F "services=bra_cpf" \
  -F "identification_number=12345678900"
200Sawa{ "match_type": "full_match", "validation_type": "1x1" }
Unamiliki data ya utambulisho. Tunaipeleka kwenye rejista sahihi na kurejesha uamuzi papo hapo.nyaraka →
Ujumuishaji tayari kwa agent

Tuma Uthibitishaji wa Hifadhidata kwa haraka.

Bandika kizuizi hapa chini kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako, framework, lugha, kesi ya matumizi, na agent atatuma workflow, webhook, na msimbo wa uamuzi mwisho hadi mwisho.
didit-integration-prompt.md
# Didit Database Validation — integrate in 5 minutes

You are integrating Didit's Database Validation module into <my_stack>.
Database Validation cross-references each user's identity data against the
authoritative source for that country — the national civil registry, tax
authority, electoral roll, credit bureau, telco database, court record or
biometric service that issued the document. 1,000+ data sources reachable
through one endpoint. 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 capture the ID document, run Optical Character Recognition (OCR), derive the
required fields automatically, and trigger the right registry service per
issuing country.

1. Create a workflow that contains the DATABASE_VALIDATION feature:
   POST https://verification.didit.me/v3/workflows/
   Authorization header:  x-api-key: <your-api-key>
   Body: workflow_label, features array including
         { feature: "DATABASE_VALIDATION" }   (UPPERCASE — strict enum)
   Configure per-country service IDs (e.g. arg_renaper, bra_cpf,
   mex_curp, dom_cedula) plus partialMatchAction / noMatchAction.

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 the identity fields (mobile SDK capture,
existing onboarding pipeline, reseller flow). Single endpoint, every
country and every service routed through it.

POST https://verification.didit.me/v3/database-validation/
Content-Type: multipart/form-data
Body fields (all optional except issuing_state and at least one identifier):
  - issuing_state           (required, ISO 3166-1 alpha-3, e.g. ARG, BRA, MEX)
  - services                (optional, repeated, service IDs to run; omit
                             to run every configured service for that country)
  - identification_number   (e.g. DNI, CPF, CURP, cedula number)
  - first_name
  - last_name
  - date_of_birth           (YYYY-MM-DD)
  - selfie                  (file, required for biometric services such as
                             arg_renaper, pan_cedula_sib, pan_cedula_sib_plus)
  - address_element_1       (street + number)
  - address_element_2       (unit / building / floor)
  - address_element_3       (suburb / district)
  - address_element_4       (city / state / region)
  - address_element_5       (postal code; postal_code alias accepted)
  - consent                 (boolean — required when the selected service
                             has requires_consent=true in the catalog)
  - vendor_data             (optional string, your user id)

Response: JSON report with match_type, validation_type (1x1 or 2x2),
per-service validations, source_data, and any warnings.

## 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 (both paths return the same shape)
The database_validation object includes:
- status: "Approved" | "Declined" | "In Review" | "Not Finished"
- match_type: "full_match" | "partial_match" | "no_match"
- issuing_state: ISO 3166-1 alpha-3 country code
- validation_type: "1x1" (single source full-match) or "2x2" (two
  independent sources corroborate the data)
- screened_data: the user fields submitted (identification_number,
  first_name, last_name, date_of_birth, selfie, address fields, ...)
- validations: array of per-service results. Each entry carries
  service_id (e.g. arg_renaper), service_name, outcome_code (MATCH,
  NO_MATCH, DOCUMENT_NOT_FOUND, BIOMETRIC_IMAGE_UNUSABLE,
  REGISTRY_UNAVAILABLE, ...), optional outcome_detail, a per-field
  validation block (full_match / partial_match / no_match), and a
  source_data block lifted from the registry record (photo, signature,
  full_name, gender, dates, face_match_score for biometric services).

Configurable risks (action per workflow — Decline, Review, or Approve):
- DATABASE_VALIDATION_PARTIAL_MATCH    (partialMatchAction)
- DATABASE_VALIDATION_NO_MATCH         (noMatchAction)

Warnings raised when a service cannot run:
- COULD_NOT_PERFORM_DATABASE_VALIDATION — required input field missing
  (e.g. CPF could not be OCR-extracted). You are NOT charged. Session
  auto-moves to In Review; saving the missing field in the Console
  retriggers the check.

## 5. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: DATABASE_VALIDATION, ID_VERIFICATION,
  LIVENESS, FACE_MATCH, AML, IP_ANALYSIS.
- Country codes are ISO 3166-1 alpha-3 UPPERCASE: ARG, BRA, MEX, ESP, ...
- Service IDs are lowercase snake-case with a country prefix:
  arg_renaper, bra_cpf, mex_curp, dom_cedula, pan_cedula_sib_plus, ...
- 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",
  "Not Finished" (title-cased, space-separated).
- match_type casing matches exactly: full_match, partial_match, no_match
  (lowercase snake-case).
- You are only billed when a service returns a result. Skipped services
  (missing input, unsupported issuing_state) are never billed.

## 6. Pricing reference (public, pay-per-call)
- Variable per source. Lowest tier: $0.05 per check (Dominican Republic,
  Junta Central Electoral).
- Standard government-registry tier: $0.20 per check (Argentina RENAPER,
  Brazil Receita Federal CPF, Mexico RENAPO CURP, Spain DGP, Colombia
  Registraduria, Peru RENIEC, Chile Registro Civil, Ecuador, Uruguay,
  El Salvador, Guatemala, Honduras, Bolivia, Paraguay, Venezuela, Costa
  Rica).
- Biometric premium tier: $0.75 (Panama SIB) up to $1.50 (Panama SIB
  Plus elevated tier with stronger biometric thresholds).
- Global identity network: 156 datasets across 45 countries (AU, NZ,
  UK, IE, FR, DE, IT, ES, PT, NL, BE, CH, AT, Nordics, Greece, Poland,
  Czechia, Hungary, Romania, Slovakia, India, Indonesia, Philippines,
  Thailand, Malaysia, Singapore, Hong Kong, China, Cambodia, Kenya,
  Nigeria, South Africa, Morocco, USA, Canada). Per-service pricing
  surfaced in the catalog and billing exports.
- 500 free checks every month, forever, on every account.

## 7. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Test the full catalog of services with the per-country reference pages
  under https://docs.didit.me/api-reference/database-validation/.
- Switch to live: flip the application's environment toggle in console.

When in doubt: https://docs.didit.me/core-technology/database-validation/overview
Upatikanaji wa rejista zenye mamlaka

147 rejista zenye mamlaka — zinazoweza kutafutwa.

Kila mtoa huduma wa Uthibitishaji wa Hifadhidata Didit huangalia, pamoja na URL ya rejea halisi na kategoria ya uthibitishaji. Imetolewa kutoka kwenye katalogi ya nyaraka za Mintlify ambayo Business Console husoma kutoka, tafuta kwa jina la nchi, msimbo wa ISO 3166-1 alpha-3, au kitambulisho cha huduma. 147 huduma · 53 nchi.

Rejea halisi: docs.didit.me/core-technology/database-validation/overview

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+
    Vyanzo vya kuaminika, simu moja.
  • 0
    Rejista za kiraia za Amerika Kusini na Uhispania, zimeunganishwa moja kwa moja.
  • Kuanzia $0.05
    Kwa kila hundi. Unalipia tu matokeo.
  • <0.0s
    Mwisho hadi mwisho kwenye trafiki ya uzalishaji.
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

Didit ni nini?

Didit ni miundombinu ya utambulisho na udanganyifu, jukwaa ambalo tulitamani lingekuwepo tulipokuwa tukijenga bidhaa sisi wenyewe: wazi, rahisi, na rafiki kwa waendelezaji, ili lifanye kazi kama sehemu halisi ya stack yako badala ya sanduku jeusi unalounganisha.

API moja inashughulikia kuthibitisha watu (KYC, mjue mteja wako), kuthibitisha biashara (KYB, ijue biashara yako), kuchunguza pochi za crypto (KYT, ijue miamala yako), na kufuatilia miamala kwa wakati halisi, kwenye stack iliyojengwa kuwa:

  • Haraka, p99 chini ya sekunde 2 kwenye kila session
  • Inaaminika, inatumika na kampuni 1,500+ katika nchi 220+
  • Salama, SOC 2 Aina ya 1, ISO 27001, GDPR-native, na imethibitishwa rasmi na mdhibiti wa kifedha wa Uhispania kuwa salama zaidi kuliko kumthibitisha mtu ana kwa ana

Upeo wa chini: aina 14,000+ za hati katika lugha 48+, vyanzo vya data 1,000+, na ishara za udanganyifu 200+ kwenye kila session. Miundombinu ya Didit hujifunza kwa nguvu kutoka kila session na inaboreshwa kila siku.

Uthibitishaji wa Hifadhidata ni nini?

Uthibitishaji wa Hifadhidata hulinganisha data ya utambulisho wa mtumiaji, jina, tarehe ya kuzaliwa, namba ya kitambulisho, anwani, dhidi ya vyanzo 1,000+ vya mamlaka vinavyoweza kufikiwa kupitia endpoint moja. Sajili za kiraia za serikali, mamlaka za kodi, orodha za wapiga kura, ofisi za mikopo, hifadhidata za telco, rekodi za mahakama, na uthibitishaji wa anwani.

Inashinda vitambulisho bandia (DNI bandia au Cadastro de Pessoas Físicas (CPF) ya Brazil haitakuwa kwenye rekodi rasmi), inathibitisha ukaazi kwa ajili ya kuingia kwa Anti-Money Laundering Directive 6 (AMLD6), na inaelekeza kiotomatiki kwa issuing_state ili usihitaji kuweka hard-code watoa huduma kwa kila nchi.

Rejea kamili: docs.didit.me/core-technology/database-validation/overview.

Uthibitishaji wa Hifadhidata unagharimu kiasi gani?

Inatofautiana kwa kila mtoa huduma, inatozwa tu kwa matokeo. Hakuna viwango vya chini, hakuna ada za jukwaa, hakuna tozo kwa huduma zilizorukwa.

  • Kiwango cha bei nafuu zaidi $0.05 kwa kila ukaguzi (Dominican Republic kupitia Junta Central Electoral).
  • Kiwango cha kawaida cha sajili ya serikali $0.20 (Argentina, Brazil, Mexico, Uhispania, Colombia, Peru, Chile, na zaidi).
  • Biometric premium $0.75–$1.50 (Panama Servicio de Identificación Biométrica (SIB) na SIB Plus).

Imejumuishwa ndani ya mtiririko kamili wa Know Your Customer (KYC) pamoja na Uthibitishaji wa Hati ya Utambulisho + Liveness + Face Match: $0.33 kwa kila session.

Uthibitishaji ni wa haraka kiasi gani kwa mtumiaji wangu wa mwisho?

Mtiririko kamili kwa kawaida huchukua chini ya sekunde 30 kuanzia mwanzo hadi mwisho, chukua kitambulisho, piga picha hati, piga selfie, umemaliza. Huu ndio wa haraka zaidi sokoni. Watoa huduma wa zamani wa KYC kwa kawaida huchukua zaidi ya sekunde 90 kwa mtiririko huo huo.

Kwa upande wa backend, Didit inarudisha matokeo kwa chini ya sekunde mbili kwa p99, ikipimwa kutoka wakati mtumiaji anamaliza selfie hadi wakati webhook yako inawaka. Upigaji picha wa simu umeboreshwa kwa simu za polepole na mitandao ya polepole: ukandamizaji wa picha unaoendelea, upakiaji wa polepole wa SDK, na uhamishaji wa kugusa mara moja kutoka desktop kwenda simu kupitia QR code ikiwa mtumiaji anaanza kwenye wavuti.

Muundo wa majibu ni upi?

Kitu cha database_validation kinarudisha:

  • status, Approved, Declined, In Review.
  • match_type, full_match, partial_match, no_match.
  • validation_type, 1x1 (sajili moja inathibitisha) au 2x2 (sajili mbili huru zinathibitisha, uaminifu wa juu zaidi tunaoweza kueleza).
  • validations[], safu za kila huduma zenye service_id, matokeo ya kila sehemu, outcome_code (MATCH, NO_MATCH, DOCUMENT_NOT_FOUND, BIOMETRIC_IMAGE_UNUSABLE, REGISTRY_UNAVAILABLE), na source_data iliyochukuliwa kutoka rekodi ya sajili, jina kamili, tarehe, Uniform Resource Locator (URL) ya picha, saini, pamoja na face_match_score kwa huduma za biometriska.

Muundo sawa kwenye Application Programming Interface (API) inayojitegemea na kwenye mtiririko wa session.

Nini kinatokea ikiwa mtumiaji atashindwa, kuacha, au muda wake kuisha?

Kila session inatua kwenye mojawapo ya hali saba zilizo wazi, kwa hivyo code yako inajua nini cha kufanya:

  • Approved, kila ukaguzi umefaulu. Endeleza mtumiaji.
  • Declined, ukaguzi mmoja au zaidi umeshindwa. Unaweza kumruhusu mtumiaji kutuma tena hatua maalum iliyoshindwa (kwa mfano, piga tena selfie) bila kuendesha tena mtiririko mzima.
  • In Review, imewekwa alama kwa ukaguzi wa kufuata. Fungua kesi kwenye console, angalia kila ishara, amua kuidhinisha au kukataa.
  • In Progress, mtumiaji yuko katikati ya mtiririko.
  • Not Started, kiungo kimetumwa, mtumiaji bado hajafungua. Tuma ukumbusho ikiwa inakaa muda mrefu sana.
  • Abandoned, mtumiaji alifungua kiungo lakini hakumaliza kwa wakati. Shirikisha tena au muda wake uishe.
  • Expired, kiungo cha session kimepitwa na wakati. Unda session mpya.

Webhook iliyosainiwa inawaka kwenye kila mabadiliko ya hali, kwa hivyo hifadhidata yako inabaki sawa kila wakati. Sessions zilizoachwa na zilizokataliwa ni bure.

Data ya mteja wangu inakaa wapi na inalindwaje?

Data ya uzalishaji inachakatwa na kuhifadhiwa katika Umoja wa Ulaya kwa chaguo-msingi, kwenye Amazon Web Services. Mikataba ya biashara inaweza kuomba mikoa mbadala kwa mamlaka ambazo wadhibiti wao wanahitaji.

Usimbaji fiche kila mahali. AES-256 wakati wa kupumzika kwenye kila hifadhidata, hifadhi ya vitu, na backup. Transport Layer Security 1.3 wakati wa usafiri kwenye kila simu ya API, webhook, na session ya Business Console. Data ya biometriska imesimbwa kwa kutumia Customer Master Key tofauti.

Uhifadhi ni wako kudhibiti. Uhifadhi wa chaguo-msingi ni usio na kikomo (unlimited) isipokuwa ukisanidi mfupi zaidi, kati ya siku 30 na miaka 10 kwa kila programu, na unaweza kufuta session yoyote binafsi wakati wowote kutoka kwenye dashibodi au API.

Vyeti: SOC 2 Aina ya 1 (ukaguzi wa Aina ya 2 unaendelea), ISO/IEC 27001:2022, iBeta Level 1 PAD, na uthibitisho wa umma kutoka Tesoro / SEPBLAC / CNMV ya Uhispania kwamba uthibitishaji wa utambulisho wa mbali wa Didit ni salama zaidi kuliko kumthibitisha mtu ana kwa ana. Ripoti kamili inapatikana /security-compliance.

Je, Didit inatii sheria kwa tasnia yangu?

Didit inatii kanuni za udhibiti muhimu kwa miundombinu ya utambulisho:

  • GDPR + UK GDPR, mgawanyo wa mtawala / mchakato, Mkataba kamili wa Uchakataji Data ulichapishwa, mamlaka kuu ya usimamizi ilitajwa (AEPD ya Uhispania).
  • AMLD6 + EU AML Single Rulebook, vikwazo 1,300+, mtu mashuhuri kisiasa, na orodha za habari hasi huchunguzwa kwa wakati halisi.
  • eIDAS 2.0, Imeunganishwa na EU Digital Identity Wallet; tayari kwa utambulisho unaoweza kutumika tena.
  • MiCA (Markets in Crypto-Assets), tayari kwa crypto on-ramps, exchanges, na custodians.
  • DORA, Sheria ya Ustahimilivu wa Uendeshaji wa Dijitali, ustahimilivu wa uendeshaji wa huduma za kifedha za EU.
  • BIPA, CUBI, Washington HB 1493, CCPA / CPRA, faragha ya kibayometriki ya Marekani (Illinois, Texas, Washington) na faragha ya watumiaji wa California.
  • UK Online Safety Act, majukumu ya kudhibiti umri na usalama wa watoto.
  • FATF Travel Rule, data ya mwanzilishi na mnufaika kwenye uhamishaji wa crypto, IVMS-101 inayoendana.

Memo ya kina, kila cheti, kila barua ya mdhibiti: /security-compliance.

Ninaweza kuunganisha na kuanza kuthibitisha watumiaji haraka kiasi gani?
  • Sekunde 60 kupata akaunti ya sandbox kwenye business.didit.me, hakuna kadi ya mkopo.
  • Dakika 5 kupata uthibitishaji unaofanya kazi kupitia Claude Code, Cursor, au wakala yeyote wa kuweka code kupitia seva yetu ya Model Context Protocol (MCP).
  • Wikiendi moja kupata muunganisho tayari kwa uzalishaji na uthibitishaji wa webhook uliosainiwa, majaribio upya, na mtiririko wa kurekebisha pale mtumiaji anapokataliwa.

Njia tatu za kuunganisha, chagua inayofaa stack yako:

  • Pachika moja kwa moja na Web, iOS, Android, React Native, au Flutter SDK yetu.
  • Elekeza mtumiaji kwenye ukurasa wa uthibitishaji uliopangishwa, hakuna SDK.
  • Tuma kiungo kwa barua pepe, SMS, WhatsApp, au chaneli yoyote, hakuna kazi ya front-end.

Dashibodi ileile, bili ileile, bei ileile ya kulipa-kwa-mafanikio kwa zote tatu. Mwongozo wa hatua kwa hatua unapatikana kwenye docs.didit.me/integration/integration-prompt.

Husika

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