Ruka hadi maudhui makuu
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Uchambuzi wa Kifaa & IP

Jua kifaa.
Jua IP. Kwenye kila kipindi.

Alama ya kidole ya kifaa, chapa, mfumo, kivinjari, mfumo wa uendeshaji (OS), jukwaa, zinanasa pamoja na IP, eneo la kijiografia, Virtual Private Network (VPN) / proxy / Tor, bendera ya kituo cha data, na sheria za Duplicated-Device + Duplicated-IP. Hitimisho moja. $0.03 kwa kila ukaguzi, imejumuishwa kwenye KYC kamili ya $0.33 (mjue mteja wako). 500 bila malipo kila mwezi.

Inaungwa mkono na
Y CombinatorRobinhood Ventures
Firecrawl
Slash
Crnogorski Telekom
UCSF Neuroscape
Bit2Me

Inaaminika na mashirika 2,000+ duniani kote.

Didit Uchambuzi wa Kifaa & IP, Kadi ya hatari ya IP imechanganuliwa na topolojia ya mtandao na viwekeleo vya eneo la kijiografia.

Ishara 200+ za udanganyifu

Device fingerprint. IP intelligence.
Utoaji wa hitimisho mmoja wa $0.03.

Kila kipindi kinarudisha chapa ya kifaa, mfumo, familia ya kivinjari, mfumo wa uendeshaji, jukwaa, na alama ya kidole ya kifaa thabiti, ikiambatana na eneo kamili la kijiografia la IP, mwendeshaji wa mtandao, bendera ya Virtual Private Network (VPN) / proxy / Tor, bendera ya kituo cha data, na sheria za Duplicated-Device + Duplicated-IP. Simu moja, ishara 200+, p99 chini ya sekunde 2.

Jinsi inavyofanya kazi

Kuanzia kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.

Hatua 01 / 04

Unda mtiririko wa kazi

Chagua ukaguzi unaotaka, Kitambulisho, uhai, ulinganishaji wa nyuso, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko kwenye dashibodi, au tuma mtiririko huo huo kwenye API yetu. Gawanya kwa masharti, fanya majaribio ya A/B, hakuna msimbo unaohitajika.

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

Uwezo sita. Feature flag moja. IP_ANALYSIS.

Kila uwezo hapa chini ni swichi kwenye moduli moja. Hakuna viwango vya kuongeza mauzo, hakuna SKUs tofauti, hakuna simu za nyongeza. Viwashe kwa kila workflow, au jumuisha kipengele cha IP_ANALYSIS unapoanzisha workflow.
01 · Alama za kidole za kifaa + kivinjari, OS, jukwaa

Kitambulisho kimoja cha kifaa kinachodumu hata baada ya kivinjari kufutwa.

Kila session inarudisha chapa ya kifaa, mfumo wa kifaa, familia ya kivinjari, familia ya mfumo wa uendeshaji (OS), jukwaa (simu au kompyuta), na alama za kidole za kifaa zisizobadilika. Alama za kidole hudumu hata baada ya kufuta cookies na sessions za incognito, hivyo kifaa kilekile kinaporudi na utambulisho mpya kinalinganishwa kwenye `matches` array na kuonyeshwa kama onyo la Duplicated-Device.
02 · IP geolocation + mtoa huduma wa mtandao

IP inasema Madrid. ID inasema Madrid. Session inapita.

Kila IP inabainisha nchi, msimbo wa nchi (International Organization for Standardization 3166-1 alpha-2), mkoa, jiji, latitudo, longitudo, mtoa huduma wa intaneti (ISP), na shirika. Pia tunarudisha umbali kwa kilomita kati ya IP, anwani ya hati ya utambulisho (ID), na hati yoyote ya uthibitisho wa anwani, kutolingana kwa Nchi kunasababisha onyo linaloweza kusanidiwa ambalo unaweza kuelekeza kwa ukaguzi wa mikono.
03 · Virtual Private Network (VPN), proxy, Tor

Nasa kinyago. Kila muunganisho, kila session.

Ishara za akili za vyanzo vingi huashiria Virtual Private Network (VPN), proxy, na The Onion Router (Tor) exit nodes pindi tu muunganisho uliofichwa unapotua. Rekebisha hatua kwa kila workflow, kataa kwa onboarding ya thamani kubwa, elekeza kwa ukaguzi kwa maeneo yenye utata, idhinisha kwa watumiaji wa crypto ambao hutumia VPN kwa mazoea.
04 · Kugundua hosting na datacenter

Watumiaji halisi wanaishi majumbani. Bots wanaishi kwenye datacenters.

Kila IP inaboreshwa na mtoa huduma wa mtandao na shirika. Ishara ya datacenter inawaka kwa miunganisho inayotoka Amazon Web Services (AWS), Hetzner, DigitalOcean, OVH, na kila mtoa huduma mwingine wa hosting, otomatiki ileile ya saini, scrapers, na mashamba ya usajili wa wingi huacha. Zichuje bila kugusa trafiki ya makazi.
05 · Sheria tano. Vitendo vitatu. Kwa kila programu.

Console moja. Idhinisha, Kagua, au Kataa.

Kila sheria inayoweza kusanidiwa, IP mismatch, Virtual Private Network (VPN) / proxy / Tor, Expected-IP mismatch, Duplicated IP, Duplicated Device, inalingana na Approve / Review / Decline kwenye console. Rekebisha sera kwa kila programu, soko, na workflow. Duplicated-Device + Duplicated-IP huwekwa chaguomsingi kuwa Approve, ziwashe kwa masoko na iGaming, ambapo mtu yuleyule chini ya vitambulisho vingi ndio tishio kuu.
06 · Inajitegemea au imefungwa pamoja

$0.03 alone. Free inside the $0.33 full KYC.

Endesha Uchambuzi wa Kifaa & IP kama nyongeza ya session kwa $0.03 kwa kila ukaguzi ikiwa hiyo ndiyo ishara pekee unayohitaji. Au iunganishe kwenye workflow kamili ya KYC (know your customer) ya $0.33, Uthibitishaji wa Utambulisho (ID), Passive Liveness, Face Match 1:1, Uchambuzi wa Kifaa & IP, imejumuishwa kwa bei ya kifurushi. Uthibitishaji 500 bila malipo kila mwezi, kwenye kila akaunti, milele.
Unganisha

Endpoint moja. JSON ileile. Bei ileile.

Uchambuzi wa Kifaa & IP unafanya kazi ndani ya session ya Didit, hakuna API tofauti inayojitegemea. UI iliyopangishwa inakamata alama za kidole za kifaa, chapa, mfumo, kivinjari, mfumo wa uendeshaji (OS), jukwaa, na anwani ya IP kiotomatiki, hakuna Software Development Kit (SDK) ya upande wa mteja, hakuna ombi la ruhusa. Bainisha IP inayotarajiwa unapoijua tayari mtumiaji anapaswa kutoka wapi.
POST /v3/session/Kukamata kiotomatiki
$ 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_ip_only",
    "vendor_data": "user-42"
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
Didit inakamata ip_address na device_fingerprint kwenye upakiaji wa UI iliyopangishwa.nyaraka →
POST /webhooks/diditHatua ya 2 · Pokea
// Your endpoint receives a signed payload
app.post("/webhooks/didit", (req, res) => {
  const sig = req.headers["x-signature-v2"];
  const expected = crypto.createHmac("sha256", SECRET)
    .update(req.rawBody).digest("hex");
  if (sig !== expected) return res.sendStatus(401);
  const { status, decision, vendor_data } = req.body;
  // status: Approved | Declined | In Review | ...
  res.sendStatus(200);
});
200Sawa{ webhook_type: "status.updated", status: "Approved" }
Webhook ya HMAC-signed ya muda halisi. Thibitisha, chambua, sasisha database yako.nyaraka →
Ujumuishaji tayari kwa agent

Weka Device & IP Analysis 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 kuweka sokoni.
didit-integration-prompt.md
# Didit Device & IP Analysis — integrate in 5 minutes

You are integrating Didit's Device & IP Analysis (VPN, datacenter, Tor, geolocation,
device intelligence) 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. Integration path — Workflow Builder (session-only)

Device & IP Analysis runs inside a Didit session — there is no standalone
POST /v3/ip-analysis/ endpoint. The IP and device fingerprint are
captured automatically when the user lands on the hosted UI, so you
do not collect or send them yourself.

1. Create a workflow that includes the IP_ANALYSIS feature:
   POST https://verification.didit.me/v3/workflows/
   Authorization header:  x-api-key: <your-api-key>
   Body: workflow_label, features array including
         { feature: "IP_ANALYSIS" }   (UPPERCASE — strict enum)
   Combine with ID_VERIFICATION, LIVENESS, FACE_MATCH in the same
   workflow for the full $0.33 Know Your Customer (KYC) bundle (Device & IP Analysis is included).

2. (Optional) Configure per-warning actions in the console for the
   application — pick Decline, Review, or Approve for each of
   PRIVATE_NETWORK_DETECTED, COUNTRY_FROM_DOCUMENT_DOES_NOT_MATCH_COUNTRY_FROM_IP,
   EXPECTED_IP_ADDRESS_MISMATCH, DUPLICATED_IP_ADDRESS,
   DUPLICATED_DEVICE_FINGERPRINT.

3. (Optional) Pin an expected IP per session: pass expected_ip_address
   in the POST /v3/session/ body if you already know where the user
   should be (for example: their last known login IP).

4. 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),
         optional expected_ip_address.
   Response: session_url — redirect the user to it.

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

## 3. Webhooks
- 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
The session decision payload contains an ip_analysis object with:
- status: "Approved" | "Declined" | "In Review" | "Not Finished"
- ip_address, ip_country, ip_country_code, ip_state, ip_city
- latitude, longitude, time_zone, time_zone_offset
- isp, organization
- is_vpn_or_tor (boolean) — fires the PRIVATE_NETWORK_DETECTED warning
- is_data_center (boolean) — hosting/datacenter origin
- device_brand, device_model, browser_family, os_family, platform
  (mobile or desktop)
- locations_info with ip, id_document, poa_document blocks — each
  carries a location object plus distance_from_* fields in kilometres
- matches array — cross-session matches on ip_address or
  device_fingerprint when the same value appears under a different
  vendor_data
- warnings array — each entry has risk, log_type,
  short_description, long_description

Auto-decline risks (always enforced by Didit, not configurable):
- IP_ADDRESS_IN_BLOCKLIST
- DEVICE_FINGERPRINT_IN_BLOCKLIST

Configurable risks (action per workflow — Decline, Review, or Approve):
- PRIVATE_NETWORK_DETECTED (VPN, proxy, Tor)
- COUNTRY_FROM_DOCUMENT_DOES_NOT_MATCH_COUNTRY_FROM_IP
- EXPECTED_IP_ADDRESS_MISMATCH
- DUPLICATED_IP_ADDRESS (default: Approve)
- DUPLICATED_DEVICE_FINGERPRINT (default: Approve)

## 5. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: IP_ANALYSIS, ID_VERIFICATION, LIVENESS, FACE_MATCH, AML.
- 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).
- Always pass vendor_data (your own user id). Without it, every session
  is treated as a unique user and DUPLICATED_IP_ADDRESS /
  DUPLICATED_DEVICE_FINGERPRINT noise rises sharply.

## 6. Pricing reference (public)
- IP_ANALYSIS as a session add-on: $0.03 per check
- Bundled in a full KYC workflow (ID_VERIFICATION + LIVENESS +
  FACE_MATCH + IP_ANALYSIS): $0.33 per session — Device & IP Analysis is
  already included at the bundle price.
- 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 IPs: deterministic synthetic responses returned in sandbox (Approved
  by default; trigger PRIVATE_NETWORK_DETECTED by using a known VPN exit IP
  on the verification device).
- Switch to live: flip the application's environment toggle in console.

When in doubt: https://docs.didit.me/core-technology/ip-analysis/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
SOC 2 · Type II — AICPA · 2026
SOC 2 · Type I — AICPA · 2026
ISO/IEC 27001 — Usalama wa habari · 2026
EU financial sandbox — Tesoro · SEPBLAC · BdE
FIDO Alliance — Mwanachama Mshirika · 2026
iBeta Level 1 PAD — NIST / NIAP · 2026
GDPR — EU 2016/679
HIPAA — 45 CFR §160 · §164
DORA — EU 2022/2554
MiCA — EU 2023/1114
Miongozo ya EBA ya kuingiza wateja mtandaoni — EBA/GL/2022/15
AMLD6 · eIDAS 2.0 — EU-aligned kwa muundo
Jugendschutz geprüft — FSM · JMStV §4(2) · 2026

Namba za uthibitisho

Namba za uthibitisho
  • $0.00
    Kila ukaguzi wa Device & IP Analysis kwenye session.
  • 0+
    Ishara za udanganyifu za Device + IP zilizopimwa kwenye kila session.
  • <0s
    Utoaji wa hitimisho wa p99 wa mwisho-hadi-mwisho kwa kila session.
  • 0
    Uthibitishaji wa bure kila mwezi. Milele.
Ngazi tatu, orodha moja ya bei

Anza bure. Lipa kadri unavyotumia. Kuza hadi Enterprise.

Uthibitishaji 500 bila malipo kila mwezi, milele. Kisha lipa tu moduli inapofanya kazi. Mikataba maalum, uhifadhi wa data, na makubaliano ya kiwango cha huduma (SLAs) kwenye Enterprise.

Bure

$0/ mwezi · hakuna kadi

Kwa ajili ya kuunda, kujaribu, na watumiaji wako wa kwanza.

Kila kitu unachohitaji kuanzia:
  • Uthibitishaji kamili wa KYC 500 kila mwezi
  • Kitambulisho, uhai, kulinganisha uso, kifaa & IP
  • Ishara za udanganyifu 200+, orodha nyeusi, marudio
  • KYC inayoweza kutumika tena kwenye mtandao wa Didit
  • Mjenzi wa mtiririko wa kazi, usimamizi wa kesi, SDKs
  • Usaidizi wa AI AI agent ndani ya console, docs, na jumuiya.
Maarufu zaidi

Lipa kadri unavyotumia

$0.33kwa KYC kamili

Moduli 25+, bei wazi. Punguzo la kiotomatiki kwa wingi.

Kila kitu kilichopo kwenye Bure, pamoja na:
  • Uchunguzi na ufuatiliaji wa AML kuanzia $0.07
  • Uthibitishaji wa biashara kwa $2.00 kwa kampuni
  • Ufuatiliaji wa miamala kwa $0.02 kila moja
  • Uchunguzi wa pochi kwa $0.15 kwa kila ukaguzi
  • Mtiririko wa white-label chini ya chapa yako mwenyewe
  • Usaidizi wa AI AI agent ndani ya console, docs, na jumuiya.

Enterprise

Maalummkataba wa mwaka

Kwa kiasi kikubwa na programu zilizodhibitiwa.

Kila kitu kilichopo kwenye Lipa kadri unavyotumia, pamoja na:
  • Mikataba ya kila mwaka, bei ya kiasi kilichokubaliwa
  • Masharti maalum ya kisheria na SLA ya 99.99% ya muda wa kufanya kazi
  • Uhifadhi wa data, uhifadhi, ukaguzi wa usalama
  • Wakaguzi wa mikono kwa mahitaji
  • Masharti ya muuzaji na white-label
  • Usaidizi wa kipaumbele kutoka kwa binadamu Kituo cha Slack kinachoshirikiwa saa 24/7, meneja maalum wa mafanikio.

Punguzo la wingi hutumika kiotomatiki kadri matumizi yanavyoongezeka — hakuna mazungumzo, hakuna simu ya mauzo.

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 kipindi
  • Inaaminika, inatumika na kampuni 2,000+ katika nchi 220+
  • Salama, SOC 2 Aina ya 1 & Aina ya 2, ISO 27001, GDPR-native, na kuthibitishwa rasmi na mdhibiti wa kifedha wa Uhispania kuwa salama zaidi kuliko kumthibitisha mtu ana kwa ana

Alama ya miguu chini: aina 14,000+ za hati katika lugha 48+, vyanzo vya data 1,000+, na ishara za udanganyifu 200+ kwenye kila kipindi. Miundombinu ya Didit hujifunza kwa nguvu kutoka kila kipindi na inakuwa bora kila siku.

Didit inarudisha data gani ya kifaa?
Kila kipindi kinarudisha block ya Kifaa & Kipindi na device_brand, device_model, browser_family, os_family (mfumo wa uendeshaji), platform (simu au kompyuta), na device_fingerprint thabiti. Fingerprint hudumu hata baada ya cookies kufutwa na vipindi vya incognito, kwa hivyo kifaa kilekile kinaporudi chini ya utambulisho mpya, kinalinganishwa kwenye array ya matches na kuonyeshwa kama onyo la Kifaa Kilichorudiwa. Marejeleo kamili yanapatikana docs.didit.me/core-technology/ip-analysis/report-ip-analysis.
Didit inarudisha data gani ya IP?
Kila kipindi kinarudisha ip_address, ip_country, ip_country_code (Shirika la Kimataifa la Viwango 3166-1 alpha-2), ip_state, ip_city, latitude, longitude, isp (mtoa huduma wa intaneti), organization, time_zone, na time_zone_offset. IP halisi, eneo lililotatuliwa, na mwendeshaji wa mtandao vyote viko kwenye kitu kimoja, kwa hivyo unaweza kujenga ramani, kumbukumbu za ukaguzi, na dashibodi za hatari kutoka chanzo kimoja cha ukweli.
Uthibitishaji ni wa haraka kiasi gani kwa mtumiaji wangu wa mwisho?

Mchakato mzima kwa kawaida huchukua chini ya sekunde 30 kuanzia mwanzo hadi mwisho, chukua kitambulisho, piga picha hati, piga picha selfie, umemaliza. Huu ndio kasi zaidi sokoni. Watoa huduma wa zamani wa KYC kwa kawaida huchukua zaidi ya sekunde 90 kwa mchakato huo huo.

Kwa upande wa nyuma, 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 kompyuta hadi simu kupitia msimbo wa QR ikiwa mtumiaji anaanza kwenye wavuti.

Didit hugundua vipi Kifaa Kilichorudiwa na IP Iliyorudiwa?
Kwenye kila kipindi, Didit huangalia vipindi vingine vyote katika programu hiyo hiyo na kulinganisha kwenye funguo mbili: ip_address na device_fingerprint. Wakati kulinganisha kunapatikana kwenye kipindi kinachomilikiwa na mtumiaji tofauti wa `vendor_data`, sheria inawaka, IP Iliyorudiwa kwa kulinganisha IP, Kifaa Kilichorudiwa kwa kulinganisha fingerprint. Kila kulinganisha huangukia kwenye array ya ip_analysis.matches na session_id inayolingana, session_number, vendor_data, match_type, matched_value, pamoja na blocks za device_info na location_info. Daima pitisha vendor_data (kitambulisho chako cha mtumiaji) kwenye uundaji wa kipindi, bila hiyo, kila kipindi kinachukuliwa kama mtumiaji wa kipekee na kelele za kurudia huongezeka sana.
Nini kinatokea ikiwa mtumiaji atashindwa, kuacha, au muda wake kuisha?

Kila kipindi huangukia kwenye mojawapo ya hali saba zilizo wazi, kwa hivyo msimbo wako unajua nini cha kufanya:

  • Approved, kila ukaguzi umepita. Endelea na mtumiaji.
  • Declined, ukaguzi mmoja au zaidi umeshindwa. Unaweza kumruhusu mtumiaji kutuma tena hatua maalum iliyoshindwa (kwa mfano, piga tena selfie) bila kurudia mchakato 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 mchakato.
  • Not Started, kiungo kimetumwa, mtumiaji bado hajafungua. Tuma ukumbusho ikiwa inakaa muda mrefu sana.
  • Abandoned, mtumiaji alifungua kiungo lakini hakumaliza kwa wakati. Mshirikishe tena au muda wake uishe.
  • Expired, kiungo cha kipindi kimepitwa na wakati. Unda kipindi kipya.

Webhook iliyosainiwa inawaka kwenye kila mabadiliko ya hali, kwa hivyo database yako inabaki sawa. Vipindi vilivyoachwa na vilivyokataliwa ni bure.

Data ya mteja wangu inakaa wapi na inalindwa vipi?

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

Usimbaji fiche kila mahali. AES-256 wakati wa kupumzika kwenye kila database, hifadhi ya vitu, na backup. Usalama wa Tabaka la Usafirishaji 1.3 wakati wa kusafirisha kwenye kila simu ya API, webhook, na kipindi cha Business Console. Data ya kibayometriki imesimbwa kwa njia fiche chini ya Ufunguo Mkuu wa Mteja 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 kipindi chochote cha kibinafsi wakati wowote kutoka kwenye dashibodi au API.

Vyeti: SOC 2 Aina ya 1 & Aina ya 2, ISO/IEC 27001:2022, iBeta Kiwango cha 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 kwenye /security-compliance.

Je, Didit inatii sheria kwa tasnia yangu?

Didit inatii sheria kwa chaguo-msingi kwa wadhibiti muhimu kwa miundombinu ya utambulisho:

  • GDPR + UK GDPR, mgawanyo wa mtawala / mchakataji, Mkataba kamili wa Uchakataji Data ulichapishwa, mamlaka kuu ya usimamizi imetajwa (AEPD ya Uhispania).
  • AMLD6 + EU AML Single Rulebook, vikwazo 1,300+, mtu aliye wazi kisiasa, na orodha za vyombo vya habari hasi zimechunguzwa 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, kubadilishana, na walinzi.
  • 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 kuweka 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 kwa akaunti ya sandbox kwenye business.didit.me, hakuna kadi ya mkopo.
  • Dakika 5 kwa uthibitishaji unaofanya kazi kupitia Claude Code, Cursor, au wakala yeyote wa kuweka msimbo kupitia seva yetu ya Model Context Protocol (MCP).
  • Wikiendi moja kwa muunganisho tayari kwa uzalishaji na uthibitishaji wa webhook uliosainiwa, majaribio tena, na mtiririko wa kurekebisha wakati mtumiaji anakataliwa.

Njia tatu za kuunganisha, chagua inayofaa stack yako:

  • Pachika asili 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 sawa, bili sawa, bei sawa ya kulipa kwa mafanikio kwa zote tatu. Mwongozo wa hatua kwa hatua unapatikana docs.didit.me/integration/integration-prompt.

Miundombinu ya utambulisho na udanganyifu.

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

Uliza AI ifupishe ukurasa huu