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

Chunguza malipo yenye hatari kubwa katika hatua mbili. Ishara za bei nafuu kwanza. Biometriska tu inapohitajika.

Pima mtandao na kifaa kwenye kila gari la ununuzi lenye hatari kubwa kwa $0.03. Ongeza ukaguzi wa biometriska kwenye sehemu ndogo ambapo ishara pekee hazitoshi. Uthibitishaji 500 bure kila mwezi.

Inaungwa mkono na
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

Inaaminika na mashirika 2,000+ duniani kote.

Mrundiko wa giza usioeleweka wa skrini ya kuzuia ulaghai wa wanunuzi, paneli nne zinazoelea, zisizo na uwazi za kioo cheusi katika mtazamo wa 3D kwenye rangi nyeusi safi, zikipitishwa na mstari wima wa Didit Blue unaong'aa na kuwekewa fremu na mabano ya skana yanayong'aa. Kila paneli ina motifu ndogo, nyeupe-nyeupe isiyo dhahiri (kikapu cha ununuzi chenye ngao, ramani ya dunia yenye alama mbili, simu mahiri yenye arcs za mawimbi, kitelezi cha hatari).

Kwa nini malipo mengi hayahitaji usumbufu

Haina usumbufu kwa wanunuzi wanaoaminika. Huamua kwa haraka.

90% ya oda ni za wanunuzi wa kila siku wanaotumia vifaa vya kuaminika, wanapaswa kupita bila shida. Asilimia 10 zenye hatari kubwa hupitia skrini: $0.03 IP + kifaa kwa kesi za bei nafuu, $0.10 hatua ya ziada ya biometriska kwa zile za thamani kubwa. Uthibitishaji 500 bure kila mwezi.

Jinsi inavyofanya kazi

Kuanzia kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.

  1. Hatua 01

    Unda mtiririko wa kazi

    Chagua ukaguzi unaotaka, ID, liveness, face match, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko katika dashibodi, au tuma mtiririko huo huo kwenye API yetu. Gawanya kwa masharti, fanya majaribio ya A/B, hakuna code inayohitajika.

  2. Hatua 02

    Unganisha

    Pachika asili na SDK yetu ya Web, iOS, Android, React Native, au Flutter. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu kiungo kwa mtumiaji wako, kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa stack yako.

  3. Hatua 03

    Mtumiaji anapitia mtiririko

    Didit inasimamia kamera, ishara za mwanga, uhamishaji wa simu, na ufikiaji. Wakati mtumiaji yuko kwenye mtiririko, tunapima ishara 200+ za ulaghai kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya kuaminika. 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 kwa njia yako.

Imeundwa kwa ajili ya malipo · Bei kama miundombinu

Hatua mbili. $0.03 kwa kesi za bei nafuu. $0.13 kwa zile za thamani kubwa.

Skrini ya kuzuia ulaghai wa wanunuzi ni mchanganyiko, vichochezi vya gari, ishara za mtandao, hatua ya ziada ya biometriska, kifurushi cha ukaguzi, uaminifu wa mnunuzi anayerudi. Washa kila moja kwa kila mtiririko wa kazi katika Workflow Builder.
01 · Vichochezi vya malipo

Wewe unachagua wakati. Didit inafanya ukaguzi.

Jumla ya gari juu ya kiwango chako. Mrundikano wa kadi za zawadi tatu au zaidi. Nchi ya usafirishaji isiyolingana na kadi ya malipo. Ununuzi wa kwanza kutoka kifaa kipya. Hitilafu ya kasi, oda N ndani ya dirisha W. Malipo / marudisho ya pesa yamebadilishwa katikati ya mtiririko. Zote zinaweza kuhaririwa katika Workflow Builder isiyo na code.
Moduli ya Workflow Orchestrator
02 · Skrini ya bei nafuu ya IP + kifaa

Ishara kwanza. Rahisi. Maamuzi.

Uchambuzi wa Kifaa & IP unarudisha alama ya hatari ya 0–100 pamoja na bendera za Virtual Private Network (VPN), Tor, datacenter, nchi, Autonomous System Number (ASN), na alama za kidole za kifaa. $0.03 kwa kila simu, chini ya 100ms. Uamuzi wa haraka kwa kesi zilizo wazi, zimekataliwa au kuidhinishwa papo hapo, hakuna kamera inayohitajika.
Moduli ya Device & IP Analysis
03 · Hatua ya ziada ya biometriska

Ukaguzi wa uso pale ishara hazitoshi.

Pandisha hadi Passive Liveness ($0.10) pamoja na hiari ya 1:1 face match dhidi ya picha ya mnunuzi iliyohifadhiwa ($0.05) kwenye magari yenye thamani kubwa. Imethibitishwa na iBeta Level 1 Presentation Attack Detection (PAD). Uamuzi chini ya sekunde mbili. Ukaguzi wa uso wakati wa malipo hauwezi kutatuliwa na kadi iliyoibiwa.
Moduli ya Biometric Authentication
04 · Kifurushi cha ushahidi wa chargeback

Kifurushi cha ukaguzi kwa kila mzozo.

Payload ya uamuzi ni faili ya kesi ya chargeback, uamuzi wa biometriska, alama ya IP, alama ya kidole ya kifaa, nchi, Autonomous System Number (ASN), historia ya oda za awali. Inaendana vizuri na 3-D Secure 2.x liability shift kwenye kadi za EU na kiwango cha Visa Compelling Evidence 3.0 (CE3.0) cha mteja anayeaminika.
Rejea ya Webhook
05 · Uaminifu unaoweza kutumika tena kwa wanunuzi wanaorudi

Wanunuzi wanaoaminika wanaorudi wanaruka usumbufu.

Mara tu mnunuzi anapopitisha utambulisho mara moja kwenye jukwaa, kitambulisho kinaweza kutumika tena kwenye malipo ya baadaye bila gharama kupitia Reusable KYC. Tafuta session_id ya awali ya mnunuzi; ikiwa kitambulisho ni halali na cha hivi karibuni, ruka skrini ya moja kwa moja. Bure milele.
Moduli ya Reusable KYC
06 · Webhook pipeline + hatua ya gari

Uamuzi uliotiwa saini. Kitendo cha gari kimeunganishwa.

Webhook iliyotiwa saini inatua na Imeidhinishwa, Inakaguliwa, au Imekataliwa. Thibitisha X-Signature-V2 na Hash-based Message Authentication Code (HMAC) SHA-256. Oda iliyoidhinishwa inatumwa. Inakaguliwa inashikilia kwa ukaguzi wa mwongozo na ishara za moduli kama faili ya kesi ya ufunguzi. Imekataliwa inaghairi na kurejesha pesa.
Marejeleo ya Webhook
Unganisha

Session moja. Hatua mbili. Uamuzi mmoja uliotiwa saini.

Fungua skrini dhidi ya mtiririko wa kazi wa skrini ya mnunuzi. Soma uamuzi uliotiwa saini. Tuma, shikilia, au ghairi.
POST /v3/session/Ukaguzi wa mnunuzi
$ 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_buyer_screen",
    "vendor_data": "order-A4421",
    "metadata": { "cart_total_cents": 78500 }
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
Shikilia agizo hadi webhook itue status: Approved.nyaraka →
POST /webhooks/diditUamuzi
// X-Signature-V2 verified upstream
if (payload.status === "Imeidhinishwa") {
  shipOrder(payload.vendor_data);
} vinginevyo ikiwa (payload.status === "Imekataliwa") {
  cancelAndRefund(payload.vendor_data);
}
200Sawahali Imeidhinishwa · Imekataliwa · Inakaguliwa · Haijakamilika
Thibitisha X-Signature-V2 kabla ya kusoma payload.nyaraka →
Ujumuishaji tayari kwa agent

Anzisha ukaguzi wa udanganyifu wa mnunuzi kwa amri moja.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent inaunganisha vichochezi vya gari, inafanya ukaguzi wa hatua mbili, inathibitisha webhook, na inasafirisha au inazuia agizo.
didit-integration-prompt.md
You are integrating a Didit buyer-side fraud screen on a marketplace / e-commerce checkout. Goal: catch stolen-card use, account takeover, gift-card stack abuse, geo-mismatch friendly fraud, and bot scalping on high-value carts. Two stages — cheap signals first, biometric step-up only when signals aren't enough.

WHY THIS SHAPE
  - Most checkouts don't need any friction. Day-to-day buyers on trusted devices from residential networks should sail through.
  - A small percentage are high-value or high-risk — cart over a threshold, gift-card stack, payout to a new card, geo mismatch, new device, velocity anomaly. On those, run a screen.
  - Two stages keep the cost and the friction proportional to the risk. Cheap IP + device check ($0.03) is decisive on the obvious cases. Biometric step-up ($0.10) only fires when the cheap signals are inconclusive AND the order is high-value.
  - 500 verifications free every month. The screen runs inside the free tier for most teams while they tune the thresholds.

PRE-REQUISITES
  - Production API key from https://business.didit.me (sandbox key in 60 seconds, no credit card).
  - A webhook endpoint with HMAC SHA-256 verification of the X-Signature-V2 header using your webhook secret.
  - A Workflow Builder workflow with Device & IP Analysis and optionally Passive Liveness + Face Match 1:1 against the stored buyer portrait.
  - A server-side cart-gate that defaults to BLOCK on the high-risk path and only unblocks on a verified webhook with status: Approved.

STEP 1 — Decide WHEN to screen (your code, not Didit's)
  Run your usual checkout signals. Default triggers worth a screen:
    - Cart total above your account-level tier (e.g. > $500)
    - Gift-card stack of three or more cards in one order
    - Shipping country that doesn't match the billing-card country
    - First buy from a new device
    - Velocity anomaly — N orders within window W from the same buyer
    - Payout / refund destination changed mid-flow

  Day-to-day reads from trusted-device + residential-network buyers do NOT need a screen.

STEP 2 — Open the screen session
  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<wf id with Device & IP Analysis + optional Passive Liveness + Face Match 1:1>",
      "vendor_data": "<your order id, max 256 chars>",
      "callback": "https://<your-app>/checkout/screen/callback",
      "metadata": {
        "cart_total_cents": 78500,
        "currency": "EUR",
        "trigger": "high_value_cart"
      }
    }

  Response: 201 Created with a hosted session URL. Show inline at checkout (web), or open in a Software Development Kit (SDK) webview (mobile). The order stays in HOLD on your side until the signed webhook lands.

STEP 3 — Read the signed webhook
  Didit POSTs the verdict. Verify X-Signature-V2 (HMAC SHA-256 of the raw body) BEFORE reading the JSON.

  Payload (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your order id>",
      "status": "Approved",
      "ip_analysis": { "status": "Approved", "score": 11 },
      "liveness":    { "status": "Approved" },
      "face":        { "status": "Approved", "similarity_score": 0.93 }
    }

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

STEP 4 — Branch the cart action
  Approved      → ship the order, capture the auth, send the confirmation.
  In Review     → hold the order. Route to manual review with the per-module signals as the case file.
  Declined      → cancel the order, refund the auth, log warnings (liveness / face-match / ip flags), throttle the source IP.
  Not Finished  → invite the buyer to retry the screen with a fresh session URL. Don't ship.

STEP 5 — (Optional) Reusable Know Your Customer (KYC) for returning trusted buyers
  Once a buyer has passed identity once on the platform, the credential can replay on future checkouts at no cost via Reusable KYC. Look up the buyer's prior session_id; if the credential is valid and recent, skip the live screen.

  That keeps the friction on the unknown traffic only. Free forever.

STEP 6 — Use the decision payload as the chargeback evidence pack
  When a dispute lands, pull the full decision payload via:
    GET https://verification.didit.me/v3/session/{session_id}/decision/
    Headers:
      x-api-key: <your api key>

  Pairs naturally with:
    - 3-D Secure 2.x (3DS2) liability shift on EU cards
    - Visa Compelling Evidence 3.0 (CE3.0) — biometric + IP + device fingerprint + prior-order history meets the "trusted customer" bar
    - Mastercard Identity Check chargeback dispute kit

WEBHOOK EVENT NAMES
  - Sessions: standard session webhook. One endpoint, status field tells you the lifecycle.
  - Verify X-Signature-V2 (HMAC SHA-256) on every payload.

WHAT IT BLOCKS
  - Stolen-card use on first-time-buy + geo mismatch
  - Account takeover on a previously-verified buyer (the step-up is the second-factor)
  - Friendly fraud where the cardholder disputes a charge they actually authorised
  - Bot scalpers running multi-item carts from datacenter Internet Protocol (IP) addresses
  - Gift-card stack drains funded by a stolen card
  - Reshipper / mule patterns (ship-to address inconsistent with prior orders)

CONSTRAINTS
  - Session statuses use Title Case With Spaces. Never UPPER_SNAKE_CASE — that's the Transactions API.
  - Start with IP-only on the cheap cases. Add the biometric step-up only on high-value carts or when IP alone is inconclusive — keeps cost down and friction proportional.
  - 200+ fraud signals are evaluated on every session at no extra cost — read them off the decision payload, don't re-query.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/core-technology/ip-analysis/overview
  - https://docs.didit.me/core-technology/biometric-auth/overview
  - https://docs.didit.me/core-technology/reusable-kyc/overview
  - https://docs.didit.me/integration/webhooks

Start free at https://business.didit.me — sandbox key in 60 seconds, 500 verifications free every month, no credit card.
Unahitaji maelezo zaidi? Tazama nyaraka kamili za moduli.docs.didit.me →
Inatii kwa muundo

Fungua nchi mpya kwa kubofya mara moja. Tunafanya kazi ngumu.

Tunafungua kampuni tanzu za ndani, tunapata leseni, tunafanya majaribio ya kupenya, tunapata vyeti, na tunalingana na kila kanuni mpya. Ili kusafirisha uthibitishaji katika nchi mpya, geuza swichi. Nchi 220+ ziko hewani, zinakaguliwa na kupimwa kila robo mwaka, mtoa huduma pekee wa utambulisho ambaye serikali ya nchi mwanachama wa EU imemwita rasmi kuwa salama zaidi kuliko uthibitishaji wa ana kwa ana.
Soma faili ya usalama na utiifu
EU financial sandbox
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
Usalama wa habari · 2026
SOC 2 · Type I
AICPA · 2026
iBeta Level 1 PAD
NIST / NIAP · 2026
GDPR
EU 2016/679
DORA
EU 2022/2554
MiCA
EU 2023/1114
AMLD6 · eIDAS 2.0
EU-aligned kwa muundo

Takwimu za kuthibitisha

Namba za uthibitisho
  • $0.00
    Kila uchambuzi wa Kifaa & IP kwa kesi rahisi, huamua zile zilizo wazi.
  • $0.00
    Kila tukio la ununuzi wa thamani ya juu na hatua ya kibayometriki, $0.10 kwa hatua + $0.03 kwa IP.
  • <0s
    Uamuzi wa hatua-juu mwisho-hadi-mwisho kwenye Android ya kiwango cha chini.
  • 0
    Uthibitishaji wa bure kila mwezi, kwenye kila akaunti.
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 is buyer fraud on a marketplace?

Any pattern where the person paying does not have the right to pay with that instrument, or where the transaction is structured to trigger a later chargeback.

Common shapes:

  • Stolen-card use, a fresh card-not-present buy from a new device on a country-mismatch ship-to
  • Account takeover, an attacker uses a hijacked logged-in account to buy and ship to themselves
  • Friendly fraud, the cardholder authorised the purchase, received the goods, then disputes the charge
  • Gift-card stack abuse, stolen card funds a stack of digital gift cards that are immediately drained
  • Bot scalpers, automated checkout farms buying limited-supply items at scale
Why two stages instead of one universal screen?

Friction has a cost. Conversion drops measurably on every extra checkout step. Most buyers, known device, residential network, normal cart total, should sail through with no screen at all.

Two stages keep the friction proportional to the risk:

  • Stage 1 ($0.03), Device & IP Analysis is cheap and silent. Decisive on the obvious cases (VPN + datacenter Internet Protocol (IP) + headless browser = block on the spot; trusted device + residential ISP = pass on the spot).
  • Stage 2 ($0.10), Passive Liveness step-up fires only on the small slice where stage 1 is inconclusive AND the cart total is above the worth-it threshold.

The result: the median checkout adds zero friction, and the high-risk slice gets a decisive check.

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.

When does the biometric step-up fire?

Only when stage 1 is inconclusive AND the order is high-value enough to justify the friction. Examples:

  • IP score is in the grey zone (say 40–70) but cart is above \$500
  • Cart includes a high-resale digital good (gift card stack, electronics, luxury) on a new device
  • Buyer is paying out to a card seen for the first time on a returning account
  • Velocity-rule trip on an established buyer

The step-up is Passive Liveness at \$0.10, optionally with a Face Match 1:1 against the stored buyer portrait at an extra \$0.05. Sub-two-second verdict on entry-level Android.

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.

Does this work on mobile and web?

Yes. The same POST /v3/session/ powers both. On web, render the returned session_url inline at checkout. On mobile, open it in the Didit Software Development Kit (SDK) webview, five SDKs ship: Web, iOS, Android, React Native, Flutter, all free.

The verdict comes through the same signed webhook regardless of surface. One integration, every platform.

What does the recipe cost?

Two line items in the worst case:

  • Device & IP Analysis check: \$0.03 per call (cheap stage)
  • Passive Liveness step-up: \$0.10 per session (only on the high-value cases)
  • Face Match 1:1 against stored portrait (optional): \$0.05 per match

Median protected checkout that needs both stages: ~\$0.13. Most checkouts run only stage 1 at \$0.03. Returning trusted buyers via Reusable KYC are free forever.

The first 500 verifications every month are free on every account.

Which industries run this recipe?

Anywhere the basket is big enough that a stolen-card buy hurts:

  • High-AOV marketplaces, electronics, luxury, art, second-hand goods over \$500
  • Digital-good resellers, gift cards, in-game items, software licences
  • Ticketing, sports, concerts, travel, where scalping bots cluster
  • Subscription commerce, high-tier subscription boxes, premium SaaS plans
  • Cross-border e-commerce, geo-mismatch shipping is the universal red flag
  • Pharmacy / regulated products, age + identity + chargeback all matter together

One workflow, every cart shape.

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