Verifica al comprador en la entrada. Abre la cesta. Bloquea los SKU restringidos.
$0.33 la primera visita, $0.10 cada regreso, reconocimiento facial en la entrada, edad verificada por categoría, sin personal. 500 verificaciones gratis cada mes.
Con la confianza de más de 2.000 organizaciones en todo el mundo.
Lo que el comercio sin personal debe cumplir
Sin dependientes. Sin personal. Cumplimiento garantizado en cada entrada.
Las tiendas de conveniencia sin personal, los puntos de venta automáticos, las neveras inteligentes, las gasolineras autónomas…
todas deben cumplir con las mismas normativas que una tienda con personal: identificación real, edad real,
y un rastro de auditoría real. Didit lo ofrece como un único flujo de trabajo: $0.33 la primera visita, $0.10 cada
regreso, veredicto en menos de 2 segundos de media, más de 14.000 documentos en más de 220 países.
Cómo funciona
De la suscripción al usuario verificado en cuatro pasos.
Paso 01
Crea el flujo de trabajo
Elige las verificaciones que necesites: ID, prueba de vida, coincidencia facial, sanciones, dirección, edad, teléfono, email, preguntas personalizadas. Arrástralas a un flujo en el panel de control, o publica el mismo flujo en nuestra API. Crea ramificaciones condicionales, haz pruebas A/B, sin necesidad de código.
Paso 02
Integra
Integra de forma nativa con nuestros SDK para Web, iOS, Android, React Native o Flutter. Redirige a una página alojada. O simplemente envía a tu usuario un enlace, por email, SMS, WhatsApp, donde quieras. Elige lo que mejor se adapte a tu stack.
Paso 03
El usuario completa el proceso
Didit gestiona la cámara, las indicaciones de iluminación, la transferencia móvil y la accesibilidad. Mientras el usuario está en el flujo, puntuamos más de 200 señales de fraude en tiempo real y verificamos cada campo contra fuentes de datos autorizadas. El resultado en menos de dos segundos.
Paso 04
Recibes los resultados
Los webhooks firmados en tiempo real mantienen tu base de datos sincronizada en el momento en que un usuario es aprobado, rechazado o enviado a revisión. Consulta la API bajo demanda. O abre la consola para inspeccionar cada sesión, cada señal, y gestiona los casos a tu manera.
Diseñado para el comercio autónomo · Precios de infraestructura
Seis primitivas. $0.33 la primera visita, $0.10 cada regreso.
El cumplimiento en el comercio autónomo no es una única verificación, es una receta. KYC en la primera visita, reconocimiento facial en cada regreso, control de edad por SKU y región, y firma de cada intento.
Paquete de primera visita: verificación de identidad, prueba de vida pasiva, Face Match 1:1, más la edad calculada a partir de la fecha de nacimiento verificada. Certificado iBeta Nivel 1 anti-spoof, más de 14 000 documentos en más de 220 países.
Alcohol 18 UE / 21 EE. UU., tabaco estado por estado, vapers 18 / 21, bebidas energéticas 16 en algunos estados de la UE, herramientas afiladas 18, entrega de recetas en farmacia. Aplicado en el servidor, nunca en el quiosco.
Autenticación biométrica a 0,10 $ por entrada: el comprador acerca su cara a la cámara de la puerta y esta se desbloquea. Tiempo medio de 1,4 segundos. Misma identidad en todas las tiendas de tu flota.
Marca de tiempo, ID de tienda, PID de comprador (identificador seudónimo), decisión de edad, X-Signature-V2 HMAC SHA-256: un registro por intento, exportable a tu panel de prevención de pérdidas o al portal del regulador estatal. Retención predeterminada de 5 años.
Pipe to your loss-prevention dashboard. 5-year retention.
05 · Categoría × región · tiempo
Reglas locales sin volver a desplegar el sistema operativo de la tienda.
Bloquea el alcohol en condados secos, restringe las ventas fuera de horario, exige una licencia estatal para SKUs de vapeo, dirige las recetas al backend de la farmacia asociada. Edita por tienda en el Workflow Builder sin código.
Tune rules per store in the no-code Workflow Builder.
06 · Ecosistema
Integración con el sistema operativo de la tienda, TPV y pila de pagos.
Los webhooks llegan a tu sistema operativo de tienda, el TPV bloquea los SKUs restringidos al escanear, las máquinas expendedoras inteligentes abren ranuras solo después de la verificación de edad, el panel de prevención de pérdidas recibe cada intento firmado.
201CreadoAutenticación biométrica por $0.10 · puerta abre en ~1.4 s.
La misma API de Sesiones. Solo un flujo de autenticación biométrica.docs →
Integración lista para agentes
Lanza la entrada a tu tienda autónoma con un solo prompt.
Pégalo en Claude Code, Cursor, Codex, Devin, Aider o Replit Agent. Rellena tu stack. El agente construye ambos flujos de trabajo, conecta el webhook del controlador de la puerta y aplica las reglas de SKU en el checkout.
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.
¿Necesitas más contexto? Consulta la documentación completa del módulo.docs.didit.me →
Cumplimiento por diseño
Abre un nuevo país en un clic. Nosotros hacemos el trabajo duro.
Abrimos las filiales locales, aseguramos las licencias, realizamos las pruebas de penetración, obtenemos las certificaciones y nos alineamos con cada nueva regulación. Para lanzar verificaciones en un nuevo país, activa un interruptor. Más de 220 países en vivo, auditados y probados trimestralmente, el único proveedor de identidad que un gobierno de un estado miembro de la UE ha calificado formalmente como más seguro que la verificación presencial.
Paquete KYC para la primera visita. Luego $0.10 por cada regreso con autenticación biométrica.
~1.4s
Tiempo medio real desde que se detecta la cara en la puerta hasta que esta se desbloquea.
0+
Tipos de documentos en más de 220 países: funciona para todo el flujo de clientes de cualquier tienda.
0
Verificaciones gratuitas cada mes, en cada cuenta.
Tres niveles, una lista de precios
Empieza gratis. Paga por uso. Escala a Enterprise.
500 verificaciones gratuitas cada mes, para siempre. Pago por uso para producción. Contratos personalizados, residencia de datos y SLAs (Acuerdos de Nivel de Servicio) en Enterprise.
Gratis
Gratis
$0 / mes. No se requiere tarjeta de crédito.
Paquete KYC gratuito (Verificación de ID + Prueba de vida pasiva + Coincidencia facial + Análisis de dispositivo e IP), 500 / mes, cada mes
Empieza gratis → paga solo cuando se ejecuta una verificación → desbloquea Enterprise para un contrato personalizado, SLA o residencia de datos.
FAQ
Preguntas frecuentes
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:
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.
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.