Uso ni tiketi. Hakuna QR. Hakuna msimbopau. Hakuna chapa.
Mwandikishe mnunuzi mara moja wakati wa ununuzi. Kila skani ya lango ni mechi ya uso 1:N ya chini ya sekunde 1. Bure kwa kila skani baada ya kujiandikisha. Uthibitishaji 500 bure kila mwezi.
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 Utafutaji wa Uso 1:N
— chini ya sekunde 1 kwa kiwango cha sherehe. Mtiririko huo huo hufanya kazi katika viwanja, sherehe,
njia za usafiri, na mikutano.
Jinsi inavyofanya kazi
Kutoka kujiandikisha hadi mtumiaji aliyethibitishwa kwa hatua nne.
Hatua 01
Unda mtiririko wa kazi
Chagua ukaguzi unaotaka — Kitambulisho, uhai, mechi ya uso, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko kwenye dashibodi, au tuma mtiririko huo huo kwenye API yetu. Tawi kwenye masharti, endesha majaribio ya A/B, hakuna msimbo unaohitajika.
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 mkusanyiko wako.
Hatua 03
Mtumiaji anapitia mtiririko
Didit huandaa kamera, ishara za taa, uhamishaji wa simu, na ufikiaji. Wakati mtumiaji yuko kwenye mtiririko, tunapata alama za ishara 200+ za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya mamlaka. Matokeo chini ya sekunde mbili.
Hatua 04
Unapokea matokeo
Webhooks zilizosainiwa kwa wakati halisi huweka hifadhidata yako ikiwa sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Uliza API inapohitajika. Au fungua koni kukagua kila kikao, kila ishara, na kudhibiti kesi kwa njia yako.
Imejengwa kwa ajili ya kumbi · Bure kwa kila skani baada ya kujiandikisha
Uwezo sita. $0.25 mara moja, bure kwa kila skani.
Usajili mmoja hulipia kila lango linalofuata. Utafutaji wa Uso 1:N umejumuishwa bure kwenye kila akaunti ya Didit; ukumbi hulipa tu kwa ukaguzi wa kitambulisho wa mara moja wakati wa ununuzi.
Selfie moja wakati wa kulipa. Inaweza kutumika tena milele.
Weka kikao cha API cha Vikao kwenye mtiririko wako wa ununuzi. Uthibitishaji wa Kitambulisho unathibitisha mnunuzi, Uhai Tulivu unakataa kila aina ya Utambuzi wa Mashambulizi ya Uwasilishaji (PAD), na picha inayosababishwa inahifadhiwa kama kiolezo cha faharisi ya tukio la mnunuzi — kilichofungwa kwa vendor_data yako, kinachoweza kutumika tena katika kila tukio la baadaye ambalo mnunuzi huyo anahudhuria.
Inaweza kutumika tena katika kila tukio la baadaye ambalo mnunuzi yule yule anahudhuria.
02 · Uso NDIO tiketi
Hakuna simu. Hakuna chapa. Hakuna msimbopau.
Langoni, kamera inachukua fremu moja na mgeni anapita. Hakuna kutoa simu (hakuna wasiwasi wa betri), hakuna nakala iliyochapishwa (hakuna karatasi, hakuna udanganyifu wa kuuza tena), hakuna msimbo wa Majibu ya Haraka (QR) kabisa. Uso wa mnunuzi NDIO ishara ya ufikiaji, na Utafutaji wa Uso 1:N ni bure kwenye kila mpango.
Hakuna msimbo wa QRHakuna kutoa simu, hakuna wasiwasi wa betri
Hakuna chapaHakuna karatasi, hakuna udanganyifu wa kuuza tena
Angalia kameraLango linanasa fremu moja
Uamuzi katika ~sekunde 1Linganisha na faharisi ya tukio
Kulinganisha chini ya sekunde 1 langoni.Bure kwa kila skani
03 · Matrix ya uamuzi wa lango
Kuingia. Kuingia tena. Zuia. Inaweza kusanidiwa.
Mzigo wa malipo ya mechi hukupa rejeleo la mnunuzi anayelingana na similarity_score. Mantiki yako ya lango 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.
Uso umelingana · tayari yuko ndaniSera ya kuingia tena
Uso umelingana · tiketi imeisha mudaMwelekeze kwa wafanyakazi
Uso umelingana · umeuzwa tena kwa mnunuzi mwingineZuia
Hakuna kinacholingana · sura isiyojulikanaZuia
Inaweza kusanidiwa kwa kila tukio, kwa kila lango, kwa kila kiwango cha tiketi.
04 · Uwanja, sherehe, usafiri
Usajili sawa. Kila aina ya ukumbi.
Kiolezo kimoja cha uso kinashughulikia 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 hutumia kitambulisho bila gharama — Semantiki ya Kitambulisho Kinachoweza Kutumika Tena inatumika kwa udhibiti wa ufikiaji.
Matukio ya viwanjaniMpira wa miguu, matamasha, mashindano
TamashaSiku nyingi, malango mengi, inaweza kutumika tena
Njia za usafiriPasi za msimu, wasafiri wa kila siku
MikutanoVikao, vyumba vya kupumzikia, kumbi za maonyesho
Usajili mmoja. Kila tukio.Nchi 220+
05 · Uwezo wa kiwango cha sherehe
Mechi ya chini ya sekunde 1 kwa kiwango cha tamasha.
Imejaribiwa kwa makumi ya maelfu ya nyuso zilizosajiliwa kwa kila faharisi ya tukio, mechi ya fremu moja kwa takriban sekunde, ~30 za kuingia kwa dakika kwa kila lango. Muda wa kufanya kazi wa jukwaa ni 99.99% — API sawa ya /v3/ kama moduli nyingine yoyote ya Didit, kwa hivyo kitabu cha uendeshaji ulichonacho tayari kwa KYC kinatumika langoni.
API sawa ya /v3/ kama moduli nyingine zote za Didit.
06 · Bure langoni
$0.25 mara moja. Bure kwa kila skani. 500 bila malipo / mwezi.
Bei ya umma, hakuna kiwango cha chini, hakuna mkataba. Uthibitishaji wa Kitambulisho kwa $0.15 pamoja na Uhai Tulivu kwa $0.10 hugharamia usajili wa mara moja kwa $0.25 kwa kila mnunuzi. Utafutaji wa Uso 1:N kwa kila skani ya lango inayofuata ni bure. Nafuu kuliko bomba la tiketi ya karatasi iliyochapishwa mara tu unapozingatia udanganyifu na hasara za kuuza tena.
Uthibitishaji wa Kitambulisho (jiandikishe)$0.15 one-time
Uhai Tulivu (jiandikishe)$0.10 one-time
Utafutaji wa Uso 1:N kwenye langoBure / skani
Nafuu kuliko mchakato wa tiketi za karatasi zilizochapishwa.
Unganisha
Sehemu moja ya mwisho ya usajili. Sehemu moja ya mwisho ya lango.
Mwandikishe mnunuzi kwa simu ya API ya Vikao wakati wa malipo. Linganisha fremu ya kamera kwenye lango na simu ya Utafutaji wa Uso 1:N inayojitegemea. Mkataba sawa wa /v3/ kama moduli nyingine yoyote ya Didit.
Bure kwa kila skani. Mechi inarudisha vendor_data + similarity_score.nyaraka →
Ujumuishaji tayari kwa wakala
Tuma tiketi za matukio ya kibayometriki kwa haraka.
Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Wakala huandaa Didit, huunda mtiririko wa kazi wa usajili, huunganisha sehemu ya skani ya lango, na kutuma.
didit-integration-prompt.md
You are integrating Didit'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'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'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+ zinafanya kazi, zinakaguliwa na kujaribiwa 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.
Usajili wa mara moja kwa kila mnunuzi. Kila uchunguzi wa lango wa baadaye ni bure.
~1s
Ulinganishaji wa uso wa fremu moja kwenye faharisi za matukio ya kiwango cha tamasha.
0.00%
Muda wa kufanya kazi wa jukwaa — API sawa ya /v3/ kama moduli nyingine zote za Didit.
0
Uthibitishaji wa bure kila mwezi, milele.
Ngazi tatu, orodha moja ya bei
Anza bure. Lipa kwa matumizi. Panua hadi Biashara.
Uthibitishaji 500 bila malipo kila mwezi, milele. Lipa kadri unavyotumia kwa uzalishaji. Mikataba maalum, makazi ya data, na SLA (Mikataba ya Kiwango cha Huduma) kwenye Biashara.
Bure
Bure
$0 / mwezi. Hakuna kadi ya mkopo inayohitajika.
Kifurushi cha KYC cha bure (Uthibitishaji wa Kitambulisho + Uhai Usio na Kazi + Kulinganisha Uso + Uchambuzi wa Kifaa na IP) — 500 / mwezi, kila mwezi
Watumiaji Waliozuiliwa
Kugundua Marudio
Ishara 200+ za udanganyifu kwenye kila kipindi
KYC inayoweza kutumika tena kwenye mtandao wa Didit
Jukwaa la Usimamizi wa Kesi
Mjenzi wa Mtiririko wa Kazi
Hati za umma, sandbox, SDKs, seva ya MCP (Model Context Protocol)