Skip to main content
Didit Raih $7,5 Juta untuk Membangun Infrastruktur Identitas dan Fraud
Didit
Penyalahgunaan Multi-akun

Tangkap sybil dengan Face Search 1:N. Satu orang, satu akun.

Cari setiap selfie pendaftaran baru terhadap galeri selfie yang sebelumnya disetujui. Kecocokan berarti orang yang sama sudah memiliki akun. Pencarian Wajah gratis; 500 verifikasi gratis setiap bulan.

Didukung oleh
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

Dipercaya oleh 2.000+ organisasi di seluruh dunia.

Tumpukan deteksi sybil abstrak gelap, empat panel kaca gelap transparan mengambang dalam perspektif 3D di atas latar belakang hitam pekat, dihubungkan oleh garis vertikal Didit Blue yang bercahaya dan dibingkai oleh braket pemindai yang bersinar. Setiap panel membawa satu motif abstrak putih pucat kecil (satu wajah, wajah berulang, jaringan node, kluster akun yang terhubung).

Yang tidak bisa ditangkap email dan telepon

Email murah. Telepon murah. Satu wajah, setiap saat.

Alias email dan SIM burner hanya butuh beberapa sen. Wajah manusia adalah satu-satunya identitas yang tidak bisa dirotasi oleh "petani" sybil. Face Search 1:N terhadap galeri selfie sebelumnya membuat orang yang sama tidak mungkin bersembunyi. Gratis per pencarian, 500 verifikasi gratis setiap bulan.

Cara kerjanya

Dari pendaftaran hingga pengguna terverifikasi dalam empat langkah.

  1. Langkah 01

    Buat workflow

    Pilih pemeriksaan yang Anda inginkan, ID, liveness, face match, sanksi, alamat, usia, telepon, email, pertanyaan kustom. Seret ke dalam alur di dashboard, atau posting alur yang sama ke API kami. Buat cabang berdasarkan kondisi, jalankan A/B test, tanpa perlu coding.

  2. Langkah 02

    Integrasi

    Integrasikan secara native dengan Web, iOS, Android, React Native, atau Flutter SDK kami. Redirect ke halaman yang di-host. Atau cukup kirim tautan ke pengguna Anda, via email, SMS, WhatsApp, di mana saja. Pilih yang sesuai dengan stack Anda.

  3. Langkah 03

    Pengguna melewati alur

    Didit meng-host kamera, isyarat pencahayaan, hand-off mobile, dan aksesibilitas. Saat pengguna berada dalam alur, kami menilai 200+ sinyal fraud secara real-time dan memverifikasi setiap bidang terhadap sumber data otoritatif. Hasil dalam waktu kurang dari dua detik.

  4. Langkah 04

    Anda menerima hasilnya

    Webhook terautentikasi real-time menjaga database Anda tetap sinkron saat pengguna disetujui, ditolak, atau dikirim untuk ditinjau. Lakukan polling API sesuai permintaan. Atau buka konsol untuk memeriksa setiap sesi, setiap sinyal, dan mengelola kasus sesuai keinginan Anda.

Dibuat untuk resep · Harga seperti infrastruktur

Enam pemeriksaan. Satu hasil verifikasi terautentikasi. Gratis per face search.

Pertahanan multi-akun adalah komposisi, pencarian, liveness, tautan antar-akun, audit trail. Aktifkan setiap modul per workflow di Workflow Builder.
01 · Bentuk masalah

Ketika orang yang sama muncul dua kali.

Sybil airdrop, siklus pembayaran referral, multi-akun iGaming yang melewati pengecualian diri, kluster ulasan palsu marketplace, vote stuffing DAO, penumpukan bonus selamat datang pada pendaftaran neobank atau broker. Workflow Builder yang sama melindungi setiap varian.
Modul Workflow Orchestrator
02 · Gerbang Face Search

Cari setiap wajah baru di galeri.

Face Search 1:N mengindeks selfie yang diambil saat pendaftaran dan mencarinya terhadap galeri selfie yang sebelumnya disetujui di bawah akun Anda. Mengembalikan kandidat teratas dengan skor kemiripan. Gratis per pencarian, tanpa biaya per panggilan. Pencarian vektor mengembalikan hasil dalam waktu kurang dari dua detik.
Modul Face Search 1:N
03 · Kluster kecocokan

Wajah yang sama, sudah ada di database.

Ketika pencarian menemukan kecocokan, payload webhook membawa setiap session_id sebelumnya, referensi pengguna yang cocok, dan skor kemiripan. Sesuaikan ambang batas keras/lunak per workflow, default 0.85 = Ditolak, 0.75–0.85 = Dalam Peninjauan, < 0.75 = Disetujui.
Cara kerja Face Search
04 · Sinyal tautan antar-akun

Perangkat yang sama. IP yang sama. Metode pembayaran yang sama.

Gabungkan Device & IP Analysis ($0.03 / panggilan) dalam workflow yang sama. Payload keputusan menampilkan fingerprint perangkat, alamat Internet Protocol (IP), Autonomous System Number (ASN), dan negara. Gabungkan dengan hash instrumen pembayaran dari back-end Anda untuk mengelompokkan sybil sebelum face search mengonfirmasi.
Modul Analisis Perangkat & IP
05 · Jangkar identitas yang dapat digunakan kembali

Satu identitas. Banyak produk. Tanpa kloning.

KYC yang dapat digunakan kembali memungkinkan pengguna yang sah untuk masuk kembali ke produk Anda yang lain dengan kredensial yang sebelumnya diverifikasi tanpa biaya, itu adalah penggunaan yang disengaja, bukan penyalahgunaan. "Petani" sybil tidak dapat memutar ulang kredensial yang sama di akun baru karena face search masih mengacu pada satu identitas yang dikeluarkan.
Modul KYC yang bisa dipakai ulang
06 · Keputusan webhook terautentikasi

Verifikasi tervalidasi. Daftar kecocokan lengkap sebagai audit trail.

Webhook terautentikasi tiba dengan hasil verifikasi, Disetujui, Dalam Peninjauan, Ditolak, ditambah daftar lengkap session_id yang cocok dan skor kemiripan. Verifikasi X-Signature-V2 dengan Hash-based Message Authentication Code (HMAC) SHA-256 sebelum membaca. Daftar kecocokan adalah audit trail untuk setiap sengketa.
Referensi Webhook
Integrasi

Satu sesi. Satu hasil verifikasi terautentikasi. Daftar kecocokan ikut disertakan.

Buka pendaftaran. Baca hasil verifikasi yang terautentikasi. Daftar kecocokan face-search ada di payload, blokir duplikatnya, catat klusternya.
POST /v3/session/Face Search
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflow_id": "wf_sybil_gate",
    "vendor_data": "signup-A4",
    "metadata": { "surface": "airdrop_claim" }
  }'
201Dibuat{ "session_url": "verify.didit.me/..." }
Jangan buat akun sampai webhook mendarat status: Approved.dokumen →
POST /webhooks/diditDaftar kecocokan
// X-Signature-V2 verified upstream
if (payload.status === "Declined") {
  logCluster(payload.face_search.matches);
  blockSignup(payload.vendor_data);
} else if (payload.status === "Dalam Peninjauan") {
  queueForAnalyst(payload);
}
200OKstatus Disetujui · Ditolak · Dalam Peninjauan · Belum Selesai
Verifikasi X-Signature-V2 sebelum membaca payload.dokumen →
Integrasi siap agen

Kirim Face Search 1:N sybil-gate dalam satu prompt.

Tempel ke Claude Code, Cursor, Codex, Devin, Aider, atau Replit Agent. Isi stack Anda. Agent akan menyusun workflow, membuka sesi, membaca daftar kecocokan, dan memblokir duplikat.
didit-integration-prompt.md
You are integrating Didit Face Search 1:N to catch the same human opening many accounts on your platform — sybil airdrops, referral payout cycles, sign-up bonus stacking, iGaming multi-accounting that bypasses self-exclusion, marketplace fake-review clusters. One API call. One signed webhook. One decision.

WHY THIS SHAPE
  - Email, phone, device, IP can all be rotated cheaply. A human face cannot.
  - Every new sign-up captures one Passive Liveness selfie. Didit searches that selfie against the gallery of prior approved selfies under your account. A high-similarity match means the same person already has an account.
  - Face Search 1:N itself is FREE on every session — no per-search fee. Only the surrounding bundle (ID + Passive Liveness + AML) carries the usual cost. Use the full Know Your Customer (KYC) bundle on sign-up or the Passive Liveness + Face Search subset, depending on what the product needs.

PRE-REQUISITES
  - Production API key from https://business.didit.me (sandbox key in 60 seconds, no credit card).
  - A webhook endpoint with HMAC SHA-256 verification of the X-Signature-V2 header using your webhook secret.
  - A Workflow Builder workflow that contains the Face Search 1:N module. Compose it with Passive Liveness so an attacker cannot upload a still photo of the target.
  - Define what a "match" means for your product. Default: similarity ≥ 0.85 = Declined. 0.75–0.85 = In Review. < 0.75 = Approved.

STEP 1 — Open the sign-up session
  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<wf id with Face Search 1:N + Passive Liveness>",
      "vendor_data": "<your new-account id, max 256 chars>",
      "callback": "https://<your-app>/sybil-gate/callback",
      "metadata": {
        "surface": "airdrop_claim",
        "campaign": "<your campaign id>"
      }
    }

  Response: 201 Created with a hosted session URL. Redirect inline (web) or open in a Software Development Kit (SDK) webview (mobile). The new account stays UNCREATED on your side until the signed webhook lands.

STEP 2 — Read the signed webhook
  Didit POSTs the verdict. Verify X-Signature-V2 (HMAC SHA-256 of the raw body) BEFORE reading the JSON.

  Payload (excerpted, match case):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your new-account id>",
      "status": "Declined",
      "face_search": {
        "matches": [
          { "session_id": "sess-9182", "similarity": 0.96, "vendor_data": "user-A1" },
          { "session_id": "sess-7733", "similarity": 0.94, "vendor_data": "user-A2" }
        ]
      }
    }

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

STEP 3 — Branch the sign-up
  Approved   → no gallery match. Create the account.
  In Review  → soft match (similarity in your grey-zone band). Queue for human review.
  Declined   → hard match (similarity above your hard threshold). Block, log the matched session_id list as the audit trail.

STEP 4 — Cross-account link signals (optional but cheap)
  Compose Device & IP Analysis ($0.03 / call) in the same workflow. The decision payload surfaces device fingerprint, IP, Autonomous System Number (ASN), country, and city. Combine with your own payment-instrument hash and you can cluster sybils even before the face search confirms.

STEP 5 — Reusable KYC for legitimate cross-product re-entry
  If the user is supposed to reuse one identity across multiple products you own, Reusable KYC lets them replay a previously verified credential at no cost. That is different from sybil abuse — reuse is intentional and you control the issuance.

WEBHOOK EVENT NAMES
  - Sessions: standard session webhook. One endpoint, status field tells you the lifecycle.
  - Verify X-Signature-V2 (HMAC SHA-256) on every payload.

WHAT IT BLOCKS
  - Sybil airdrop / token claims (one person · many wallets)
  - Self-referral payout cycles (sign-up bonus farms)
  - iGaming multi-accounting that bypasses self-exclusion
  - Marketplace fake-review clusters from a single human
  - DAO and community-vote stuffing
  - Welcome-bonus stacking on neobank / brokerage sign-ups

CONSTRAINTS
  - Session statuses use Title Case With Spaces. Never UPPER_SNAKE_CASE for session verdicts — that's the Transactions API.
  - Face Search 1:N WITHOUT Passive Liveness lets an attacker upload a still photo of the target. Always compose them together.
  - Thresholds are tunable per workflow. Start at 0.85 hard / 0.75 soft and adjust based on your false-positive tolerance.
  - The gallery is scoped to your account — no cross-customer leakage by design.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/core-technology/face-search/overview
  - https://docs.didit.me/core-technology/liveness/overview
  - 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.
Butuh konteks lebih? Lihat dokumentasi modul lengkapnya.docs.didit.me →
Dirancang untuk kepatuhan

Buka negara baru dengan satu klik. Kami yang mengerjakan bagian sulitnya.

Kami membuka anak perusahaan lokal, mengamankan lisensi, menjalankan pengujian penetrasi, mendapatkan sertifikasi, dan menyelaraskan dengan setiap regulasi baru. Untuk meluncurkan verifikasi di negara baru, cukup aktifkan tombol. 220+ negara sudah aktif, diaudit dan diuji penetrasi setiap kuartal, satu-satunya penyedia identitas yang secara formal disebut oleh pemerintah negara anggota Uni Eropa lebih aman daripada verifikasi langsung.
Baca dossier keamanan & kepatuhan
Sandbox keuangan UE
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
Keamanan informasi · 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
Selaras dengan UE secara desain

Angka pembuktian

Angka pembuktian
  • Free
    Per Face Search 1:N, tanpa biaya per panggilan. Hanya bundle di sekitarnya yang dikenakan biaya.
  • <0s
    Verifikasi vector-search end-to-end di Android entry-level.
  • iBeta L1
    Passive Liveness di setiap selfie, tanpa bypass foto diam.
  • 0
    Verifikasi gratis setiap bulan, di setiap akun.
Tiga tingkatan, satu daftar harga

Mulai gratis. Bayar sesuai penggunaan. Skala ke Enterprise.

500 verifikasi gratis setiap bulan, selamanya. Pay-as-you-go untuk produksi. Kontrak kustom, data residency, dan SLA (Service Level Agreements) untuk Enterprise.
Gratis

Gratis

$0 / bulan. Tidak perlu kartu kredit.

  • Paket KYC gratis (Verifikasi ID + Passive Liveness + Face Match + Analisis Perangkat & IP), 500 / bulan, setiap bulan
  • User yang masuk daftar hitam
  • Deteksi Duplikat
  • 200+ sinyal fraud di setiap sesi
  • KYC yang dapat digunakan kembali di seluruh jaringan Didit
  • Platform Manajemen Kasus
  • Workflow Builder
  • Dokumentasi publik, sandbox, SDK, server MCP (Model Context Protocol)
  • Dukungan komunitas
Paling populer
Bayar sesuai pemakaian

Berbasis Pemakaian

Bayar hanya untuk yang kamu pakai. 25+ modul. Harga per modul transparan, tanpa biaya minimum bulanan.

  • Full KYC seharga $0.33 (ID + Biometrik + IP / Perangkat)
  • 10.000+ dataset AML, sanksi, PEP, media yang merugikan
  • 1.000+ sumber data pemerintah untuk Database Validation
  • Transaction Monitoring seharga $0.02 per transaksi
  • Live KYB seharga $2.00 per bisnis
  • Wallet Screening seharga $0.15 per pemeriksaan
  • Alur verifikasi whitelabel, brand kamu, infrastruktur kami
Enterprise

Enterprise

MSA & SLA kustom. Untuk volume besar dan program yang diatur.

  • Kontrak tahunan
  • MSA, DPA, dan SLA kustom
  • Saluran Slack dan WhatsApp khusus
  • Peninjau manual sesuai permintaan
  • Ketentuan reseller dan white-label
  • Fitur eksklusif dan integrasi partner
  • CSM khusus, tinjauan keamanan, dukungan kepatuhan

Mulai gratis → bayar hanya saat pemeriksaan berjalan → buka Enterprise untuk kontrak kustom, SLA, atau data residency.

FAQ

Pertanyaan umum

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 a sybil attack?

A sybil attack is when one human creates many accounts to pretend to be many humans. The name comes from a 1973 case study of a patient with dissociative identity disorder. In product terms it shows up as one person claiming an airdrop ten times, stacking ten sign-up bonuses, or stuffing a leaderboard with ten "different" wins.

The attack works because every other identifier, email, phone, device, Internet Protocol (IP) address, can be rotated for cents. The one identifier that cannot be cheaply rotated is the attacker's own face.

Why is email and phone defence not enough?

A sybil farmer in 2026 can buy:

  • 10,000 throwaway email aliases for under \$50
  • 10,000 Subscriber Identity Module (SIM) cards or virtual numbers for under \$200
  • A residential-proxy Virtual Private Network (VPN) subscription for under \$100 / month
  • A second-hand or virtualised device pool for a few hundred dollars

The whole operation pays back if a single sybilled airdrop or bonus is worth more than the kit. Face Search 1:N takes the face, the one thing the farmer cannot cheaply duplicate, and turns it into the unique key.

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.

How is Face Search 1:N different from Face Match 1:1?

Different question, different math.

  • Face Match 1:1 asks "is this the same person as the one selfie I have on file?" Used at account-takeover step-up, where the comparison target is the user's own enrollment portrait.
  • Face Search 1:N asks "is this person already in my gallery of N enrolled humans?" Used at sign-up, to surface duplicates across all prior accounts.

The 1:1 check costs \$0.05 per match. Face Search 1:N is free per search, only the surrounding bundle (ID Verification, Passive Liveness) carries cost.

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 do I tune the match thresholds?

Face Search 1:N returns a similarity score between 0 and 1 per match. You set two thresholds per workflow:

  • Hard threshold (default 0.85): scores at or above → Declined. Auto-block the sign-up.
  • Soft threshold (default 0.75): scores between soft and hard → In Review. Queue for analyst.
  • Below soft: Approved. No duplicate found.

Start at the defaults. If you see too many false positives (real twins, real strong family resemblance), raise the hard threshold. If duplicates slip through, lower it. Tune in the Workflow Builder, no redeploy needed.

What does the recipe cost?

Two line items per new sign-up:

  • Passive Liveness: \$0.10 per check
  • Face Search 1:N: \$0.00 per search (free, no per-call fee)

Around \$0.10 per protected sign-up. Add Device & IP Analysis at \$0.03 if you want device + IP link signals for clustering. The first 500 verifications every month are free on every account.

No minimums, no annual commitment, no per-seat pricing.

Which industries run this recipe?

Anywhere multiplying accounts has economic value:

  • Web3 / crypto airdrops, to keep one human from claiming an allocation N times
  • Marketplace + creator-economy referral programs, to kill self-referral payout cycles
  • iGaming, to enforce self-exclusion that the user themselves requested
  • Fintech / neobank welcome bonuses, to prevent the same human stacking ten sign-up rewards
  • DAO / community voting, to make one-vote-per-human stick
  • Marketplace review systems, to kill 5-star clusters from one human

One integration, every surface.

Infrastruktur untuk identitas dan fraud.

Satu API untuk KYC, KYB, Transaction Monitoring, dan Wallet Screening. Integrasi dalam 5 menit.

Minta AI untuk merangkum halaman ini