Choosing an Identity Verification API: Features, Pricing & Speed

An identity verification (IDV) API is a programmatic interface that lets your product run KYC (Know Your Customer), AML (Anti-Money-Laundering), biometric, and document checks without building the underlying infrastructure yourself. Coverage, speed, pricing transparency, composability, and developer experience vary enough between vendors to affect your integration timeline, your user conversion rate, and your long-term compliance posture.

This post gives you a structured evaluation framework — five criteria and a set of concrete questions to apply to any IDV API before you commit.

Key takeaways

• Coverage — countries, document types, languages — determines whether the API can serve your current and near-future markets without a vendor swap.
• Speed matters at the user level: sub-2-second inference keeps abandonment low; slow checks lose users mid-flow.
• Pricing transparency separates vendors that publish per-module prices from those that require a sales call — which is the first signal of how predictable and comparable the cost will actually be.
• Composability — a unified API that handles KYC, KYB (Know Your Business), AML, Transaction Monitoring, and Wallet Screening in one workflow — reduces integration overhead and removes data gaps between identity and fraud.
• Developer experience (SDKs, MCP server, documentation quality) determines how quickly the first check goes live.
• Didit integrates in 5 minutes, covers 220+ countries and 14,000+ document types, publishes a public price on every module, and ships a free MCP (Model Context Protocol) server for AI agent workflows.

What an IDV API does

At minimum, an IDV API accepts a user identity claim — a document scan, a biometric capture, a data point — and returns a decision. The decision can be binary (pass / fail), risk-scored, or status-based (APPROVED, IN_REVIEW, DECLINED). Most modern APIs also handle the collection flow — a hosted URL or embedded SDK that guides the user through document capture and liveness — so your team does not need to build native camera handling.

The scope of what APIs cover differs significantly. Some handle documents only. Others add liveness detection, biometric matching, database cross-referencing, AML screening, transaction monitoring, and ongoing monitoring. The wider the scope on a single API, the fewer point solutions you need to stitch together.

Why the choice matters

Switching identity vendors is expensive. You rebuild integrations, remap data schemas, retrain compliance teams, and often re-verify a portion of your user base. Getting the evaluation right the first time avoids a 6–12 month remediation project.

The choice also has regulatory consequences. Your vendor's certifications, audit scope, and data-residency commitments become part of your own compliance posture. A vendor without documented certifications shifts the burden of proof back onto your team.

Evaluation criterion 1 — coverage and compliance

Geographic coverage. How many countries, document types, and languages does the API support? If your roadmap extends to new markets, verify those markets are covered before signing — not after.

Questions to ask:

• How many countries and document types are in the coverage list?
• How frequently is the document template library updated as new IDs are issued?
• What languages does the verification UI support, and how are they added?

Regulatory certifications. Look for SOC 2, ISO/IEC 27001, and iBeta Level 1 PAD (for passive liveness). For EU-facing products, government-level attestation carries weight that no vendor-produced compliance statement can match.

Questions to ask:

• Is the liveness solution iBeta Level 1 PAD certified?
• Has the vendor received any formal government attestation?
• Where is biometric and document data processed and stored, and can you choose the region?

Speed. Sub-2-second inference at the module level keeps users inside the flow. Latency above 5 seconds measurably increases abandonment.

Evaluation criterion 2 — pricing, composability, and developer experience

Pricing transparency. Does the vendor publish per-module prices, or is everything quote-only? Published prices mean predictable unit economics. Quote-only pricing means cost depends on negotiation leverage, and comparing vendors becomes time-consuming guesswork.

Questions to ask:

• What is the per-check price for document verification, liveness, AML screening, and each module I will use?
• Is there an annual minimum, a seat license, or a charge for failed attempts?
• Is there a free tier to test with before committing?

Composability. An API that handles both identity (KYC, KYB, reusable credentials) and fraud (Transaction Monitoring, AML, Wallet Screening) in one unified interface removes the integration overhead of connecting separate point solutions. It also eliminates data handoffs that create latency and gaps — a KYC result that never makes it into the AML system, or a transaction flag that doesn't link back to the user's identity record.

Questions to ask:

• Does the same API handle KYC, KYB, AML, Transaction Monitoring, and Wallet Screening?
• Can I compose a workflow visually without writing new integration code every time I add a check?
• Can a KYB session automatically spawn KYC sessions for UBOs (ultimate beneficial owners)?

Developer experience. Integration speed depends on SDK quality, documentation depth, and how quickly you can run a first real check in your environment.

Questions to ask:

• Are there native SDKs for my platforms (Web, iOS, Android, React Native, Flutter)?
• Is there an MCP server for AI agent orchestration?
• How long does a working integration take from first API call to production?

Use cases

Fintech and neobanks. High-volume flows where cost per check is a direct unit-economics line item. Composability matters here: the same flow that onboards a user today may need to route into transaction monitoring next quarter, without a second integration project.

Crypto exchanges and VASPs (Virtual Asset Service Providers). AML screening, wallet screening, FATF Travel Rule compliance, and transaction monitoring ideally live in one API. BYOK (bring-your-own-key) wallet screening pricing removes the need for expensive annual blockchain-analytics contracts.

Marketplace platforms. Seller onboarding needs document verification, KYB for merchant entities, and linked KYC for UBOs. Fragmented APIs require manual joins between systems to produce a complete compliance record.

iGaming and age-gated products. Age Estimation + ID Verification + Passive Liveness is a common onboarding stack. The platform also needs ongoing AML monitoring as users become active and transaction volumes grow.

How Didit meets the criteria

Didit's unified /v3/ API covers identity and fraud in one interface: KYC, KYB, AML, Transaction Monitoring, Wallet Screening, Email Verification, and Phone Verification are all callable at https://verification.didit.me. A Visual Workflow Builder handles conditional branching, A/B testing, and nested decisions without new code deploys.

Coverage: 220+ countries, 14,000+ document types, 48+ languages, sub-2-second inference across all modules.

Certifications: SOC 2 Type 1, ISO/IEC 27001:2022, iBeta Level 1 PAD (0% IAPAR / 360 attempts). Only provider formally attested by an EU member-state government (Spain's Tesoro / BdE / SEPBLAC / CNMV) as safer than in-person verification.

Pricing: every module is public — ID Verification $0.15, Passive Liveness $0.10, Face Match 1:1 $0.05, AML Screening $0.20, full core KYC flow $0.33. No minimums, no seat licenses, pay-per-success. 500 free verifications per month.

Developer experience: SDKs for Web, iOS, Android, React Native, and Flutter are free. A free MCP server enables AI agent orchestration. A basic integration runs in about 5 minutes.

# Create a KYC session — unified /v3/ API
curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflow_id": "your-workflow-id",
    "vendor_data": "user-5678",
    "callback": "https://your-app.com/webhook"
  }'

The response includes a session_url you open for the user and a session_id to track via webhook. That is the full integration surface for a standard KYC flow.

Frequently asked questions

How long does a Didit integration take?

About 5 minutes to run a first check. SDKs for Web, iOS, Android, React Native, and Flutter are free and cover both the collection flow and the API calls, so you're not writing camera handling from scratch.

Does Didit cover all my markets?

220+ countries and 14,000+ document types. The full coverage list is at docs.didit.me — check your specific countries and document types before assuming coverage.

Is there a free tier?

Yes. 500 free verifications per month, no credit card required at signup. business.didit.me

Does the API handle KYB and Transaction Monitoring, not just KYC?

Yes. The unified /v3/ API handles KYC, KYB, AML, Transaction Monitoring, Wallet Screening, Email Verification, and Phone Verification. A KYB session can automatically spawn KYC sessions for each UBO, and those users flow into Transaction Monitoring without a separate integration.

What certifications does Didit hold?

SOC 2 Type 1, ISO/IEC 27001:2022, iBeta Level 1 PAD. Spain's Tesoro / BdE / SEPBLAC / CNMV have formally attested that Didit is safer than in-person identification — a regulatory credential unique to Didit.

Ready to get started?

• Read the docs → docs.didit.me — API reference, SDK guides, coverage tables
• Explore the platform → didit.me/products/id-verification
• See pricing → didit.me/pricing — every module, public price
• Start free → business.didit.me — 500 free verifications / month, no commitment