Q: Can I replace the KYC vendor Unit21 currently integrates with?

Yes — and that's the most common reason Unit21 customers add Didit. Unit21 is KYC-agnostic and connects to any KYC provider via webhook or API. If you're currently routing through Persona, Veriff, or Trulioo into Unit21: 1. Add Didit as your KYC provider (one weekend integration, public docs at [docs.didit.me](https://docs.didit.me)). 2. Map Didit's webhook payload to your existing Unit21 user-create call. 3. Cut over traffic. Mirror 10 % first, compare results, flip the rest. Didit ships the same identity signals — document data, biometrics, AML flag, risk score — that Unit21 expects. No changes needed on the Unit21 side.

Q: Is there a native Didit × Unit21 integration?

Not a one-click connector yet — the integration is a webhook mapping your engineering team configures in an afternoon. Both products have open, well-documented APIs, and the data shapes align naturally. If you want help with the integration spec (payload mapping, error handling, retry logic), email `hello@didit.me` and our solutions team will send you the reference implementation. We've done this with dozens of Unit21 customers.

Q: Does Didit satisfy the KYC requirements that regulators expect before transaction monitoring?

Yes. Didit is the only KYC provider an EU government has formally attested as **safer than verifying someone in person** — Spain's Tesoro, Banco de España, and SEPBLAC reviewed and signed off on the architecture. The report is public. Certifications: **SOC 2 Type 1, ISO/IEC 27001:2022, iBeta Level 1 anti-spoofing, GDPR-native**. For US FinCEN/BSA programmes: Didit's document + biometric + AML onboarding check satisfies Customer Identification Program (CIP) requirements and produces audit-ready session records. Aligned with AMLD6, MiCA, eIDAS 2.0.

Q: How does Didit handle step-up verification when Unit21 flags a high-risk transaction?

Unit21 can trigger a Didit step-up verification via webhook or direct API call. When a transaction alert fires, your backend calls `POST /v3/session/` with a `step_up` workflow — typically Passive Liveness + Face Match 1:1 against the original onboarding selfie — and redirects the user to the hosted verification URL. The result comes back in a signed webhook in <2s. Your backend reads the verdict, passes it back to Unit21 as a case annotation, and either clears or escalates the alert. 500 free step-up sessions every month. Paid sessions at the same $0.33 KYC bundle price.

Question 1

Does Didit replace Unit21?

Accepted Answer

No — they operate at different layers of the compliance stack and work best together.

**Unit21** is a Transaction Monitoring and case-management platform: alert triage, SAR (Suspicious Activity Report) filing, AI-assisted investigation. It monitors behaviour after a user is onboarded.

**Didit** is the identity and fraud layer that runs *before* Unit21 sees the user: ID document capture, biometric liveness, face match, AML onboarding screening. Didit verifies who someone is and whether they're high-risk at the point of signup.

The standard pairing: Didit onboards → passes a verified user ID and risk signal to Unit21 → Unit21 monitors transactions going forward.

Question 2

How does Didit feed verified users into Unit21?

Accepted Answer

Via webhook. Every completed Didit session fires a signed webhook (HMAC-SHA256) with the verified identity, document data, AML onboarding result, and risk score. Your backend ingests that event and creates the Unit21 user profile in the same handler — no manual bridge needed.

The `/v3/` API response also returns a structured JSON object with all verification fields (name, DOB, document number, nationality, liveness result, face-match score) that map directly to Unit21's user-create payload.

Integration typically takes an afternoon for an existing Unit21 customer.

Question 3

What does Didit cost as the KYC layer feeding into Unit21?

Accepted Answer

**$0.33 per full KYC check** (ID document + passive liveness + face match + IP analysis, bundled). Compare that to Persona at $1.50 or Veriff at $1.39 — the two providers Unit21 most commonly integrates with today.

Additional modules stack on top at public per-check prices:

- AML onboarding screening: $0.27
- Ongoing AML monitoring: $0.07 / user / year
- Business verification (KYB): $2.00 per business

**500 verifications free every month, forever.** No contract, no minimum. Pay-per-success: failed sessions don't count.

Question 4

Can I use Didit's AML results as risk signals inside Unit21?

Accepted Answer

Yes. Didit's AML onboarding check runs against **1,000+ sanctions, PEP, and adverse-media lists** at the point of signup. The result — hit / no-hit, list name, match confidence — is returned in the session webhook payload and can be forwarded directly to Unit21 as a user-level attribute or risk tag.

Didit also supports **ongoing AML monitoring** ($0.07 / user / year) that re-checks the same person every 24 hours and fires a webhook on any new hit — keeping Unit21's risk profile current without a manual re-verification.

Question 5

Does Didit handle case management or SAR filing?

Accepted Answer

No — that's Unit21's domain. Didit focuses on the identity and fraud layer at onboarding (and during step-up checks): document capture, biometrics, liveness, AML onboarding screening, device & IP analysis.

Once a user is verified and live, any suspicious transaction patterns are Unit21's territory — alert queues, case management, SAR filing, AI-assisted triage. The two tools are designed to be complementary, not overlapping.

Question 6

What's the difference between Didit AML and Unit21 Transaction Monitoring?

Accepted Answer

Two different AML disciplines:

**Didit AML screening** (onboarding-time) — checks a person's identity at the point of signup against sanctions lists, PEP registries, and adverse-media sources. Answers: *is this person on a list?* Runs in <1s as part of the KYC flow.

**Unit21 Transaction Monitoring** (post-onboarding) — watches transaction behaviour over time, applies rule-based alerts, and flags patterns like structuring, layering, and velocity anomalies. Answers: *is this account behaving suspiciously?*

Both layers are required for a complete AML programme. Didit at onboarding + Unit21 in production = the standard stack for regulated fintechs.

Question 7

Can I replace the KYC vendor Unit21 currently integrates with?

Accepted Answer

Yes — and that's the most common reason Unit21 customers add Didit. Unit21 is KYC-agnostic and connects to any KYC provider via webhook or API. If you're currently routing through Persona, Veriff, or Trulioo into Unit21:

1. Add Didit as your KYC provider (one weekend integration, public docs at [docs.didit.me](https://docs.didit.me)).
2. Map Didit's webhook payload to your existing Unit21 user-create call.
3. Cut over traffic. Mirror 10 % first, compare results, flip the rest.

Didit ships the same identity signals — document data, biometrics, AML flag, risk score — that Unit21 expects. No changes needed on the Unit21 side.

Question 8

Is there a native Didit × Unit21 integration?

Accepted Answer

Not a one-click connector yet — the integration is a webhook mapping your engineering team configures in an afternoon. Both products have open, well-documented APIs, and the data shapes align naturally.

If you want help with the integration spec (payload mapping, error handling, retry logic), email `hello@didit.me` and our solutions team will send you the reference implementation. We've done this with dozens of Unit21 customers.

Question 9

Does Didit satisfy the KYC requirements that regulators expect before transaction monitoring?

Accepted Answer

Yes. Didit is the only KYC provider an EU government has formally attested as **safer than verifying someone in person** — Spain's Tesoro, Banco de España, and SEPBLAC reviewed and signed off on the architecture. The report is public.

Certifications: **SOC 2 Type 1, ISO/IEC 27001:2022, iBeta Level 1 anti-spoofing, GDPR-native**.

For US FinCEN/BSA programmes: Didit's document + biometric + AML onboarding check satisfies Customer Identification Program (CIP) requirements and produces audit-ready session records. Aligned with AMLD6, MiCA, eIDAS 2.0.

Question 10

How does Didit handle step-up verification when Unit21 flags a high-risk transaction?

Accepted Answer

Unit21 can trigger a Didit step-up verification via webhook or direct API call. When a transaction alert fires, your backend calls `POST /v3/session/` with a `step_up` workflow — typically Passive Liveness + Face Match 1:1 against the original onboarding selfie — and redirects the user to the hosted verification URL.

The result comes back in a signed webhook in <2s. Your backend reads the verdict, passes it back to Unit21 as a case annotation, and either clears or escalates the alert.

500 free step-up sessions every month. Paid sessions at the same $0.33 KYC bundle price.

Alternatif Unit21, empat lini produk dalam satu API

3 alasan untuk menggabungkan Didit dengan Unit21

Lengkapi stack Anda

KYC 3-6x lebih murah

Handoff onboarding → monitoring <2 detik

Unit21 vs Didit, baris demi baris.

Verifikasi Identitas

Biaya vs. Mitra KYC

Kecepatan Verifikasi

Penyaringan AML

Pengalaman Developer

Sumber data terhubung

Atestasi regulator

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

Mulai gratis. Bayar sesuai penggunaan. Skala ke Enterprise.

Gratis

Berbasis Pemakaian

Enterprise

Harga transparan, detail per baris.

Switching from Unit21.

Infrastruktur untuk identitas dan fraud.