Skip to main content
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
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

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.

  1. Hatua 01

    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.

  2. Hatua 02

    Unganisha

    Pachika kiasili na SDK yetu ya Web, iOS, Android, React Native, au Flutter. 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. Mtumiaji anapoendelea na mchakato, tunachunguza ishara 200+ za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vinavyoaminika. Matokeo yanapatikana chini ya sekunde mbili.

  4. Hatua 04

    Unapokea matokeo

    Webhooks zilizotiwa saini kwa wakati halisi huweka database yako sawa pindi tu mtumiaji anapoidhinishwa, kukataliwa, au kupelekwa kwa ukaguzi. Uliza API inapohitajika. Au fungua console kukagua kila session, kila ishara, na kudhibiti kesi kwa njia yako.

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{tI18n("webhookTypeStatusUpdatedStatusApproved")}
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
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 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 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
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
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

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 device data does Didit return?
Every session ships back a Device & Session block with device_brand, device_model, browser_family, os_family (operating system), platform (mobile or desktop), and a stable device_fingerprint. The fingerprint persists across cleared cookies and incognito sessions, so the same device coming back under a new identity is matched on the matches array and surfaced as a Duplicated-Device warning. Full reference at docs.didit.me/core-technology/ip-analysis/report-ip-analysis.
What IP data does Didit return?
Every session ships back ip_address, ip_country, ip_country_code (International Organization for Standardization 3166-1 alpha-2), ip_state, ip_city, latitude, longitude, isp (internet service provider), organization, time_zone, and time_zone_offset. The raw IP, the resolved location, and the network operator all sit on the same object, so you can build maps, audit logs, and risk dashboards from one source of truth.
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 does Didit detect Duplicated Device and Duplicated IP?
On every session, Didit looks across every other session in the same application and matches on two keys: ip_address and device_fingerprint. When a match is found on a session belonging to a different `vendor_data` user, the rule fires, Duplicated IP for IP matches, Duplicated Device for fingerprint matches. Each match lands on the ip_analysis.matches array with the matching session_id, session_number, vendor_data, match_type, matched_value, plus device_info and location_info blocks. Always pass vendor_data (your user identifier) on session create, without it, every session is treated as a unique user and duplicate noise rises sharply.
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.

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