Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Tiketi za matukio kwa biometriska

Uso ndio tiketi. Hakuna QR. Hakuna barcode. Hakuna chapisho.

Msajili mnunuzi mara moja wakati wa ununuzi. Kila skani ya lango ni mechi ya uso ya 1:N chini ya sekunde 1. Bure kwa kila skani baada ya usajili. Uthibitishaji 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.

Mrundiko wa tiketi za matukio ya biometriska yenye giza, ya sinema, paneli nne za kioo zinazoelea, zinazopitisha mwanga katika mtazamo wa 3D kwenye rangi nyeusi safi, zikipitishwa na mstari mweupe wa Didit Blue na zikizungukwa na mabano ya skana yanayong'aa. Kila paneli ina motifu ndogo nyeupe-nyepesi inayowakilisha uwanja wa michezo, muundo wa skana wa dot-matrix, lango la kugeuka, na safu ya mistari ya viti.

Viwanja · Tamasha · Usafiri · Mikutano

Ruka msimbo wa QR. Pita tu.

Hakuna kutoa simu, hakuna wasiwasi wa betri, hakuna udanganyifu wa kuuza tena. Mnunuzi anajiandikisha mara moja wakati wa ununuzi kwa $0.25, na kila skani ya lango ya baadaye ni mechi ya bure ya Utafutaji wa Uso 1:N , chini ya sekunde 1 kwa kiwango cha tamasha. Mfumo huo huo hufanya kazi katika viwanja, sherehe, njia za usafiri, na mikutano.

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 kwenye dashibodi, au tuma mtiririko huo huo kwenye API yetu. Panga masharti, fanya majaribio ya A/B, hakuna code inayohitajika.

  2. Hatua 02

    Unganisha

    Pachika asili na Web, iOS, Android, React Native, au Flutter SDK yetu. 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 kwa wakati halisi huweka database yako sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Piga API inapohitajika. Au fungua console kukagua kila kikao, kila ishara, na kudhibiti kesi zako mwenyewe.

Imejengwa kwa ajili ya kumbi · Bure kwa kila skani baada ya usajili

Uwezo sita. $0.25 mara moja, bure kwa kila skani.

Usajili mmoja unalipia kila lango linalofuata. Face Search 1:N imejumuishwa bure kwenye kila akaunti ya Didit; ukumbi unalipa tu kwa ukaguzi wa kitambulisho wa mara moja wakati wa ununuzi.
Soma nyarakaPata API key
01 · Sajili wakati wa ununuzi

Selfie moja wakati wa kulipa. Inaweza kutumika tena milele.

Weka kikao cha Sessions API kwenye mtiririko wako wa ununuzi. Uthibitishaji wa ID unathibitisha mnunuzi, Passive Liveness inakataa kila aina ya Presentation Attack Detection (PAD), na picha inayosababishwa inahifadhiwa kama template ya index ya tukio ya mnunuzi, iliyofungwa kwa vendor_data yako, inayoweza kutumika tena katika kila tukio la baadaye ambalo mnunuzi huyo anahudhuria.
Moduli ya Uthibitishaji wa Kitambulisho
02 · Uso NDIO tiketi

Hakuna simu. Hakuna chapa. Hakuna barcode.

Langoni, kamera inanasa fremu moja na mgeni anapita. Hakuna kutoa simu (hakuna wasiwasi wa betri), hakuna chapisho (hakuna karatasi, hakuna udanganyifu wa kuuza tena), hakuna Quick Response (QR) code kabisa. Uso wa mnunuzi NDIO tokeni ya ufikiaji, na Face Search 1:N ni bure kwenye kila mpango.
Moduli ya Utafutaji wa Uso 1:N
03 · Matrix ya uamuzi wa lango

Kuingia. Kuingia tena. Zuia. Inaweza kusanidiwa.

Payload ya mechi inakupa rejeleo la mnunuzi anayelingana na similarity_score. Mantiki ya lango lako inagawanyika: tiketi halali + skani ya kwanza = kuingia; tayari ndani = sera ya kuingia tena; tiketi iliyoisha muda au iliyoghairiwa = elekeza kwa wafanyakazi; iliyouzwa tena au isiyolingana = zuia. Kwa kila tukio, kwa kila lango, kwa kila kiwango cha tiketi.
Mratibu wa Mtiririko wa Kazi
04 · Uwanja, tamasha, usafiri

Usajili uleule. Kila aina ya ukumbi.

Template moja ya uso inashughulikia viwanja vya mpira, sherehe za siku nyingi, pasi za msimu wa usafiri, na mikutano mikubwa. Mnunuzi anajiandikisha mara moja na wewe, na kila ukumbi unaotumia Didit anaohudhuria baada ya hapo unatumia kitambulisho bila gharama yoyote, semantics za Reusable Credential zimetumika kwa udhibiti wa ufikiaji.
Mtiririko wa kazi wa kudhibiti ufikiaji
05 · Uwezo wa kiwango cha tamasha

Mechi chini ya sekunde 1 kwa kiwango cha tamasha.

Imejaribiwa kwa makumi ya maelfu ya nyuso zilizosajiliwa kwa kila index ya tukio, mechi ya fremu moja kwa takriban sekunde moja, ~30 za kuingia kwa dakika kwa kila lango. Uptime ya jukwaa ni 99.99%, API sawa ya /v3/ kama moduli nyingine yoyote ya Didit, kwa hivyo playbook ya shughuli uliyonayo tayari kwa KYC inatumika kwa lango.
Vigezo vya utendaji
06 · Bure langoni

$0.25 mara moja. Bure kwa kila skani. 500 bure / mwezi.

Bei ya umma, hakuna kiwango cha chini, hakuna mkataba. Uthibitishaji wa Kitambulisho kwa $0.15 pamoja na Passive Liveness kwa $0.10 inagharamia usajili wa mara moja kwa $0.25 kwa kila mnunuzi. Utafutaji wa Uso 1:N kwenye kila skani ya lango inayofuata ni bure. Nafuu kuliko mfumo wa tiketi za karatasi zilizochapishwa ukizingatia udanganyifu na hasara za kuuza tena.
Angalia bei
Unganisha

Endpoint moja ya usajili. Endpoint moja ya lango.

Msajili mnunuzi kwa kutumia simu ya Sessions API wakati wa malipo. Linganisha fremu ya kamera kwenye lango na simu ya Face Search 1:N inayojitegemea. Mkataba sawa wa /v3/ kama moduli nyingine yoyote ya Didit.
POST /v3/session/Jisajili
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_event_enrol",
    "vendor_data": "buyer-42",
    "metadata": { "event_id": "evt_1234" }
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
Inatumia ID_VERIFICATION + LIVENESS; inaunganisha picha na vendor_data.nyaraka →
POST /v3/face-search/Lango · bure
$ curl -X POST https://verification.didit.me/v3/face-search/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -F "image=@gate-frame.jpg" \
  -F "metadata={'event_id':'evt_1234'}"
200Sawa{ "status": "Imeidhinishwa", "matches": […] }
Bure kwa kila skani. Mechi inarudisha vendor_data + similarity_score.nyaraka →
Ujumuishaji tayari kwa agent

Tuma tiketi za matukio ya kibayometriki kwa amri moja.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent inasanidi Didit, inajenga mtiririko wa kazi wa usajili, inaunganisha endpoint ya skani ya lango, na inatuma.
didit-integration-prompt.md
You are integrating Didit&apos;s biometric event-ticketing into <my_stack>. The face IS the ticket — no QR code, no barcode, no printout. Two phases:

  1. Enrol the buyer ONCE at ticket purchase. A Sessions API call runs ID Verification + Passive Liveness and stores the buyer&apos;s portrait as the event-index template.
  2. At every gate scan, call the standalone Face Search 1:N endpoint with the camera frame. Sub-1-second match against the event index. Verdict returned inline.

Pricing (public):
  - Enrolment (one-time per buyer): $0.15 ID Verification + $0.10 Passive Liveness = $0.25
  - Face Search 1:N at the gate: free per scan
  - 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 Hash-based Message Authentication Code (HMAC) SHA-256 verification using the X-Signature-V2 header.
 HMAC-SHA256 verification MUST run against the raw body bytes (the raw payload as Didit sent it) BEFORE any JSON parsing — re-serialising the parsed body changes whitespace and key order, which invalidates the signature.  - A workflow_id from the Workflow Builder. The workflow MUST contain ID_VERIFICATION + LIVENESS (and optionally Anti-Money Laundering (AML) if you sell age-restricted access).
  - One Didit account = one face index. Tag every enrolment with metadata.event_id so the gate-side search filters by the right event.

STEP 1 — Enrol at ticket purchase

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<your enrolment workflow>",
      "vendor_data": "<your buyer id — must be unique per buyer>",
      "callback": "https://<your-app>/ticketing/enrol/callback",
      "metadata": {
        "order_id": "<your order reference>",
        "event_id": "<the event the buyer is entering>",
        "ticket_tier": "<GA | VIP | accessible | etc>"
      }
    }

  Response: 201 Created with the hosted session_url. Redirect the buyer. After the buyer completes ID Verification + Passive Liveness, the portrait is stored as their face template and bound to vendor_data.

STEP 2 — Read the signed verdict on enrolment completion

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your buyer id>",
      "status": "Approved",
      "id_verification": { "status": "Approved", "document_type": "Passport" },
      "liveness": { "status": "Approved", "method": "PASSIVE", "score": 94 }
    }

  Verify X-Signature-V2 BEFORE trusting the body. On Approved, mark the order as enrolled and bind the order to vendor_data in your application database.

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

STEP 3 — At every gate scan, match the face against the event index

  POST https://verification.didit.me/v3/face-search/
  Headers:
    x-api-key: <your api key>
  Body (multipart/form-data):
    image           <the camera frame captured at the gate>
    vendor_data     <optional — restrict the search to a specific buyer>
    metadata        <optional JSON — e.g. { "event_id": "<...>" } to filter>

  Response (excerpted):
    {
      "status": "Approved",
      "matches": [
        {
          "vendor_data": "<buyer id>",
          "similarity_score": 0.96
        }
      ]
    }

  Match outcomes the gate logic should handle:
    - Match found, ticket valid, no prior scan      → grant entry, mark scanned
    - Match found, already inside                    → apply re-entry policy
    - Match found, ticket expired or canceled        → route to staff
    - Match found, ticket resold to another buyer    → block, route to staff
    - No match (similarity below threshold)          → block, fall back to backup ticket flow

STEP 4 — Reusable across every event the same buyer attends

  Because the buyer&apos;s face template is bound to vendor_data, the SAME enrolment works for every future event the same buyer holds a ticket for. No re-enrolment, no re-payment. Reusable Credential semantics applied to the venue use case.

CONSTRAINTS
  - Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
  - Feature enum is UPPERCASE: ID_VERIFICATION, LIVENESS, FACE_MATCH, AML, IP_ANALYSIS.
  - Method enum is UPPERCASE: PASSIVE, FLASHING, ACTIVE_3D.
  - Auth header is x-api-key (lowercase, hyphenated).
  - Webhook signature header is X-Signature-V2 (NOT X-Signature).
  - Status casing matches exactly: Approved, Declined, In Review, Expired, Not Finished, Resubmitted, Kyc Expired, Abandoned.
  - The face template is irreversible (a one-way hash). End users can request deletion via the standard data-subject-request path.

ACCESS CONTROL CONSIDERATIONS
  - For minor-attended events, run AGE_ESTIMATION during enrolment to gate age-restricted areas. See /solutions/age-verification.
  - For high-value VIP areas, gate behind a Biometric Authentication step-up. See /solutions/biometric-2fa.
  - For accessibility lanes, surface the ticket-tier metadata on the verdict payload and route the gate UI accordingly.

DATA-PROTECTION NOTES
  - The enrolment selfie produces an irreversible face template; raw images are deleted unless retention is explicitly enabled.
  - The gate frame is processed in memory and not persisted by default.
  - Display the privacy notice (didit.me/terms/verification-privacy-notice) to the buyer before the enrolment selfie. EU GDPR Article 13 requires it.

Read the docs:
  - https://docs.didit.me/core-technology/face-search/overview
  - https://docs.didit.me/sessions-api/create-session
  - 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

Takwimu za kuthibitisha
  • $0.00
    Usajili wa mara moja kwa kila mnunuzi. Kila skani ya lango ijayo ni bure.
  • ~1s
    Ulinganishaji wa uso wa fremu moja kwenye faharisi za matukio makubwa ya tamasha.
  • 0.00%
    Muda wa mfumo kuwaka, API ileile ya /v3/ kama moduli nyingine zote za Didit.
  • 0
    Uthibitishaji wa bure kila mwezi, milele.
Ngazi tatu, orodha moja ya bei

Anza bure. Lipa kulingana na matumizi. Panua hadi Enterprise.

Uthibitishaji 500 bila malipo kila mwezi, milele. Lipa kadri unavyotumia kwa uzalishaji. Mikataba maalum, uhifadhi wa data, na SLA (Service Level Agreements) kwenye Enterprise.
Bure

Bure

$0 / mwezi. Hakuna kadi ya mkopo inayohitajika.

  • Kifurushi cha bure cha KYC (Uthibitishaji wa Kitambulisho + Passive Liveness + Face Match + Uchambuzi wa Kifaa & IP), 500 / mwezi, kila mwezi
  • Watumiaji Waliozuiwa
  • Utambuzi wa Marudio
  • Ishara 200+ za udanganyifu kwenye kila session
  • KYC inayoweza kutumika tena kwenye mtandao wa Didit
  • Jukwaa la Usimamizi wa Kesi
  • Workflow Builder
  • Nyaraka za umma, sandbox, SDKs, server ya MCP (Model Context Protocol)
  • Usaidizi wa jamii
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 is "face-as-ticket"?

A ticket where the access token is the buyer's face, not a Quick Response (QR) code, a barcode, or a paper printout.

The buyer takes a selfie at purchase. The face template is stored against the order. At the gate, a camera captures one frame and 1:N face search matches it against the event's enrolled templates. Sub-1-second verdict, walk through.

Why are venues moving away from QR codes?

Three problems with QR-based ticketing:

  • Resale fraud. A screenshot of a QR code is the ticket. Once a buyer screenshots and resells, every copy is valid until the first scan invalidates it, chaos at the gate.
  • Battery anxiety. Phones die mid-day; users argue with stewards.
  • Throughput. A QR scanner takes 2-4 seconds per scan plus fumble time. A face camera takes one frame at walking pace.
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.

What about people who don't want to be enrolled?

Always ship a non-biometric fallback, a printed PDF, an email-delivered QR code, or a staffed gate. The European Union Artificial Intelligence Act and most national consumer-protection regimes require an alternative path.

In practice, venues running biometric ticketing report 70-85% opt-in because the face lane is dramatically faster. The non-biometric lane stays open for the rest.

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.

How fast is the match at the gate?
Sub-1-second per scan against event indexes in the tens of thousands of enrolled faces. Throughput at a single gate sits around 30 entries per minute at a comfortable walking pace, comparable to the fastest QR scanner pipelines without the fumble time. Platform uptime is 99.99%, with the same operations playbook as every other Didit module.
Do we need an on-premise camera or special hardware?

Any commodity IP camera or tablet works, POST /v3/face-search/ accepts a single JPEG frame over HTTPS. Most venues use existing entry kiosks, ticket-scanner replacements, or a tablet on a stand. No custom Software Development Kit (SDK), no special drivers, no on-premise inference box.

For edge-cached gates (transit, large venues without reliable connectivity), Didit ships an on-premise face-search appliance, talk to sales.

What about minors and age-restricted events?

Run AGE_ESTIMATION at enrolment for age-gated zones (over-18 areas at a festival, alcohol bars at a stadium). The signed verdict carries an age band per buyer, and your gate logic surfaces the right wristband colour or wristband-free lane.

For minors attending family events, a parent / guardian completes the enrolment on the minor's ticket and consents to the template on the minor's behalf, the EU General Data Protection Regulation requires explicit parental consent under age 16 in most member states.

Related

Moduli zinazohusiana + mtiririko wa kazi

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