Skip to main content
Didit Raih $7,5 Juta untuk Membangun Infrastruktur Identitas dan Fraud
Didit
Autentikasi Biometrik

Ganti SMS 2FA.
Dengan wajah. Dalam satu detik.

Re-autentikasi tanpa password yang mudah diintegrasikan untuk pengguna kembali. Tanpa biaya SMS, tanpa risiko SIM-swap, tanpa ketergantungan operator. Menggunakan mesin iBeta Level 1 PAD (presentasi deteksi serangan) yang sama dengan saat pendaftaran. $0.10 per autentikasi, 500 gratis/bulan.

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

Dipercaya oleh 2.000+ organisasi di seluruh dunia.

Didit Biometric Authentication, re-autentikasi liveness pasif dalam waktu kurang dari dua detik.

Login anti-phishing

Faktor inherence.
Di bawah 1 detik di Android.

Gunakan kembali identitas terverifikasi dari pendaftaran untuk mengautentikasi pengguna yang kembali. Anti-SIM swap, anti-phishing, $0.10 per panggilan, lebih murah dari SMS bolak-balik di pasar mana pun.

Cara kerjanya

Dari pendaftaran hingga pengguna terverifikasi dalam empat langkah.

  1. Langkah 01

    Buat workflow-nya

    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

    Integrasikan

    Integrasikan secara native dengan SDK Web, iOS, Android, React Native, atau Flutter 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 seluler, dan aksesibilitas. Saat pengguna berada dalam alur, kami menilai 200+ sinyal fraud secara real-time dan memverifikasi setiap bidang terhadap sumber data otoritatif. Hasilnya kurang dari dua detik.

  4. Langkah 04

    Anda menerima hasilnya

    Webhook yang ditandatangani secara 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 kelola kasus sesuai keinginan Anda.

Dibuat untuk developer · Dibuat untuk melawan fraud · Desain terbuka

Enam kapabilitas. Satu workflow. biometric_authentication.

Setiap kapabilitas di bawah ini adalah toggle pada jenis workflow yang sama. Tanpa tingkatan upsell, tanpa SKU terpisah, tanpa panggilan add-on. Aktifkan per workflow, lalu buat sesi dengan satu panggilan.
01 · Step-up 2FA

Pengganti langsung untuk two-factor berbasis SMS.

Picukan Biometric Authentication pada setiap tindakan sensitif, transfer bernilai tinggi, reset kata sandi, penarikan besar, login perangkat baru. Tanpa biaya operator, tanpa risiko SIM-swap, tanpa phishing OTP. UI yang di-host sama dengan alur pendaftaran Anda, pengguna tidak perlu mempelajari kontrol baru. $0.10 per autentikasi, lebih murah dari SMS dan kebal terhadap setiap vektor serangan SMS.
Autentikasi bertingkatPOST /v3/session/
SMS 2FA
Kode 6 digit
  • SIM swap
  • Tagihan operator
  • Phishing
Autentikasi Biometrik
Pengecekan wajah
  • Tanpa eksposur SIM
  • $0.10 per auth
  • Anti-phishing
Pengganti drop-in. Engine bersertifikasi iBeta yang sama dengan yang Anda gunakan saat pendaftaran.
02 · Dua mode

Liveness-only atau liveness plus face match. Pilih per workflow.

Liveness-only untuk pemeriksaan kehadiran gesekan rendah, atau liveness plus face match untuk pengikatan identitas penuh terhadap potret pendaftaran yang tersimpan. Keduanya mengembalikan JSON yang sama. Beralih mode dengan mengedit workflow, tanpa perubahan klien, tanpa endpoint baru, tetap $0.10 per autentikasi.
Dua mode · Satu workflowbiometric_authentication
  • Hanya livenesspengecekan kehadiran
    fitur: [LIVENESS]
    Memastikan ada manusia sungguhan. Gesekan paling rendah.
  • Liveness + Face Matchpengikatan identitas
    fitur: [LIVENESS, FACE_MATCH]
    Menambahkan pengikatan portrait_image ke pendaftaran. Keamanan tertinggi.
Toggle per workflow. workflow_id yang sama. $0.10 per autentikasi yang sama.
03 · Verifikasi kurang dari 2 detik

Kurang dari satu detik latensi yang dirasakan saat login.

Inference yang dilayani di edge, tanpa unduhan model, tanpa asumsi akselerasi on-device, tanpa pengalaman yang menurun pada Android murah. Pengambilan ~0.3 detik, liveness kurang dari satu detik, face match ~0.5 detik, webhook keluar kurang dari 2 detik end-to-end. Lebih cepat dari kode SMS, dan pengguna tidak pernah meninggalkan aplikasi Anda.
Latensi loginend-to-end < 2 d
  • Capture · auto-frame0.32 s
  • Liveness · passive0.81 s
  • Face match · 1:10.42 s
  • Approved · webhook out1.65 s
Inferensi yang disajikan di edge. Tanpa unduhan model. Tanpa round-trip operator.
04 · Pertahanan terhadap pengambilalihan akun

iBeta Level 1 terhadap katalog serangan lengkap.

Bersertifikat independen di PAD (presentation attack detection) Level 1 oleh iBeta, standar yang dikutip oleh NIST dan Open Identity Exchange. Mengalahkan replay selfie curian, deepfake, topeng kertas, topeng silikon dan lateks, serangan morph. Pemicu penolakan keras (wajah yang diblokir, tidak ada wajah terdeteksi, tanda serangan, tidak ada gambar referensi) tetap diberlakukan terlepas dari pengaturan Anda.
Pertahanan terhadap pengambilalihan akuniBeta L1 PAD
  • Deepfake pemilik akunDiblokir
  • Masker silikon atau kertasDiblokir
  • Selfie curian · serangan replayDiblokir
  • Wajah di daftar blokirTolak otomatis
05 · Penggunaan ulang potret

Gunakan kembali potret pendaftaran. Tidak ada yang baru untuk disimpan.

Anda sudah memiliki foto referensi pengguna dari KYC pendaftaran, teruskan pada setiap sesi Biometric Authentication dan kami akan menilai kesamaannya. Penyimpanan template yang sama, infrastruktur default UE yang sama (residency wilayah tertentu pada Enterprise), petugas perlindungan data yang sama. Tanpa re-onboarding, tanpa keputusan penyimpanan tambahan.
Pakai ulang portrait KYCportrait_image
sign-up
Portrait KYC
setiap login
Face Match 1:1
  • skor kemiripan96.2
  • template store yang sama dengan KYCEU AWS
06 · Threshold yang dapat disesuaikan

Threshold kesamaan dan liveness yang dapat dikonfigurasi per workflow.

Peringatan liveness rendah dan face match rendah masing-masing memiliki threshold Review dan threshold Decline yang Anda sesuaikan per aplikasi. Ketat untuk transfer bernilai tinggi, longgar untuk login perangkat baru, semuanya dari editor workflow yang sama di konsol. Katalog peringatan lengkap ada di dokumentasi.
Editor workflow Biometric Authentication Didit Business Console menampilkan threshold liveness dan face match yang dapat dikonfigurasi.
Integrasikan

Dua konfigurasi. Sesi yang sama. Harga yang sama.

Kedua konfigurasi membuat sesi pada workflow Biometric Authentication yang sama. Liveness-only berarti hanya kehadiran, gesekan paling rendah. Liveness plus face match mengikat autentikasi ke potret pendaftaran pengguna yang tersimpan. Beralih dengan mengedit workflow, tanpa perubahan klien.
POST /v3/session/Liveness + Face Match
$ 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_bio_auth",
    "vendor_data": "user-42",
    // base64-encoded reference selfie, ≤ 1MB
    // omit this field for liveness-only mode
    "portrait_image": "/9j/4AAQSkZJRgABAQE..."
  }'
201Dibuat{ "session_url": "verify.didit.me/..." }
Sertakan portrait_image untuk pencocokan wajah; abaikan jika hanya untuk liveness.dokumen →
POST /webhooks/diditLangkah 2 · Terima
// Your endpoint receives a signed payload
app.post("/webhooks/didit", (req, res) => {
  const sig = req.headers["x-signature-v2"];
  const expected = crypto.createHmac("sha256", SECRET)
    .update(req.rawBody).digest("hex");
  if (sig !== expected) return res.sendStatus(401);
  const { status, decision, vendor_data } = req.body;
  // status: Approved | Declined | In Review | ...
  res.sendStatus(200);
});
200OKwebhook_type: "status.updated", status: "Approved"
Webhook real-time dengan tanda tangan HMAC. Verifikasi, parse, dan update database Anda.dokumen →
Integrasi siap agen

Deploy Autentikasi Biometrik dalam satu prompt.

Tempel blok di bawah ini ke Claude Code, Cursor, Codex, Devin, Aider, atau Replit Agent. Isi placeholder my_stack dengan framework, bahasa, dan kasus penggunaan Anda. Agen akan memprovisi Didit, membuat workflow, menghubungkan sesi dan webhook, lalu deploy.
didit-integration-prompt.md
# Didit Biometric Authentication — integrate in 5 minutes

You are integrating Didit's Biometric Authentication module into <my_stack>.
This is a returning-user passwordless re-verification flow — a drop-in
replacement for SMS or email 2FA at high-value actions (large transfers,
password reset, large withdrawals, sensitive setting changes). It is NOT
the first-time KYC sign-up flow — for that, see Didit Liveness at
docs.didit.me/core-technology/liveness/overview.

Every URL, header, and enum value below is canonical — do not paraphrase
or "improve" them.

## 1. Provision an account
- Sign up: https://business.didit.me (no credit card required).
- Or provision programmatically: POST https://apx.didit.me/auth/v2/programmatic/register/
  (returns an API key bound to the workspace + application).

## 2. Create the biometric_authentication workflow (one time)
Biometric Authentication is a workflow_type, not a feature flag. Create
the workflow once, reuse the workflow_id for every authentication.

POST https://verification.didit.me/v3/workflows/
Header: x-api-key: <your-api-key>
Body:
  - workflow_label   (your label, e.g. "step-up-2fa")
  - workflow_type    "biometric_authentication"  (snake_case enum)
  - features         the array
                       [{ feature: "LIVENESS" }]                    (liveness-only mode)
                     OR
                       [{ feature: "LIVENESS" }, { feature: "FACE_MATCH" }]  (face-match mode)
  - liveness_method  "PASSIVE" | "FLASHING" | "ACTIVE_3D"   (PASSIVE recommended for low-friction step-up)

Store the returned workflow_id — you will reuse it on every auth.

## 3. Authenticate a returning user

POST https://verification.didit.me/v3/session/
Header: x-api-key: <your-api-key>
Header: Content-Type: application/json
Body:
  - workflow_id     (from step 2)
  - vendor_data     (your own user id, e.g. "user-42")
  - callback        (optional URL we redirect the user to after capture)
  - metadata        (optional JSON, surfaced back on the webhook)
  - portrait_image  (Base64 JPEG, REQUIRED when the workflow has FACE_MATCH;
                     OMIT for liveness-only mode)

The portrait_image is the stored reference photo from the user's original
KYC verification (you already have it as id_verification.portrait_image in
the original session response). Send it as a Base64-encoded JPEG, max 1 MB.

Response: session_url — redirect the user to it. Didit hosts the capture
(camera, motion prompts, low-light fallback, accessibility) and posts the
verdict back via webhook.

## 4. Webhooks
- Register a webhook destination once via
  POST https://verification.didit.me/v3/webhook/destinations/
  Body: url, subscribed_events: ["session.verified", "session.declined",
                                  "session.review_started"]
- Response includes secret_shared_key — store it.
- Every webhook delivery carries an X-Signature-V2 header you MUST verify
  before trusting the payload.  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.Algorithm:
    1. sortKeys(payload) recursively
    2. shortenFloats (truncate trailing zeros after the decimal point)
    3. JSON.stringify the result
    4. HMAC-SHA256 with the secret_shared_key
    5. Hex-encode, compare to the X-Signature-V2 header.

## 5. Reading the report
The webhook payload (and the GET /v3/session/{id}/decision/ response)
returns the combined biometric_authentication shape:

  status               "Approved" | "Declined" | "Not Finished"
  workflow_id          string
  session_id           uuid
  session_number       integer
  vendor_data          your user id
  liveness:
    status             "Approved" | "Declined" | "Not Finished"
    method             "PASSIVE" | "FLASHING" | "ACTIVE_3D"
    score              number 0-100
    reference_image    signed URL to the captured selfie (expires in 1 hour)
    video_url          signed URL (FLASHING and ACTIVE_3D only, expires in 1 hour)
    warnings           array
  face_match:                     (only present in face-match mode)
    status             "Approved" | "Declined" | "Not Finished"
    score              number 0-100 (similarity %)
    source_image       signed URL to the captured selfie
    target_image       signed URL to the supplied portrait_image
    warnings           array

Overall status is "Approved" only when liveness.status == "Approved" AND
(face_match is absent OR face_match.status == "Approved").

Auto-decline triggers (always enforced by Didit, not configurable):
  FACE_IN_BLOCKLIST, NO_FACE_DETECTED, LIVENESS_FACE_ATTACK, NO_REFERENCE_IMAGE

Configurable risks (action per workflow — Decline, Review, or Approve):
  LOW_LIVENESS_SCORE, LOW_FACE_MATCH_SIMILARITY

## 6. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- workflow_type is snake_case: biometric_authentication.
- Feature enums inside the workflow are UPPERCASE: LIVENESS, FACE_MATCH.
- Liveness 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).
- Always verify webhook signatures before trusting payload data.
- Status casing matches exactly: "Approved", "Declined", "In Review",
  "Not Finished" (title-cased, space-separated).
- portrait_image is Base64 JPEG, max 1 MB, required only in face-match mode.

## 7. Pricing reference (public)
- Biometric Authentication: $0.10 per authentication (passwordless re-auth).
- 500 free authentications every month, forever, on every account.
- For the original sign-up KYC, see https://didit.me/pricing (full KYC
  bundle is $0.33 per onboarded user, which includes Liveness + Face Match +
  ID Verification + Device & IP Analysis).

## 8. When to use this versus Liveness directly
- First-time KYC sign-up: use Liveness (the feature) inside an ID
  Verification workflow. See docs.didit.me/core-technology/liveness/overview.
- Step-up at sensitive actions (transfer, password reset, large
  withdrawal): use this Biometric Authentication workflow.
- High-volume passive monitoring (any login): use this workflow with
  liveness-only mode (no portrait_image) — fastest, lowest friction.

## 9. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Test images: deterministic synthetic faces returned in sandbox
  (Approved by default; trigger Declined by sending the canonical "spoof"
  test image).
- Switch to live: flip the application's environment toggle in console.

When in doubt: https://docs.didit.me/core-technology/biometric-auth/overview
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-angka bukti

Angka-angka bukti
  • iBeta L1
    Deteksi serangan presentasi yang tersertifikasi secara independen.
  • <0s
    Verifikasi autentikasi end-to-end per sesi, disajikan di edge.
  • $0.00
    Per autentikasi, lebih murah dari SMS dan kebal terhadap semua vektor serangan SMS.
  • 0
    Autentikasi gratis setiap bulan, selamanya, 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 Biometric Authentication and how is it different from Liveness?
Biometric Authentication is the returning-user re-auth surface, a drop-in replacement for SMS or email two-factor authentication (2FA) at sensitive actions (high-value transfer, password reset, large withdrawal, new-device login). It is a workflow_type (snake-case: biometric_authentication) that composes the LIVENESS feature with an optional FACE_MATCH feature. Liveness on its own is the sign-up capability, see /products/liveness for the first-time know-your-customer (KYC) flow. Both use the same iBeta Level 1 Presentation Attack Detection (PAD)-certified engine, so the model your user passed at onboarding is the same model checking them at every login.
What is the response shape?
The combined report returns status (Approved, Declined, Not Finished), a liveness block with status, method (PASSIVE, FLASHING, or ACTIVE_3D), score 0-100, reference_image, video_url, and warnings, plus a face_match block (only present when the workflow has FACE_MATCH) with status, score 0-100, source_image, target_image, and warnings. The signed image and video URLs expire after 60 minutes. Overall status is Approved only when liveness is approved AND (face match is absent OR face match is approved).
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 account-takeover attacks does it block?
Didit Biometric Authentication is iBeta Level 1 PAD certified against the full ISO/IEC 30107-3 attack catalog, printed photos, screen replays, paper masks, silicone masks, latex masks, morph attacks, AI-generated deepfakes of the account owner, and stolen-selfie replays. Four risks are auto-decline regardless of your settings: FACE_IN_BLOCKLIST, NO_FACE_DETECTED, LIVENESS_FACE_ATTACK, and NO_REFERENCE_IMAGE. Configurable warnings, LOW_LIVENESS_SCORE and LOW_FACE_MATCH_SIMILARITY, let you tune the review and decline thresholds per application.
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.

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