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

Verifikasi silang identitas apa pun.
Terverifikasi dengan sumber yang menerbitkannya.

Verifikasi silang nama, nomor ID, atau alamat dengan sumber yang menerbitkannya, 1.000+ registri, biro, dan telco melalui satu panggilan. Mulai dari $0.05 per pemeriksaan, 500 gratis/bulan.

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

Dipercaya oleh 2.000+ organisasi di seluruh dunia.

Validasi Database Didit, kartu identitas nasional dicocokkan dengan registri di dalam negeri.

Registri pemerintah

Validasi ID dengan
database nasional terkini.

Konfirmasi identitas seseorang dan ID mereka dengan catatan resmi, SSN, RFC, CPF, Aadhaar, NIN, dan 60+ registri nasional lainnya. Harga dipublikasikan per negara.

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

    Integrasikan

    Integrasikan secara native dengan Web, iOS, Android, React Native, atau Flutter SDK kami. Redirect ke halaman yang di-host. Atau cukup kirim link 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, mobile hand-off, dan aksesibilitas. Saat pengguna berada dalam alur, kami menilai 200+ sinyal fraud secara real-time dan memverifikasi setiap field dengan 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 · Dibangun untuk melawan fraud · Desain terbuka

Enam kapabilitas. Satu feature flag. DATABASE_VALIDATION.

Setiap kapabilitas di bawah ini adalah toggle pada modul yang sama. Tanpa tingkatan upsell, tanpa paket terpisah, tanpa panggilan add-on, aktifkan layanan yang Anda inginkan per workflow.
Baca dokumentasiDapatkan API key
01 · Katalog sumber

1.000+ sumber otoritatif. Satu panggilan.

Registri sipil, otoritas pajak, daftar pemilih, biro kredit, telco, catatan pengadilan, dan verifikasi alamat, semuanya dapat diakses melalui satu endpoint. Sumber baru ditambahkan setiap bulan dan muncul secara otomatis.
02 · Kategori sumber

Registri. Biro. Telco. Pengadilan. Alamat.

Pilih domain data yang sesuai dengan fraud yang Anda lawan. Pemeriksaan registri sipil mengalahkan identitas sintetis. Pemeriksaan biro kredit mengkonfirmasi riwayat. Pemeriksaan telco mengkonfirmasi jalur aktif. Verifikasi alamat membuktikan domisili.
03 · Orkestrasi per sumber

Jalankan layanan secara paralel. Kepercayaan tertinggi menang.

Aktifkan sejumlah layanan per negara dan Didit akan menjalankannya secara paralel. Satu sumber yang mengkonfirmasi adalah sinyal kuat, dua sumber independen yang saling menguatkan adalah putusan terkuat yang dapat kami berikan.
04 · Bentuk laporan

Pencocokan per field. Data sumber. Skor biometrik.

Setiap sumber mengembalikan putusan per field, kode hasil, dan catatan registri yang sudah dibersihkan, nama lengkap, tanggal, foto, tanda tangan, dan skor face-match pada layanan biometrik seperti RENAPER Argentina dan Tribunal Electoral Panama.
05 · Cakupan regional

Amerika Latin, Spanyol, dan 45+ negara.

19 registri sipil yang terintegrasi langsung di seluruh Amerika Latin dan Spanyol. 156 dataset di 45+ negara lainnya melalui jaringan identitas global. Integrasi baru biasanya aktif dalam dua hingga tiga minggu berdasarkan permintaan.
06 · Pembayaran variabel per panggilan

Mulai $0.05 per cek. Tanpa minimum. 500 gratis.

Ditagih hanya untuk query yang berhasil. Tingkat termurah $0.05 (Republik Dominika). Tingkat registri pemerintah standar $0.20 (Argentina, Brasil, Meksiko, Spanyol, Kolombia, Peru, Chili, dan lainnya). Layanan yang dilewati tidak pernah ditagih.
Integrasikan

Dua endpoint. JSON yang sama. Katalog yang sama.

Biarkan Didit menangkap ID dan menarik field secara otomatis, atau kirim data identitas langsung jika Anda sudah memilikinya. Bentuk JSON yang sama saat keluar.
POST /v3/session/Hosted UI
$ 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_db_validation",
    "vendor_data": "user-42"
  }'
201Dibuat{ "session_url": "verify.didit.me/..." }
Didit mengambil ID, menarik data secara otomatis, dan menjalankan semua sumber yang aktif.dokumen →
POST /v3/database-validation/Server ke server
$ curl -X POST https://verification.didit.me/v3/database-validation/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -F "issuing_state=BRA" \
  -F "services=bra_cpf" \
  -F "identification_number=12345678900"
200Oke{ "match_type": "full_match", "validation_type": "1x1" }
Anda memiliki data identitasnya. Kami akan meneruskannya ke registri yang tepat dan mengembalikan hasilnya secara langsung.dokumen →
Integrasi siap agen

Selesaikan Validasi Database dalam satu prompt.

Tempel blok di bawah ini ke Claude Code, Cursor, Codex, Devin, Aider, atau Replit Agent. Isi stack Anda, framework, bahasa, kasus penggunaan, dan agen akan menyelesaikan workflow, webhook, dan kode keputusan secara menyeluruh.
didit-integration-prompt.md
# Didit Database Validation — integrate in 5 minutes

You are integrating Didit's Database Validation module into <my_stack>.
Database Validation cross-references each user's identity data against the
authoritative source for that country — the national civil registry, tax
authority, electoral roll, credit bureau, telco database, court record or
biometric service that issued the document. 1,000+ data sources reachable
through one endpoint. Follow these steps exactly. 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. Two integration paths — pick one

### Path A — Workflow Builder (hosted UI)
Best when you want Didit to capture the ID document, run Optical Character Recognition (OCR), derive the
required fields automatically, and trigger the right registry service per
issuing country.

1. Create a workflow that contains the DATABASE_VALIDATION feature:
   POST https://verification.didit.me/v3/workflows/
   Authorization header:  x-api-key: <your-api-key>
   Body: workflow_label, features array including
         { feature: "DATABASE_VALIDATION" }   (UPPERCASE — strict enum)
   Configure per-country service IDs (e.g. arg_renaper, bra_cpf,
   mex_curp, dom_cedula) plus partialMatchAction / noMatchAction.

2. Create a verification session for an end user:
   POST https://verification.didit.me/v3/session/
   Body: workflow_id (from step 1), vendor_data (your own user id).
   Response: session_url — redirect the user to it.

3. Listen for webhook callbacks (see "Webhooks" below).

### Path B — Standalone server-to-server API
Best when you already have the identity fields (mobile SDK capture,
existing onboarding pipeline, reseller flow). Single endpoint, every
country and every service routed through it.

POST https://verification.didit.me/v3/database-validation/
Content-Type: multipart/form-data
Body fields (all optional except issuing_state and at least one identifier):
  - issuing_state           (required, ISO 3166-1 alpha-3, e.g. ARG, BRA, MEX)
  - services                (optional, repeated, service IDs to run; omit
                             to run every configured service for that country)
  - identification_number   (e.g. DNI, CPF, CURP, cedula number)
  - first_name
  - last_name
  - date_of_birth           (YYYY-MM-DD)
  - selfie                  (file, required for biometric services such as
                             arg_renaper, pan_cedula_sib, pan_cedula_sib_plus)
  - address_element_1       (street + number)
  - address_element_2       (unit / building / floor)
  - address_element_3       (suburb / district)
  - address_element_4       (city / state / region)
  - address_element_5       (postal code; postal_code alias accepted)
  - consent                 (boolean — required when the selected service
                             has requires_consent=true in the catalog)
  - vendor_data             (optional string, your user id)

Response: JSON report with match_type, validation_type (1x1 or 2x2),
per-service validations, source_data, and any warnings.

## 3. Webhooks (Path A only — Path B returns synchronously)
- Register a webhook destination once via
  POST https://verification.didit.me/v3/webhook/destinations/
  Body: url, subscribed_events: ["session.verified", "session.review_started",
                                  "session.declined"]
- 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.

## 4. Reading the report (both paths return the same shape)
The database_validation object includes:
- status: "Approved" | "Declined" | "In Review" | "Not Finished"
- match_type: "full_match" | "partial_match" | "no_match"
- issuing_state: ISO 3166-1 alpha-3 country code
- validation_type: "1x1" (single source full-match) or "2x2" (two
  independent sources corroborate the data)
- screened_data: the user fields submitted (identification_number,
  first_name, last_name, date_of_birth, selfie, address fields, ...)
- validations: array of per-service results. Each entry carries
  service_id (e.g. arg_renaper), service_name, outcome_code (MATCH,
  NO_MATCH, DOCUMENT_NOT_FOUND, BIOMETRIC_IMAGE_UNUSABLE,
  REGISTRY_UNAVAILABLE, ...), optional outcome_detail, a per-field
  validation block (full_match / partial_match / no_match), and a
  source_data block lifted from the registry record (photo, signature,
  full_name, gender, dates, face_match_score for biometric services).

Configurable risks (action per workflow — Decline, Review, or Approve):
- DATABASE_VALIDATION_PARTIAL_MATCH    (partialMatchAction)
- DATABASE_VALIDATION_NO_MATCH         (noMatchAction)

Warnings raised when a service cannot run:
- COULD_NOT_PERFORM_DATABASE_VALIDATION — required input field missing
  (e.g. CPF could not be OCR-extracted). You are NOT charged. Session
  auto-moves to In Review; saving the missing field in the Console
  retriggers the check.

## 5. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: DATABASE_VALIDATION, ID_VERIFICATION,
  LIVENESS, FACE_MATCH, AML, IP_ANALYSIS.
- Country codes are ISO 3166-1 alpha-3 UPPERCASE: ARG, BRA, MEX, ESP, ...
- Service IDs are lowercase snake-case with a country prefix:
  arg_renaper, bra_cpf, mex_curp, dom_cedula, pan_cedula_sib_plus, ...
- 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",
  "Not Finished" (title-cased, space-separated).
- match_type casing matches exactly: full_match, partial_match, no_match
  (lowercase snake-case).
- You are only billed when a service returns a result. Skipped services
  (missing input, unsupported issuing_state) are never billed.

## 6. Pricing reference (public, pay-per-call)
- Variable per source. Lowest tier: $0.05 per check (Dominican Republic,
  Junta Central Electoral).
- Standard government-registry tier: $0.20 per check (Argentina RENAPER,
  Brazil Receita Federal CPF, Mexico RENAPO CURP, Spain DGP, Colombia
  Registraduria, Peru RENIEC, Chile Registro Civil, Ecuador, Uruguay,
  El Salvador, Guatemala, Honduras, Bolivia, Paraguay, Venezuela, Costa
  Rica).
- Biometric premium tier: $0.75 (Panama SIB) up to $1.50 (Panama SIB
  Plus elevated tier with stronger biometric thresholds).
- Global identity network: 156 datasets across 45 countries (AU, NZ,
  UK, IE, FR, DE, IT, ES, PT, NL, BE, CH, AT, Nordics, Greece, Poland,
  Czechia, Hungary, Romania, Slovakia, India, Indonesia, Philippines,
  Thailand, Malaysia, Singapore, Hong Kong, China, Cambodia, Kenya,
  Nigeria, South Africa, Morocco, USA, Canada). Per-service pricing
  surfaced in the catalog and billing exports.
- 500 free checks every month, forever, on every account.

## 7. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Test the full catalog of services with the per-country reference pages
  under https://docs.didit.me/api-reference/database-validation/.
- Switch to live: flip the application's environment toggle in console.

When in doubt: https://docs.didit.me/core-technology/database-validation/overview
Butuh konteks lebih? Lihat dokumentasi modul lengkapnya.docs.didit.me →
Cakupan registri otoritatif

147 registri otoritatif — dapat dicari.

Setiap penyedia Validasi Database yang Didit gunakan untuk cross-check, lengkap dengan URL referensi kanonis dan kategori verifikasi. Sumbernya dari katalog dokumen Mintlify yang sama dengan yang dibaca oleh Business Console, cari berdasarkan nama negara, kode ISO 3166-1 alpha-3, atau ID layanan. 147 layanan · 53 negara.

Referensi kanonis: docs.didit.me/core-technology/database-validation/overview

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
  • 0+
    Sumber terpercaya, satu panggilan.
  • 0
    Registri sipil Amerika Latin dan Spanyol, terintegrasi langsung.
  • Mulai dari $0.05
    Per pemeriksaan. Hanya ditagih jika ada hasil.
  • <0.0s
    End-to-end pada traffic produksi.
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
Mulai gratis
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
Lihat daftar harga lengkapMulai gratis
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
Hubungi kami

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 Database Validation?

Database Validation cross-references a user's identity data, name, date of birth, identification number, address, against 1,000+ authoritative sources reachable through one endpoint. Government civil registries, tax authorities, electoral rolls, credit bureaus, telco databases, court records, and address verification.

It defeats synthetic identities (a fabricated DNI or Brazilian Cadastro de Pessoas Físicas (CPF) won't be in the official record), confirms residency for Anti-Money Laundering Directive 6 (AMLD6) onboarding, and routes automatically by issuing_state so you don't have to hard-code per-country providers.

Full reference: docs.didit.me/core-technology/database-validation/overview.

What does Database Validation cost?

Variable per provider, billed only on a result. No minimums, no platform fees, no charges on skipped services.

  • Cheapest tier $0.05 per check (Dominican Republic via Junta Central Electoral).
  • Standard government-registry tier $0.20 (Argentina, Brazil, Mexico, Spain, Colombia, Peru, Chile, and more).
  • Biometric premium $0.75–$1.50 (Panama Servicio de Identificación Biométrica (SIB) and SIB Plus).

Bundled inside a full Know Your Customer (KYC) workflow alongside Identity Document Verification + Liveness + Face Match: $0.33 per session.

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 is the response shape?

The database_validation object returns:

  • status, Approved, Declined, In Review.
  • match_type, full_match, partial_match, no_match.
  • validation_type, 1x1 (one registry corroborates) or 2x2 (two independent registries corroborate, the highest confidence we can express).
  • validations[], per-service rows with service_id, per-field outcome, an outcome_code (MATCH, NO_MATCH, DOCUMENT_NOT_FOUND, BIOMETRIC_IMAGE_UNUSABLE, REGISTRY_UNAVAILABLE), and the source_data lifted from the registry record, full name, dates, photo Uniform Resource Locator (URL), signature, plus face_match_score for biometric services.

Same shape on the standalone Application Programming Interface (API) and on the session flow.

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.

Related

Modul terkait

Infrastruktur untuk identitas dan fraud.

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

Mulai gratisHubungi kami
Minta AI untuk merangkum halaman ini