Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Kuingia upya kwa selfie pekee

Muingize mtumiaji tena. Kwa selfie moja.

Weka face match ya chini ya sekunde 2 kwa watumiaji wanaorudi. Ruka kuweka upya nenosiri. Ruka ucheleweshaji wa SMS. Ruka tatizo la magic-link. $0.10 kwa kila kuingia upya, uthibitishaji 500 bure kila mwezi.

Anza bureSoma nyaraka
Inaungwa mkono na
Y CombinatorRobinhood Ventures
Firecrawl
Slash
Crnogorski Telekom
UCSF Neuroscape
Bit2Me
Shiply

Inaaminika na mashirika 2,000+ duniani kote.

Picha nyeusi ya sinema ya selfie-only re-auth stack, paneli nne za kioo zinazoelea, zinazopitisha mwanga katika mtazamo wa 3D kwenye 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 kitanzi cha kuburudisha cha duara, mstari unaounganisha nukta mbili, saa, na pete ya mwendelezo.

Bila nenosiri · sugu dhidi ya phishing

Acha kupoteza watumiaji wanaorudi wakati wa kuingia. Sekunde mbili. Wanarudi.

Uwekaji upya wa nenosiri hupoteza ~30% ya watumiaji wanaorudi; nambari za Short Message Service (SMS) zinaweza kuchukua hadi sekunde 90. Selfie dhidi ya picha iliyosajiliwa ya mtumiaji inakamilika kwa takriban sekunde mbili, mkataba wa callback rahisi kwa mtiririko wowote uliopo wa OAuth / OpenID Connect. $0.10 kwa kila kuingia upya. Uthibitishaji 500 bure kila mwezi.

Jinsi inavyofanya kazi

Kutoka kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.

  1. Hatua 01

    Unda workflow

    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 moja kwa moja 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 mchakato

    Didit inasimamia kamera, ishara za mwanga, uhamishaji wa simu, na ufikiaji. Mtumiaji akiwa kwenye mchakato, tunapima ishara 200+ za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya kuaminika. Matokeo yanapatikana chini ya sekunde mbili.

  4. Hatua 04

    Unapokea matokeo

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

Badilisha nenosiri · Ruka SMS · Tuma magic link

Uwezo sita. $0.10 kwa kila re-auth.

Simu moja ya Sessions API, uamuzi mmoja uliotiwa saini, mkataba wa callback wa kuingiza. Unganisha na Device & IP Analysis ili kuruka selfie kabisa kwenye sessions zinazojulikana kuwa salama.
Soma nyarakaPata API key
01 · Mtiririko wa kuingia kwa kugusa

Gusa mara moja. Selfie moja. Rudi ndani.

Fungua simu ya Sessions API, elekeza mtumiaji kwenye Uniform Resource Locator (URL) iliyopangishwa, piga picha moja tulivu. Liveness + Face Match 1:1 + webhook iliyotiwa saini inarudi ndani ya sekunde mbili hizo hizo. Hakuna usakinishaji wa programu, hakuna Software Development Kit (SDK), hakuna njia ya mtoa huduma.
Moduli ya Uthibitishaji wa Kibayometriki
02 · dhidi ya nenosiri / SMS / magic link

Msuguano mdogo. Hakuna wizi wa data. Nafuu kuliko SMS.

Nywila huibiwa, husahaulika, na huwekwa upya (tiketi ya usaidizi ya $1-$3 kila wakati). Nenosiri la mara moja la Short Message Service (SMS) linaweza kuibiwa, linategemea mtoa huduma, na linaweza kuathiriwa na SIM-swap. Magic links hupotea kwenye vichungi vya spam. Selfie dhidi ya picha iliyosajiliwa inazuia wizi, ni ya papo hapo, na ina bei isiyobadilika.
Matrix ya njia
03 · Ongezeko la ubadilishaji

Acha kupoteza watumiaji wanaorudi mlangoni.

Uwekaji upya wa nywila kwa kawaida hupunguza ~30% ya watumiaji wanaorudi katikati ya mchakato; misimbo ya SMS inaweza kuchukua sekunde 5-90 kuanzia mwanzo hadi mwisho. Re-auth ya selfie hukamilika kwa takriban sekunde mbili, bila ujumbe wa kusubiri na hakuna cha kukumbuka. Matokeo: ongezeko linalopimika katika ubadilishaji wa kuingia kwa watumiaji wanaorudi.
Vigezo vya watumiaji wanaorudi
04 · Inaweza kutumika tena kwenye nyuso mbalimbali

Jisajili mara moja. Kila programu inayotumia Didit, bila malipo.

Funga Reusable Credential kwa kila mtumiaji aliyesajiliwa. Huduma inayofuata inayotumia Didit inayohitaji re-auth hiyo hiyo hutumia credential bila gharama. Mtumiaji anashikilia uthibitisho; programu yako inathibitisha saini. Athari ya mtandao huongezeka kwa kila mteja anayetumia Reusable Credentials.
Moduli ya KYC inayoweza kutumika tena
05 · Kuongezeka kwa hatua inayobadilika

Ruka selfie kwenye kifaa kinachojulikana + IP inayojulikana.

Unganisha na Device & IP Analysis (imejumuishwa kwenye stack ya ishara 200+ za udanganyifu). Mtumiaji anayerudi kwenye kifaa kinachojulikana na Internet Protocol (IP) inayojulikana huruka selfie kabisa. Kifaa kipya kabisa au IP mpya huamsha passive; Tor / Virtual Private Network (VPN) exit kwenye kifaa kipya kabisa huongezeka hadi Active 3D. Mtiririko ule ule, vichochezi mahiri.
Moduli ya Uchambuzi wa Kifaa na IP
06 · Bei ya umma

$0.10 kwa kila uthibitishaji upya. Bei sawa. Duniani kote.

Bei ya umma, hakuna kiwango cha chini, hakuna mkataba. Nenosiri la mara moja la SMS la Marekani Tier-1 linagharimu $0.05-$0.30 kwa kila utumaji na unalipa hata kama mtumiaji hajawahi kupokea msimbo. Uwekaji upya wa nenosiri unagharimu $1-$3 kwa kila tiketi ya usaidizi. Re-auth ya selfie ni $0.10 isiyobadilika na uthibitishaji 500 bila malipo kila mwezi, milele.
Angalia bei
Unganisha

Session moja. Callback moja. Tengeneza token.

Fungua session ya uthibitishaji wa kibayometriki, piga selfie kwenye UI iliyopangishwa, thibitisha uamuzi uliotiwa saini, ingiza mtumiaji.
POST /v3/session/Re-auth
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_reauth",
    "workflow_type": "biometric_authentication",
    "vendor_data": "user-42",
    // base64 enrolment selfie, ≤ 1MB (omit for liveness-only)
    "portrait_image": "/9j/4AAQSkZJRgABAQE..."
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
UI iliyopangishwa inaendesha LIVENESS + FACE_MATCH dhidi ya portrait_image iliyotolewa.nyaraka →
GET /v3/session/{sessionId}/decision/Uamuzi
$ curl https://verification.didit.me/v3/session/<id>/decision/ \
  -H "x-api-key: $DIDIT_API_KEY"

# Returns the re-auth verdict
{
  "status": "Approved",
  "face": { "similarity_score": 0.96 }
}
200OKhali Imeidhinishwa · Inapitiwa · Imekataliwa · Haijakamilika
Thibitisha X-Signature-V2 kwenye webhook iliyosainiwa kwanza.nyaraka →
Ujumuishaji tayari kwa agent

Badilisha nenosiri / SMS / kiungo cha uchawi kwa ombi moja.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent huandaa Didit, hubadilisha callback iliyopo ya mtumiaji anayerudi, na inasafirishwa ndani ya wikiendi.
didit-integration-prompt.md
You are integrating Didit&apos;s selfie-only re-authentication into <my_stack>. Replace password, SMS one-time-password, or magic-link on returning-user surfaces with a sub-2-second face match against the enrolled portrait. Phishing-resistant, no carrier dependency, no SIM-swap surface, no email-delivery delay.

  1. Enrol the user&apos;s portrait ONCE at sign-up (standard Know Your Customer (KYC) session).
  2. On every returning-user sign-in, open a re-auth session that runs Passive Liveness + Face Match 1:1 against the stored portrait. ~2 seconds end-to-end.

Pricing (public):
  - Selfie re-auth: $0.10 per authentication (Sessions API)
  - 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.
  - The user has previously enrolled via a Didit KYC session (the portrait captured during the liveness step is stored automatically, bound to vendor_data).
  - A workflow_id from the Workflow Builder. The workflow MUST contain LIVENESS, and the session is opened with workflow_type = "biometric_authentication".

STEP 1 — Open a re-auth session

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<your biometric_authentication workflow>",
      "workflow_type": "biometric_authentication",
      "vendor_data": "<the same user id used at enrolment>",
      "callback": "https://<your-app>/reauth/callback",
      "metadata": {
        "purpose": "returning_user_signin",
        "device_id": "<optional, your device fingerprint>",
        "from_ip": "<optional, the request IP>"
      },
      "portrait_image": "<base64 JPEG of the user's enrolment selfie, ≤ 1 MB — REQUIRED when the workflow has FACE_MATCH active; OMIT for liveness-only mode>"
    }

  Response: 201 Created with the hosted session_url. Redirect the user. The hosted UI opens the front camera, captures one passive frame, runs Liveness + Face Match 1:1 against the user&apos;s enrolled portrait, returns the verdict in sub-2-seconds.

STEP 2 — Read the signed verdict on the webhook

  Body (excerpted for a passing re-auth):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your user id>",
      "status": "Approved",
      "liveness": {
        "status": "Approved",
        "method": "PASSIVE",
        "score": 96
      },
      "face": {
        "status": "Approved",
        "similarity_score": 0.96
      }
    }

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

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

STEP 3 — Branch your sign-in logic on the verdict

  Approved      → mint your session token, sign the user in.
  Declined      → block sign-in; fall back to a higher-friction recovery (support contact / full KYC re-do).
  In Review     → hold; route to your operations queue.
  Not Finished  → user abandoned the capture; safe to re-prompt or fall back to a backup factor.

STEP 4 — Adaptive step-up (recommended)

  Pair the selfie with Device & IP Analysis (bundled into the 200+ fraud-signal stack at no extra cost). Adaptive rules to consider:

    Known device + known Internet Protocol (IP)  → skip the selfie, mint a session token.
    Known device + new IP                         → run the selfie (passive).
    New device + new IP                           → run the selfie (passive).
    Tor / Virtual Private Network (VPN) exit +
      new device                                  → escalate to ACTIVE_3D method (motion challenge).

  Implement the branching in your application or in the Workflow Builder via per-session overrides.

CONSTRAINTS
  - Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
  - Feature enum is UPPERCASE: LIVENESS, FACE_MATCH, IP_ANALYSIS, ID_VERIFICATION, AML, AGE_ESTIMATION.
  - 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). The user can request deletion via the standard data-subject-request path.

PRO TIPS
  - Bind a Reusable Credential to each enrolled user. The next Didit-powered surface that needs the same gate consumes the credential at zero cost.
  - Keep a fallback factor (password, magic link, support recovery) for users who cannot complete the selfie — accessibility, device camera failure, religious head covering, etc.

Read the docs:
  - https://docs.didit.me/core-technology/biometric-auth/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.
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

Thibitisha namba

Thibitisha namba
  • ~2s
    Uthibitishaji upya kamili, kutoka kunasa selfie hadi uamuzi uliosainiwa kwenye Android ya kiwango cha chini.
  • $0.00
    Kwa kila uthibitishaji upya, bei tambarare. Chini ya SMS ya Marekani ya nenosiri la mara moja na tiketi ya usaidizi ya kuweka upya nenosiri ya $1+.
  • 0
    Nenosiri za kuiba, misimbo ya kuiba, SIM za kubadilisha, viungo vya kuruka.
  • 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 "selfie-only re-auth"?
A sign-in flow where the only thing the user does is take a selfie. No password to type, no Short Message Service (SMS) code to wait for, no magic link to fetch from email. The selfie is matched against the user's enrolled portrait, captured during their original Know Your Customer (KYC) session, and a session token is minted in roughly two seconds.
Why are passwords still a problem in 2026?

Three reasons that have not improved:

  • People forget them. Industry surveys put password-reset rate at roughly 5-10% of monthly active users for most consumer apps. Each reset is a $1-$3 support ticket.
  • People reuse them. A breach on any one site exposes credentials reused everywhere else. Credential-stuffing attacks remain the #1 account-takeover vector.
  • People type them on the wrong site. Phishing pages cost the user the credential the moment they hit Enter.
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.

Why is this faster than Short Message Service one-time-password (SMS OTP)?

SMS one-time-password has a delivery tail of 5 to 90 seconds depending on carrier, country, and time of day. Even in the best case, the user waits, switches apps, copies a 6-digit number, switches back, pastes it, and hits submit, total time-to-signed-in is 15 to 120 seconds.

A selfie is one tap, one camera frame, one verdict, roughly 2 seconds end-to-end with no app switch, no copy/paste, no message that never arrives.

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 integration actually look like?

It's a drop-in for any existing returning-user callback contract.

  • POST /v3/session/ with workflow_type: "biometric_authentication" and the same vendor_data you used at enrolment.
  • Redirect the user to the returned session_url.
  • Verify the X-Signature-V2 Hash-based Message Authentication Code (HMAC) header on the webhook.
  • Branch on status, Approved mints your token, Declined blocks and falls back, In Review routes to ops, Not Finished re-prompts.

Most teams ship it in a weekend. Full agent-pastable prompt is above; Model Context Protocol (MCP) server speaks both surfaces.

How do you handle the user's face data?

Data minimisation by default. The selfie is processed in memory, the verdict and similarity_score persist, and the raw image is deleted unless retention is explicitly enabled. The enrolled portrait is stored as an irreversible face template, a one-way hash you cannot reconstruct the original face from.

We never sell, share, or train third-party models on a customer's biometric data. End users can request deletion of their template at any time via the standard data-subject-request path.

What happens if the user's face has changed?

Face Match 1:1 is resilient to moderate appearance change, haircut, beard, glasses, lighting, makeup, modest ageing. The similarity score returned per re-auth reflects the model's confidence.

For users who drift outside the auto-approve threshold (dramatic weight change, surgery, multi-year ageing without a refresh), the verdict returns In Review and routes to your operations queue. A 10-second re-enrolment session refreshes the template, and the next re-auth uses the new portrait.

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