Didit vs IDVerse: per-check prices vs a 12-month contract

Last reviewed: 24 October 2026 · Not legal advice

Didit vs IDVerse compares two vendors that both verify an identity document and match it to a live face. IDVerse started as a specialist in exactly that and is now sold as part of LexisNexis Risk Solutions; idverse.com redirects to its page on the LexisNexis site.^[1] Didit runs the whole verification behind one API, from the document to sanctions screening. We also keep a short IDVerse alternative page.

We build Didit, so read this as one side. Every IDVerse fact below comes from the IDVerse page and brochure on risk.lexisnexis.com and the IDVerse listing on AWS Marketplace, as we checked them on 24 October 2026, and each one is cited. We quote only the price IDVerse publishes. Where IDVerse is stronger, we say so.

Didit vs IDVerse at a glance

IDVerse column: risk.lexisnexis.com and AWS Marketplace, checked 24 October 2026. Didit column: docs.didit.me.

Which one fits your team

Pay per check, or commit to a 12-month contract

The IDVerse product page offers "Talk To Sales" and a demo request.^[1] The price we found listed is the IDVerse listing on AWS Marketplace, sold by IDVerse \ LexisNexis Risk Solutions: a 12-month contract for "IDKit (25,000 requests)", biometric identity verification up to 25,000 requests, at $35,000. The listing says unused entitlements expire if you do not renew, and refunds are given on request on the basis of no usage.^[3] Larger or different contracts go through sales.

On Didit, you open the Business Console, build a workflow and run it in the sandbox, then pay per check from prepaid credit.^[4]

Not like for like: IDVerse prices a contract for up to 25,000 requests, Didit prices each check with no commitment.

The $0.33 full ID check already includes face match; on its own, face match is $0.05, and age estimation reuses the same selfie for $0.10.^[4][11][17] Add up the checks in your workflow, or compare plans on the pricing page.

What you get back from every check

IDVerse is built to be fully automated: within seconds the user gets a yes/no answer, and your fraud, onboarding and compliance teams can open a portal to review results and look for patterns.^[1] Its FraudHub product adds insights into fraud patterns across your instance; the page points to sales for more information.^[1]

Didit returns the evidence with every decision. Each liveness check comes back in the API and the webhook with the method, a score from 0 to 100, the reference selfie, the capture video on active methods, an age estimate when enabled and up to five matching faces from your application, blocklisted and allowlisted faces first.^[6] Every warning has a stable code, and in the workflow you choose what each one does: no action, review or decline. A detected attack, a missing face or a blocklisted face always declines. Sessions sent to review land in the Business Console with that evidence on screen.^[6][7]

See the liveness report and liveness warnings docs.

Duplicates, blocklists and face search on the same selfie

A live face does not tell you whether the person already has an account or was banned last month. On Didit, face search runs inside every liveness check, with no extra integration: the selfie is compared against your approved sessions and your face blocklist. A blocklisted face declines the session automatically, a possible blocklist match goes to review, and for a duplicated face you set the action: no action, review or decline.^[7][8][6] The blocklist also covers documents, phone numbers and emails.^[9] On the IDVerse side, FraudHub is the product the page describes for blocking repeat bad actors.^[1]

What Didit runs on every selfie, before the session gets its status.

See face search 1:N, or the face search and blocklist docs.

Documents and liveness: where IDVerse is stronger

Documents are IDVerse's home ground. Its brochure says it covers up to 16,000 document types in 220+ countries and territories and 140+ languages and typesets, its OCR is accurate in over 98.5% of cases for human-readable text and 99.98% for machine-readable text, and document fraud analysis runs up to 300 checks for tampering.^[2] The same journey also verifies digital credentials such as national eIDs and mobile driver's licences.^[1]

The IDVerse page lists ISO 30107-3 Level 1 and Level 2, SOC 2 Type 2, ISO 27001, 27017, 27018, 27701, 22301 and 9001, NIST 800-63A and a Level B bias test.^[1]

Didit runs its own liveness models with three methods: passive, from a single capture; 3D Flash, which reads how projected light falls on a face; and 3D Action and Flash, which adds a random blink or nod.^[5] Virtual cameras and injected frames raise their own warnings.^[7] Didit's iBeta Level 1 PAD test (ISO/IEC 30107-3, NIST-accredited lab) recorded zero successful attacks out of 360, across six categories. After a supervised test from November 2024 to July 2025, Spain's Tesoro Público, Banco de España, SEPBLAC and CNMV concluded that Didit's NFC and liveness verification is at least as safe as an in-person ID check.^[13] Compare the methods on the liveness detection page.

One platform: liveness is one step of KYC

IDVerse is sold as document authentication and biometric verification, and its AWS Marketplace listing says IDKit meets AML KYC requirements including PEP and sanctions. Business verification and transaction monitoring are not listed on the IDVerse product page (checked 24 October 2026); whether LexisNexis Risk Solutions offers them elsewhere is not stated there.^[1][3]

On Didit, every check runs on the same user and session, assembled in a no-code workflow builder: ID verification, liveness, face match, database validation, AML screening and the rules that decide the status.^[10] The same face is reused for age estimation, face search, duplicates and the blocklist. AML screening against 1,300+ watchlists is $0.20, registry checks for companies start at $2.00, and transaction monitoring is $0.02 per transaction.^{[4][12][20][21]}

One Didit session, from the first screen to the decision your backend receives.

See the workflow orchestrator, ID verification, database validation and AML screening.

Integration and switching

IDVerse users start the flow by scanning a QR code, opening an SMS link or through the API, and the brochure lists integration options from hosted platforms to APIs and SDKs.^[1][2] Didit connects through a hosted link, an iframe or the JavaScript SDK on the web, and iOS, Android, React Native and Flutter SDKs on mobile.^[15][16] The fastest start is a hosted link: create a session, send the user to its URL, read the webhook. You can run both vendors side by side while you compare.

• List what IDVerse does for you today: documents, liveness, face match, FraudHub, Face Access.
• Note the end date of your IDVerse contract and the requests left on it.
• Rebuild the flow in the workflow builder, pick a liveness method, set thresholds and the duplicate-face action.
• Route a share of new users to Didit and compare pass rates, review workload and total cost.

How Didit helps teams replacing IDVerse

Didit gives you liveness with its full evidence, face search, document checks and AML screening as one hosted service, with a published price per check. See the IDVerse alternative page for the side-by-side, or start from the liveness detection page.

Frequently asked questions

Sources

1. IDVerse product page, LexisNexis Risk Solutions, checked 24 October 2026.
2. IDVerse brochure, LexisNexis Risk Solutions, checked 24 October 2026.
3. IDVerse, Fully Automated Identity Verification, AWS Marketplace listing sold by IDVerse \ LexisNexis Risk Solutions, checked 24 October 2026.
4. Pricing, Didit docs, read 24 October 2026.
5. Liveness detection, Didit docs.
6. Liveness report, Didit docs, read 24 October 2026.
7. Liveness warnings, Didit docs, read 24 October 2026.
8. Face Search 1:N, Didit docs, read 24 October 2026.
9. Blocklist users, Didit docs, read 24 October 2026.
10. Workflows, Didit docs, read 24 October 2026.
11. Age estimation, Didit docs, read 24 October 2026.
12. AML screening overview, Didit docs.
13. Certifications and attestations, Didit docs.
14. Security and compliance, Didit docs.
15. Web SDKs overview: JavaScript SDK, iframe and redirect, Didit docs.
16. Native SDKs overview, Didit docs.
17. Face match, Didit docs.
18. User documents and supported document types, Didit docs.
19. New pricing from 1 November 2026, Didit blog, read 24 October 2026.
20. KYB registry pricing, Didit docs.
21. Transaction monitoring overview, Didit docs.

For the full side-by-side, pricing and the switching steps, see the IDVerse alternative page.