Question 1

What is Didit?

Accepted Answer

Didit is **infrastructure for identity and fraud**, the platform we wished existed when we were building products ourselves: **open, flexible, and developer-friendly**, built to work as part of your stack.

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 **3,000+ companies** across **220+ countries**.
- **Secure**, SOC 2 Type 2, 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 learns from every session and gets better every day.

Question 2

How do I migrate from Regula to Didit?

Accepted Answer

Two paths, pick the one that suits your team.

- **Self-serve.** Open the sandbox at [business.didit.me](https://business.didit.me), get an API key in under a minute, point your session creation and webhook at Didit, and ship. Copilot can rebuild your current flow in the workflow builder from a description.
- **With our team.** Email `hello@didit.me` and our migrations team takes it end to end, across Know Your Customer (KYC), Know Your Business (KYB), Transaction Monitoring, and Wallet Screening.

Either path: one API covers KYC, KYB, AML, Transaction Monitoring, and Wallet Screening, and you pay per successful check.

Question 3

Will Didit support the same documents and countries Regula does?

Accepted Answer

**Didit's coverage is global.**

- **220+ countries and territories**, **14,000+ document types**, and **48+ languages** on the hosted user-facing flow.
- Every module you would run on Regula also runs here on one API: Identity Document Verification, NFC chip reading, Proof of Address, Passive + Active Liveness, Face Match 1:1, Face Search 1:N, Age Estimation, Biometric Auth, AML, and Device & IP analysis. Plus KYB, Transaction Monitoring and Wallet Screening, none of which is documented on Regula's public pages.
- If a document or country you need is not covered yet, **tell us**. The data-science team prioritises requests from active customers.

The best test is your own document mix. Open a free sandbox and run the documents you actually see in production.

Question 4

How similar is Didit's API to Regula's?

Accepted Answer

Didit uses the session model most identity APIs use:

- Call **`POST /v3/session/`** with a `workflow_id` and a `vendor_data` identifier.
- **Redirect or embed** the verification URL returned in the response.
- **Receive a signed webhook** (HMAC-SHA-256) with the verdict.

One `/v3/` namespace covers KYC, KYB, Transaction Monitoring, and Wallet Screening. One authentication header, one webhook receiver. SDKs for **Web, iOS, Android, React Native, and Flutter**, same packaging your engineers already use.

Question 5

Can I run Didit side-by-side with Regula before cutting over?

Accepted Answer

Yes. You can run a parallel evaluation:

- **Mirror 10 % of your traffic** to Didit while Regula keeps handling the rest.
- **Compare verdicts**, same user, both vendors, side by side in the console.
- **Flip the rest** when you're satisfied with pass rates, latency, and fraud catch.

A re-keying script ships with every migration so your internal user IDs map cleanly to Didit session IDs. You pay Didit only for the checks you run on it.

Question 6

Can I start with one module and keep my other vendors?

Accepted Answer

**Yes. Didit is modular.**

- **Pay per use.** You pay per successful check at published prices. Enterprise plans add custom terms for teams that want them.
- **Wallet Screening (Know Your Transaction)** at `$0.15` per check, with a signed PDF report.
- **AML Screening** at `$0.20` per check, against 1,300+ watchlists, with ongoing monitoring at `$0.07` per person per year.
- **Transaction Monitoring** at `$0.02` per transaction, with 150+ preset rules you can backtest on your own history before you switch them on.

Each module is a separate step in a workflow, so you can move one at a time and keep the rest with the vendors you already use.

Question 7

What does Didit cost, and what happens at scale?

Accepted Answer

Every price is published. The headline numbers:

- **Full KYC bundle: $0.33** (ID + Passive Liveness + Face Match + Device and IP).
- **Wallet Screening: $0.15 per check.**
- **KYB: from $2.00 per business** (linked KYC and AML are billed separately).
- **Ongoing AML monitoring: $0.07 per user, per year.**
- **Investigator agent: $0.20 per reviewed item.**

You pay per successful check, failed or abandoned sessions are not billed, and volume discounts apply automatically. Enterprise adds custom terms, an SLA, data-residency choice, and a dedicated support channel.

Question 8

Is Didit compliant for regulated industries?

Accepted Answer

Yes, and we can show it on paper.

Spain's **Tesoro**, the **Banco de España**, and **SEPBLAC** reviewed Didit's remote verification and formally attested that it is **safer than verifying someone in person**. The full report is public.

Certifications:

- **SOC 2 Type 2**.
- **ISO/IEC 27001:2022.**
- **iBeta Level 1** presentation-attack detection.
- **GDPR**, with **EU data residency** by default.

Every certificate and audit report lives on [/security-compliance](/security-compliance), request the Trust Pack and we send it back in one PDF.

Question 9

How does Didit catch deepfakes, face swaps, and AI-generated documents?

Accepted Answer

Every session runs **200+ fraud signals** in real time. The ones people ask about most:

- **Liveness**, proves the person is real and present (not a photo, video replay, or AI-generated face). iBeta Level 1 certified.
- **Face matching**, checks the selfie matches the document, and catches face-morph attacks.
- **Document tampering**, flags edits, splices, and AI-generated documents.
- **AML + sanctions + PEP screening**, checked against **1,300+ lists** in the same call.
- **IP + device intelligence**, network, fingerprint, and behavioural heuristics.

We run automated monitoring and retraining loops on autopilot. Every new attack pattern we see gets folded back into the models continuously, your defences improve without you migrating or upgrading anything.

Question 10

Can my AI coding agent integrate Didit without me in the loop?

Accepted Answer

Yes, we built Didit for humans and AI agents.

Our **Model Context Protocol (MCP) server** is live and plugs straight into modern AI coding tools. Your agent can sign up, generate API keys, design a workflow, run test sessions, listen for webhooks, and check the results, all without you opening the console.

We've tested the full integration with **Claude Code, Codex, Cursor, Devin, Aider, and Replit Agent**. Every one of them completes the integration end-to-end. The canonical agent prompt is paste-ready on the [/developers](/developers) page.

Question 11

Where does my customer data live, and how is it protected?

Accepted Answer

**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. TLS 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 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.

The Data Processing Addendum, sub-processor list, and security policy are public at [/security-compliance](/security-compliance).

Regula alternative: hosted checks from onboarding to monitoring

Why identity teams move from Regula to Didit

Onboarding to monitoring on one API

Pay per check at published prices

Investigator reviews the queue

Agents that do the review work, inside your policy.

Investigator agent

Support agent

Copilot

MCP server

Regula vs Didit, line by line.

Pricing Model

Product Scope

Developer Experience

Coverage

Compliance & Credibility

Connected data sources

Regulator attestation

Start free. Pay as you go. Scale to Enterprise.

Free

Pay as you go

Enterprise

Public pricing, line by line.

Switching from Regula.

Infrastructure for identity and fraud.