Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Uhakiki wa duka huru

Mhakiki mnunuzi mlangoni. Fungua kikapu. Zuia SKU zilizozuiliwa.

$0.33 ziara ya kwanza, $0.10 kila kurudi, uso mlangoni, umri unatekelezwa kwa kila kategoria, hakuna wafanyakazi. Uhakiki 500 bila malipo kila mwezi.

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

Inaaminika na mashirika 2,000+ duniani kote.

Mchoro wa sinema, giza, usioeleweka wa kuingia kwenye duka huru, paneli nne za glasi zinazoelea, zinazopitisha mwanga katika mtazamo wa 3D kwenye nyeusi tupu, zikipitishwa na mstari wa Didit Blue unaong'aa na kuwekewa fremu na mabano manne ya skana yanayong'aa. Kila paneli ina motifu ndogo, nyeupe hafifu, isiyoeleweka inayowakilisha kuingia kwa rejareja huru (mlango wa mlango, mviringo wa uso na mabano, kalenda ya umri, kikapu cha ununuzi).

Maduka ya rejareja yasiyo na wafanyakazi yanadaiwa nini

Hakuna karani. Hakuna wafanyakazi. Bado inatii sheria kila anayeingia.

Maduka ya urahisi yasiyo na wafanyakazi, vibanda vya kuuza bidhaa, friji mahiri, mafuta huru, yote yanadaiwa utiifu sawa na duka lenye wafanyakazi: kitambulisho halisi, umri halisi, rekodi halisi ya ukaguzi. Didit inatoa kama mtiririko mmoja wa kazi: $0.33 ziara ya kwanza, $0.10 kila kurudi, uamuzi wa wastani chini ya sekunde 2, nyaraka 14,000+ katika nchi 220+.

Jinsi inavyofanya kazi

Kutoka 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 tuma mtiririko huo huo kwenye API yetu. Panga 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 taa, uhamishaji wa simu, na ufikiaji. Wakati mtumiaji yuko kwenye mtiririko, tunapima ishara 200+ za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya mamlaka. Matokeo chini ya sekunde mbili.

  4. Hatua 04

    Unapokea matokeo

    Webhooks zilizosainiwa za wakati halisi huweka database yako sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Uliza API inapohitajika. Au fungua console kukagua kila kipindi, kila ishara, na kudhibiti kesi kwa njia yako.

Imejengwa kwa rejareja huru · Bei kama miundombinu

Vipengele sita. $0.33 ziara ya kwanza, $0.10 kila kurudi.

Utiifu wa rejareja huru sio ukaguzi mmoja, ni mapishi. KYC ziara ya kwanza, tambua uso kila kurudi, tekeleza umri kwa kila SKU kwa kila eneo, saini kila jaribio.
Soma nyarakaPata API key
01 · Mtiririko wa kuingia

Changanua, thibitisha, fungua.

Kifurushi cha ziara ya kwanza, Uthibitishaji wa Kitambulisho, Passive Liveness, Face Match 1:1, pamoja na umri uliokokotolewa kutoka tarehe ya kuzaliwa iliyothibitishwa. Imethibitishwa na iBeta Level 1 anti-spoof, hati 14,000+ katika nchi 220+.
Moduli ya Uthibitishaji wa Mtumiaji
02 · Lango la umri

Vizingiti vya umri kwa kila kategoria, kwa kila eneo.

Pombe miaka 18 EU / 21 US, tumbaku kulingana na jimbo, vapes 18 / 21, vinywaji vya kuongeza nguvu miaka 16 katika baadhi ya nchi za EU, zana kali miaka 18, dawa za kuagizwa na daktari zinatolewa na mfamasia. Inatekelezwa upande wa server, kamwe kwenye kiosk.
Suluhisho la Uthibitishaji wa Umri
03 · Mnunuzi anayerudi

Uso mlangoni. Hakuna simu.

Uthibitishaji wa Biometriska kwa $0.10 kwa kila kuingia, mnunuzi anaweka uso wake kwenye kamera ya mlango, mlango unafunguka. Wastani wa sekunde 1.4 kwa saa. Kitambulisho kilekile katika kila duka kwenye mtandao wako.
Uthibitishaji wa Biometriska
04 · Kumbukumbu ya majaribio yaliyotiwa saini

Kila kiingilio kimesainiwa na kuwekwa kumbukumbu.

Timestamp, kitambulisho cha duka, PID ya mnunuzi (Kitambulisho cha Bandia), uamuzi wa umri, X-Signature-V2 HMAC SHA-256, rekodi moja kwa kila jaribio, inaweza kusafirishwa kwenye dashibodi yako ya kuzuia hasara au tovuti ya mdhibiti wa serikali. Uhifadhi wa miaka 5 kama chaguo-msingi.
Nyaraka za Webhooks
05 · Kategoria × eneo · muda

Sheria za ndani bila kusakinisha upya store-OS.

Zuia pombe katika kaunti kavu, zuia mauzo baada ya saa za kazi, hitaji leseni ya serikali kwa SKU za vape, elekeza maagizo ya dawa kwenye backend ya duka la dawa. Hariri kwa kila duka katika Workflow Builder isiyo na code.
Workflow Orchestrator
06 · Mfumo-ikolojia

Unganisha kwenye store-OS, POS, payment stack.

Webhooks zinafika kwenye store-OS yako, POS inazuia SKU zilizozuiliwa wakati wa kuchanganua, mashine za kuuza zenye akili zinafungua nafasi baada tu ya kuangalia umri, dashibodi ya kuzuia hasara inapokea kila jaribio lililotiwa saini.
Moduli ya Face Match 1:1
Unganisha

Kipindi kimoja kwa ziara ya kwanza. Kibayometriki kwa kila kurudi.

Fungua kipindi cha kuingia. Soma uamuzi uliosainiwa. Fungua mlango. Tambua uso kila ziara inayofuata.
POST /v3/session/Ziara ya kwanza
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_store_entry_kyc",
    "vendor_data": "shopper-42",
    "metadata": { "store_id": "store_sf_12" }
  }'
201ImeundwaInarudisha URL ya kipindi kilichopangishwa.
Weka mlango umefungwa hadi webhook iseme status: Approved.nyaraka →
POST /v3/session/Rudisha
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_store_entry_biometric",
    "vendor_data": "shopper-42",
    // base64 first-visit selfie, ≤ 1MB (omit for liveness-only)
    "portrait_image": "/9j/4AAQSkZJRgABAQE..."
  }'
201ImeundwaUthibitishaji wa Biometric kwa $0.10 · mlango unafunguka baada ya ~1.4 s.
API ya Sessions ileile. Ni workflow ya Biometric Auth pekee.nyaraka →
Ujumuishaji tayari kwa agent

Weka mfumo wa kuingia dukani unaojitegemea kwa prompt moja.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent huunda workflows zote mbili, huunganisha webhook ya kidhibiti mlango, na kutekeleza sheria za SKU wakati wa malipo.
didit-integration-prompt.md
You are integrating Didit into an autonomous-retail surface — an unstaffed convenience store, an age-gated vending machine, a smart fridge, an autonomous fuel station, or a self-checkout that handles restricted SKUs. The recipe verifies identity + age at entry and authenticates returning shoppers via face only.

Three pillars:

  1. First visit — verify the shopper's identity and age with one POST /v3/session/ ($0.33 bundle).
  2. Returning visit — Biometric Authentication at $0.10 per entry. Shopper holds their face to the door camera; door unlocks.
  3. Per-SKU enforcement — block restricted categories (alcohol, tobacco, vapes, energy drinks, RX) at scan or checkout based on the verified age and the store's local rules.

Cost:
  - First visit KYC bundle: $0.33 per shopper (Sessions API)
  - Returning visit Biometric Auth: $0.10 per entry
  - First 500 verifications free every month, forever

PRE-REQUISITES
  - Production API key from https://business.didit.me (sandbox key in 60s, no card).
  - Webhook endpoint with HMAC SHA-256 verification using the X-Signature-V2 header and your webhook secret.
  - Two workflows in the Workflow Builder:
      wf_store_entry_kyc      — ID Verification + Passive Liveness + Face Match 1:1 + age rules (first visit)
      wf_store_entry_biometric — Biometric Auth-only (returning visit)
  - A store-id + local-rule lookup so age thresholds vary per region (EU 18 vs US 21 for alcohol; state-by-state tobacco; dry counties; etc.).

STEP 1 — First visit: verify the shopper

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<wf_store_entry_kyc>",
      "vendor_data": "<your shopper id, max 256 chars>",
      "callback": "https://<your-app>/store/entry/callback",
      "metadata": {
        "purpose": "autonomous_store_entry",
        "store_id": "<your store id>",
        "region": "<US-CA | EU-ES | etc.>"
      }
    }

  Response: 201 Created with the hosted session URL. Encode that URL in the QR sticker on the door (or push it to the shopper's phone via SMS / WhatsApp). Sub-2-second median verdict on completion.

STEP 2 — Read the signed webhook on entry-flow completion

  Didit POSTs to your callback. Session statuses are Title Case With Spaces:

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your shopper id>",
      "status": "Approved",
      "id_verification": {
        "status": "Approved",
        "date_of_birth": "1991-04-22",
        "country": "US"
      },
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94 }
    }

  Status enum (exact case): Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned.

  Verify the X-Signature-V2 header BEFORE reading the body — HMAC SHA-256 of the raw bytes with your webhook secret.

  Compute the age from date_of_birth, look up the region's age thresholds (per category), and store the (shopper_id, age_band, region, kyc_status) tuple in your data layer.

STEP 3 — Open the door

  When status is Approved, signal your store-OS / door-controller to unlock. Median wall-clock from QR scan to door open is around 1.4 seconds on entry-level Android, sub-2 seconds end to end.

  Failure modes to handle:
    Declined / In Review / Resubmitted — show a friendly UI on the kiosk and offer staff hand-off.
    Expired / Abandoned — shopper walked away; do nothing, the session expires.

STEP 4 — Returning visit: Biometric Authentication

  POST https://verification.didit.me/v3/session/
  Body:
    {
      "workflow_id": "<wf_store_entry_biometric>",
      "vendor_data": "<your shopper id>",
      "metadata": {
        "purpose": "autonomous_store_entry_return",
        "store_id": "<your store id>"
      }
    }

  The shopper just holds their face to the door camera. Cost is $0.10 per entry. Same webhook flow.

STEP 5 — Read the decision on demand

  GET https://verification.didit.me/v3/session/{sessionId}/decision/
  Headers:
    x-api-key: <your api key>

  Returns the full decision JSON. Use this from the POS / self-checkout when the shopper picks up a restricted SKU — confirm age + region match the SKU's rules before letting the basket close.

STEP 6 — Per-SKU enforcement at checkout

  Inside your POS / store-OS, every restricted SKU carries a category tag (alcohol, tobacco, vape, energy-drink, sharp-tool, RX). Look up the shopper's verified age band + the store's region rules. Examples:

    Alcohol            US-21 / EU-18, blocked in dry counties, time-of-day windows
    Tobacco / vapes    US-21 (state by state) / EU-18, store-licence flag required
    Energy drinks      EU-16 in some regions, no restriction elsewhere
    Sharp tools        ≥ 18 in most regions
    Prescription       Pharmacy hand-off only (DEA Schedule II–V)

  Tune the policy in the no-code Workflow Builder — no redeploy of your store-OS.

WEBHOOK EVENT NAMES
  - Sessions: status changes flow through the standard session webhook.
  - Verify X-Signature-V2 on every payload.

CONSTRAINTS
  - Session statuses use Title Case With Spaces (Approved, In Review). Don't transform them.
  - Don't store the raw document image in your store-OS — Didit holds it, the store-OS holds the shopper PID + age band only.
  - Compute the age band server-side, not in the kiosk — kiosks can be tampered with.
  - Log every entry attempt (Approved + Declined) signed with X-Signature-V2 for the loss-prevention dashboard. Default retention 5 years.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/sessions-api/retrieve-session
  - https://docs.didit.me/integration/webhooks
  - https://docs.didit.me/console/workflows

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

Namba za uthibitisho

Namba za uthibitisho
  • $0.00
    Kifurushi cha KYC cha ziara ya kwanza. Kisha $0.10 kwa kila kurudi kupitia Uthibitishaji wa Biometric.
  • ~1.4s
    Muda wa wastani kutoka uso mlangoni hadi mlango kufunguka.
  • 0+
    Aina za hati katika nchi 220+, inafanya kazi kwa wateja wote wa duka lolote.
  • 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
Anza bure
Maarufu zaidi
Lipa kulingana na matumizi

Kulingana na Matumizi

Lipa tu kwa unachotumia. Moduli 25+. Bei za umma kwa kila moduli, hakuna ada ya chini ya kila mwezi.

  • KYC kamili kwa $0.33 (Kitambulisho + Biometric + IP / Kifaa)
  • Data za AML 10,000+, vikwazo, PEPs, habari hasi
  • Vyanzo vya data vya serikali 1,000+ kwa Uthibitishaji wa Database
  • Ufuatiliaji wa Miamala kwa $0.02 kwa kila muamala
  • KYB ya moja kwa moja kwa $2.00 kwa kila biashara
  • Uchunguzi wa Wallet kwa $0.15 kwa kila ukaguzi
  • Mtiririko wa uthibitishaji wa Whitelabel, brand yako, miundombinu yetu
Tazama orodha kamili ya beiAnza bure
Biashara Kubwa

Biashara Kubwa

MSA & SLA maalum. Kwa idadi kubwa na programu zilizodhibitiwa.

  • Mikataba ya kila mwaka
  • MSA, DPA, na SLA maalum
  • Kituo maalum cha Slack na WhatsApp
  • Wakaguzi wa mikono wanapohitajika
  • Masharti ya muuzaji na white-label
  • Vipengele vya kipekee na ushirikiano wa washirika
  • CSM aliyetajwa, ukaguzi wa usalama, usaidizi wa kufuata
Wasiliana nasi

Anza bure → lipa tu wakati ukaguzi unafanyika → fungua Enterprise kwa mkataba maalum, SLA, au uhifadhi wa data.

FAQ

Maswali ya kawaida

What is Didit?

Didit is infrastructure for identity and fraud, the platform we wished existed when we were building products ourselves: open, flexible, and developer-friendly, so it works as a real part of your stack instead of a black box you integrate around.

One API covers verifying people (KYC, know your customer), verifying businesses (KYB, know your business), screening crypto wallets (KYT, know your transaction), and monitoring transactions in real time, on a stack built to be:

  • Fast, sub-2-second p99 on every session
  • Reliable, in production with 1,500+ companies across 220+ countries
  • Secure, SOC 2 Type 1, ISO 27001, GDPR-native, and formally attested by Spain's financial regulator as safer than verifying someone in person

The footprint underneath: 14,000+ document types in 48+ languages, 1,000+ data sources, and 200+ fraud signals on every session. The Didit infrastructure dynamically learns from every session and gets better every day.

What's autonomous-store entry verification, in plain English?

It's the identity + age check that lets an unstaffed store open its door to a real, eligible shopper, and refuse everyone else, without a human clerk in the loop.

The pattern shows up wherever retail goes staffless:

  • Grab-and-go convenience stores (think Amazon-Go-style, Aldi Shop&Go, REWE Pick&Go, Polish Żabka Nano)
  • Smart fridges in offices, gyms, hospitals, airports
  • Vending pods for tobacco, alcohol, vapes, energy drinks, pharmacy SKUs
  • Autonomous fuel stations with self-pump alcohol-sales counters
  • Ghost kitchens with self-pickup lockers
  • Self-checkout that handles restricted categories

The shopper scans a QR or holds their face to the door camera. Didit verifies who they are and how old they are. The door opens. The basket starts. The POS blocks anything they're not allowed to buy.

Why can't the store just use a card check or a phone number?

Because neither proves a real human with a real age.

  • A card proves a payment instrument, not the cardholder's identity. Stolen cards, gift cards, family cards all pass.
  • A phone number proves a SIM, not a face. SIM farms and shared phones break it instantly.
  • An age self-declaration is the worst, it's the legal-fiction version of asking the shopper to swear they're 21.

Underage purchase of alcohol, tobacco, and vapes is regulated in every developed market, the US (state by state, with strict liability), the EU (Tobacco Products Directive + national alcohol laws), the UK (Licensing Act 2003), Canada, Australia, Japan, Singapore. Penalties run from per-store fines to licence revocation. A real ID + face check is the only durable defence.

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.

Per-region age rules are a nightmare. How do you handle them?

By keeping the rules server-side, not in the kiosk. The verified date of birth comes back from /v3/session/; the rule table lives in your Workflow Builder.

Typical thresholds in scope:

  • Alcohol, EU 18, US 21 (federal floor), some EU states 16 for beer/wine, dry counties block entirely
  • Tobacco, US 21 federal (Tobacco 21 Act), state-by-state vape rules, EU 18
  • Energy drinks, EU 16 in several states (e.g. Lithuania, Latvia), unrestricted elsewhere
  • Sharp tools / knives, UK 18 (Offensive Weapons Act 2019), most US states 18
  • Prescriptions, pharmacy hand-off only, never sold from an unstaffed pod (DEA Schedule II–V controls)

Edit the rules per store, per SKU, per time-of-day in the no-code Workflow Builder. No redeploy of the store-OS. The POS reads the latest policy at scan time.

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.

What does the loss-prevention audit pack look like?

Every entry attempt, Approved, Declined, In Review, produces a signed log line:

  • session_id, Didit's verifiable identifier for the attempt
  • shopper_pid, your pseudonymous shopper id
  • store_id, which store / pod / fridge
  • timestamp, entry time in UTC
  • age_decision, verdict + threshold matched (e.g. Approved · 21+)
  • signature, X-Signature-V2 HMAC SHA-256 of the payload

Pipe to your loss-prevention dashboard, your state-regulator portal (for tobacco / alcohol audits), and your SIEM (Security Information and Event Management). Default retention is 5 years post-relationship, extendable per local audit rules. Ready for ABC (Alcoholic Beverage Control) board inspections in the US and equivalent national bodies in the EU.

What hardware do I need for the store?

Two things at the door, one at the till:

  • At the door, a QR sticker (for first-visit) and a camera (for biometric return). Any IP camera with a clear face shot works; many operators use the off-the-shelf cameras that ship with autonomous-store hardware from Standard Cognition, AiFi, Trigo, Grabango.
  • In the shopper's hand, their own phone for the QR scan + hosted session
  • At the POS / till, your normal self-checkout terminal calling the Didit decision endpoint to confirm age + region against each restricted SKU

No Didit-branded hardware. No proprietary kiosk. The recipe runs on the cameras and terminals you already have.

How do I plug this into my store-OS?

Four wires:

  • The door QR encodes the hosted session URL Didit returns from POST /v3/session/
  • Your callback endpoint receives the signed webhook (X-Signature-V2, HMAC SHA-256). On status: Approved, send the unlock command to your door-controller
  • Your POS calls GET /v3/session/'{'sessionId'}'/decision/ when the shopper scans a restricted SKU, confirms age + region
  • Your loss-prevention dashboard subscribes to the same webhook stream for the audit log

The Didit MCP (Model Context Protocol) server is included free, paste the integration prompt above into Claude Code, Cursor, Codex, Replit Agent, Devin, or Aider and the agent scaffolds the whole thing against the live /v3/ API.

Related

Moduli zinazohusiana + workflows

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