Skip to main content
Didit erhält 7,5 Mio. $ für die Infrastruktur für Identität und Betrug
Didit
Verifizierung für autonome Stores

Verifiziere den Kunden an der Tür. Öffne den Warenkorb. Blockiere eingeschränkte SKUs.

$0.33 erster Besuch, $0.10 jede Rückkehr, Gesichtserkennung an der Tür, Altersprüfung pro Kategorie, kein Personal. 500 Verifizierungen jeden Monat kostenlos.

Unterstützt von
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

Über 2.000 Organisationen weltweit vertrauen uns.

Eine filmische, dunkle, abstrakte Illustration eines autonomen Store-Eingangs, vier schwebende, durchscheinende Glaspaneele in 3D-Perspektive auf reinem Schwarz, durchzogen von einer leuchtenden Didit-Blau-Linie und umrahmt von vier glühenden Scanner-Klammern. Jedes Paneel trägt ein winziges, blassweißes, abstraktes Motiv, das den autonomen Einzelhandelseingang darstellt (Türbogen, ovales Gesicht mit Klammer, Alterskontrollkalender, Einkaufskorb).

Was unbemannter Handel leisten muss

Kein Personal. Trotzdem bei jedem Zutritt compliant.

Unbemannte Convenience Stores, Verkaufsautomaten, smarte Kühlschränke, autonome Tankstellen – sie alle müssen die gleiche Compliance wie ein bemanntes Geschäft erfüllen: echte ID, echtes Alter, echter Audit-Trail. Didit liefert das als einen Workflow: $0.33 erster Besuch, $0.10 jede Rückkehr, mediane Entscheidung in unter 2 Sekunden, 14.000+ Dokumente in über 220 Ländern.

So funktioniert's

Vom Anmelden zum verifizierten Nutzer in vier Schritten.

  1. Schritt 01

    Workflow erstellen

    Wähle die gewünschten Prüfungen aus, ID, Liveness, Face Match, Sanktionen, Adresse, Alter, Telefon, E-Mail, benutzerdefinierte Fragen. Ziehe sie im Dashboard in einen Flow oder poste denselben Flow an unsere API. Verzweige nach Bedingungen, führe A/B-Tests durch, kein Code erforderlich.

  2. Schritt 02

    Integrieren

    Bette nativ mit unserem Web-, iOS-, Android-, React Native- oder Flutter-SDK ein. Leite zu einer gehosteten Seite weiter. Oder sende deinem Nutzer einfach einen Link, per E-Mail, SMS, WhatsApp, überall. Wähle, was zu deinem Stack passt.

  3. Schritt 03

    Nutzer durchläuft den Flow

    Didit hostet die Kamera, die Beleuchtungshinweise, die mobile Übergabe und die Barrierefreiheit. Während der Nutzer den Flow durchläuft, bewerten wir über 200 Betrugssignale in Echtzeit und verifizieren jedes Feld anhand autoritativer Datenquellen. Ergebnis in unter zwei Sekunden.

  4. Schritt 04

    Du erhältst die Ergebnisse

    Echtzeit-signierte Webhooks halten deine Datenbank synchron, sobald ein Nutzer genehmigt, abgelehnt oder zur Überprüfung gesendet wird. Frage die API bei Bedarf ab. Oder öffne die Konsole, um jede Session und jedes Signal zu überprüfen und Fälle nach deinen Wünschen zu verwalten.

Für den autonomen Handel entwickelt · Preis wie Infrastruktur

Sechs Primitive. $0.33 erster Besuch, $0.10 jede Rückkehr.

Compliance im autonomen Handel ist keine einzelne Prüfung, es ist ein Rezept. KYC beim ersten Besuch, Gesichtserkennung bei jeder Rückkehr, Altersprüfung pro SKU pro Region, jede Transaktion signieren.
01 · Eintritts-Flow

Scannen, verifizieren, entsperren.

Bundle für den Erstbesuch, ID-Verifizierung, passive Lebenderkennung, Face Match 1:1, plus Altersberechnung anhand des verifizierten Geburtsdatums. iBeta Level 1 Anti-Spoof zertifiziert, 14.000+ Dokumente aus über 220 Ländern.
User Verification Modul
02 · Alterskontrolle

Altersgrenzen pro Kategorie, pro Region.

Alkohol 18 EU / 21 US, Tabak je nach Bundesstaat, Vapes 18 / 21, Energy Drinks 16 in einigen EU-Staaten, scharfe Werkzeuge 18, verschreibungspflichtige Medikamente nur mit Apothekenübergabe. Serverseitig durchgesetzt, niemals am Kiosk.
Altersverifikationslösung
03 · Wiederkehrender Kunde

Gesicht an der Tür. Kein Telefon.

Biometrische Authentifizierung für $0.10 pro Eintritt, Kunde hält sein Gesicht zur Türkamera, Tür entriegelt. Median 1,4 Sekunden Wall-Clock-Zeit. Dieselbe Identität für jede Filiale in deinem Netzwerk.
Biometrische Authentifizierung
04 · Signiertes Versuchsprotokoll

Jeder Eintrag ist signiert und protokolliert.

Zeitstempel, Filial-ID, Shopper PID (Pseudonyme ID), Altersentscheidung, X-Signature-V2 HMAC SHA-256, ein Eintrag pro Versuch, exportierbar in dein Loss-Prevention-Dashboard oder an das Portal der Aufsichtsbehörde. Standardmäßig 5 Jahre Aufbewahrung.
Webhooks Docs
05 · Kategorie × Region · Zeit

Lokale Regeln, ohne das Store-OS neu deployen zu müssen.

Alkohol in „trockenen“ Landkreisen blockieren, Verkauf nach Ladenschluss steuern, staatliche Lizenz für Vape-SKUs vorschreiben, Rezepte an das Backend der Partnerapotheke weiterleiten. Pro Filiale im No-Code Workflow Builder anpassen.
Workflow Orchestrator
06 · Ökosystem

An Store-OS, POS, Payment Stack anbinden.

Webhooks landen in deinem Store-OS, das POS blockiert eingeschränkte SKUs beim Scannen, Smart Vending öffnet Slots erst nach Altersprüfung, das Loss-Prevention-Dashboard empfängt jeden signierten Versuch.
Face Match 1:1 Modul
Integrieren

Eine Session für den ersten Besuch. Biometrisch für jede Rückkehr.

Öffne die Eintrittssitzung. Lies das signierte Ergebnis. Entriegele die Tür. Erkenne das Gesicht bei jedem weiteren Besuch.
POST /v3/session/Erstbesuch
$ 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" }
  }'
201ErstelltGibt die gehostete Session-URL zurück.
Die Tür bleibt verriegelt, bis der Webhook status: Approved meldet.docs →
POST /v3/session/Return
$ 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..."
  }'
201ErstelltBiometrische Authentifizierung für $0.10 · Tür öffnet in ~1,4 s.
Dieselbe Sessions API. Nur ein Workflow für biometrische Authentifizierung.docs →
Agenten-fertige Integration

Autonomen Store-Zugang mit einem Prompt implementieren.

In Claude Code, Cursor, Codex, Devin, Aider oder Replit Agent einfügen. Deinen Stack ergänzen. Der Agent erstellt beide Workflows, verbindet den Türsteuerungs-Webhook und setzt SKU-Regeln an der Kasse durch.
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.
Brauchst du mehr Kontext? Siehe die vollständige Moduldokumentation.docs.didit.me →
Compliant by Design

Ein neues Land mit einem Klick erschließen. Wir machen die Arbeit.

Wir gründen lokale Tochtergesellschaften, sichern Lizenzen, führen Penetrationstests durch, erhalten Zertifizierungen und passen uns jeder neuen Regulierung an. Um Verifizierungen in einem neuen Land zu starten, legst du einfach einen Schalter um. Über 220 Länder live, vierteljährlich auditiert und Pen-getestet, der einzige Identitätsanbieter, den eine EU-Mitgliedsregierung offiziell als sicherer als die persönliche Verifizierung eingestuft hat.
Sicherheits- & Compliance-Dossier lesen
EU Financial Sandbox
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
Informationssicherheit · 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-konform by Design

Zahlen belegen

Zahlen belegen
  • $0.00
    KYC-Bundle für den ersten Besuch. Danach $0.10 pro Rückkehr über biometrische Authentifizierung.
  • ~1.4s
    Median der realen Zeit von Gesichtserkennung an der Tür bis zur Entriegelung.
  • 0+
    Dokumententypen aus über 220 Ländern, funktioniert für jeden Besucherstrom in jedem Store.
  • 0
    Jeden Monat kostenlose Verifizierungen, für jedes Konto.
Drei Stufen, eine Preisliste

Kostenlos starten. Nach Nutzung zahlen. Bis zum Enterprise-Level skalieren.

500 kostenlose Verifizierungen jeden Monat, für immer. Pay-as-you-go für die Produktion. Individuelle Verträge, Datenresidenz und SLAs (Service Level Agreements) für Enterprise.
Kostenlos

Kostenlos

$0 / Monat. Keine Kreditkarte erforderlich.

  • Kostenloses KYC-Paket (ID-Verifizierung + passive Lebenderkennung + Gesichtsabgleich + Geräte- & IP-Analyse), 500 / Monat, jeden Monat
  • Blockierte Nutzer
  • Duplikaterkennung
  • Über 200 Betrugssignale pro Session
  • Wiederverwendbares KYC im Didit-Netzwerk
  • Case Management Plattform
  • Workflow Builder
  • Öffentliche Docs, Sandbox, SDKs, MCP (Model Context Protocol) Server
  • Community Support
Am beliebtesten
Zahlung nach Nutzung

Nutzungsbasiert

Zahle nur, was du nutzt. Über 25 Module. Öffentliche Preise pro Modul, keine monatliche Mindestgebühr.

  • Full KYC für $0.33 (ID + Biometrie + IP / Gerät)
  • Über 10.000 AML-Datensätze, Sanktionen, PEPs, Adverse Media
  • Über 1.000 staatliche Datenquellen für Datenbankvalidierung
  • Transaktionsüberwachung für $0.02 pro Transaktion
  • Live KYB für $2.00 pro Unternehmen
  • Wallet Screening für $0.15 pro Prüfung
  • Whitelabel-Verifizierungsflow, deine Marke, unsere Infrastruktur
Enterprise

Enterprise

Individuelle MSA & SLA. Für große Volumina und regulierte Programme.

  • Jahresverträge
  • Individuelle MSA, DPA und SLA
  • Dedizierter Slack- und WhatsApp-Kanal
  • Manuelle Prüfer auf Abruf
  • Reseller- und White-Label-Konditionen
  • Exklusive Features und Partnerintegrationen
  • Benannter CSM, Sicherheitsprüfung, Compliance-Support

Kostenlos starten → nur zahlen, wenn eine Prüfung läuft → Enterprise für einen individuellen Vertrag, SLA oder Datenresidenz freischalten.

FAQ

Häufige Fragen

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.

Infrastruktur für Identität und Betrugsprävention.

Eine API für KYC, KYB, Transaktionsüberwachung und Wallet-Screening. In 5 Minuten integriert.

Lass dir diese Seite von einer KI zusammenfassen