Didit vs Hopae: the full verification stack, not an eID add-on
Didit vs Hopae: compare documented checks, published pricing, review evidence and migration steps. Didit core KYC costs $0.33.

For IDV providers, banks and payment platforms evaluating Hopae, choose Didit to connect national eID acceptance with a complete onboarding flow. Accept six available national digital ID schemes, use document KYC when an eID is unavailable, and connect AML, KYB and monitoring in the same account. The document route has a published $0.33 core price; the eID route is priced separately.
- Published core KYC price: $0.33 for ID, passive liveness, face match and device/IP.
- Spain’s financial sandbox report: documented NFC and active-liveness fraud tests, with SEPBLAC participation.
- 4,000+ companies use Didit; document coverage spans 220+ countries and territories and 14,000+ document types. Public customer evidence.
Evidence you can inspect before switching
Published passive-liveness test: the iBeta letter dated 4 February 2026 reports zero successful presentation attacks in 360 attempts across six subjects and six attack species. The tested configuration was Safari on an iPhone 13 Pro with iOS 18.4.1 and its backend, at Level 1 under ISO/IEC 30107-3. This result applies to that configuration and attack level.
A published customer outcome: in Didit’s AhoraCrypto customer story, the crypto on/off-ramp reports more than 20% savings per user against its previous provider and over 50% less time on manual user reviews. The previous provider is unnamed; these are that customer’s reported results.
Budget the checks you will actually run
The core KYC bundle is $0.33: ID verification $0.15 + passive liveness $0.10 + face match $0.05 + device and IP analysis $0.03. The second example combines core KYC at $0.33 and initial AML screening at $0.20, totaling $0.53 per person checked.
| Monthly units | Didit core KYC at $0.33 | Didit: Core KYC + initial AML screening | Vendor published terms; different scope |
|---|---|---|---|
| 1,000 | $330 | $530 |
|
| 10,000 | $3,300 | $5,300 | |
| 50,000 | $16,500 | $26,500 |
Illustrative USD list-rate budgets. Core KYC assumes successful checks. Taxes, credits, prepaid discounts and other modules are excluded. The core-plus-AML column is the sum of $0.33 core KYC and $0.20 initial AML screening. Database checks and national digital IDs are outside the $0.33 core KYC bundle. Vendor prices retain their stated currency, billing unit and plan scope.
Integration scope: country database checks use the documented workflow or standalone API integration and require each service’s input fields. Global identity enrichment is standalone API only, outside the workflow builder. Database service scope.
Compare the scope your team needs
| Requirement | Didit | Hopae Connect public scope |
|---|---|---|
| Six national digital IDs | MitID (Denmark), BankID Sweden, iDIN (Netherlands), Finnish Trust Network, Smart-ID (Estonia, Latvia, Lithuania, Belgium) and Mobile-ID (Estonia, Lithuania). Available national digital IDs. | Hopae relays national and bank identity providers; availability and setup depend on each connection. (public source, checked 25 October 2026). |
| Document and biometric checks | Core KYC $0.33; NFC $0.15; passive liveness $0.10 in a workflow or $0.05 through the standalone API; active liveness $0.15. ID verification; liveness. | For chip-based credentials, the user scans with NFC; Hopae verifies the credential. This is distinct from document-image KYC with a selfie and face match. (public source, checked 25 October 2026). |
| Evidence and review | Check results, extracted fields, images and warnings in the API response; webhooks, compliance PDF reports and case management support review. Investigator is $0.20 per reviewed item. Investigator. | Returned attributes and provenance depend on the credential; match outcomes are supplied for match-capable providers. (public source, checked 25 October 2026). |
| Build and migrate | No-code workflows, Copilot, hosted MCP with OAuth 2.1, SDKs for web/iOS/Android/React Native/Flutter, and historical-verification imports. Workflows; Copilot; MCP; import API. | Hosted OIDC or REST API; production apps require an Enterprise subscription. (public source, checked 25 October 2026). |
| Additional checks in the same Didit account |
| Hopae Connect documents an eID verification hub. Its cited product page does not list the AML, transaction-monitoring, KYB or crypto-screening modules grouped here; those are separate requirements from accepting an eID. (public source, checked 25 October 2026). |
National digital IDs are an alternative verification route; a signed scheme result is not a selfie or face-match result. Database and eID checks have separate prices from the $0.33 core KYC bundle. Device/IP analysis here is part of a verification session.
Keep the user moving when an eID is unavailable
For a bank, payment provider or marketplace, accepting an eID is only one decision in onboarding. Configure a document fallback in the Didit verification workflow, then add the screening your policy requires. Both routes return evidence on the same verification record.
- Choose an available route. Offer a supported national eID or document capture according to the workflow.
- Verify the chosen evidence. A signed eID result supplies the scheme’s attributes; document KYC can supply a portrait for face matching and a liveness check. An eID result alone is not a selfie match.
- Continue into risk checks. Add AML, owner verification or later transaction monitoring according to the account’s requirements, without moving the result into a separate vendor dashboard.
For 1,000 successful document-route verifications with one initial AML check each, the published usage cost is $330 + $200 = $530. That example excludes eID traffic, database lookups and other modules. It is not an estimate of Hopae’s price.
| What an onboarding team needs | Didit | Hopae Connect |
|---|---|---|
| Document fallback and selfie evidence | Document capture, passive liveness, face match and device/IP form the $0.33 core route. Price list | The documented credential routes are national/bank eIDs and chip-based or digital credentials; the cited Connect pages do not document a photo-document and selfie-liveness product. (public source, checked 25 October 2026). |
| Mobile integration | SDKs for iOS, Android, React Native and Flutter, alongside web integration. SDK documentation | Connect’s FAQ says there is no mobile SDK; the customer’s app performs the user step. (public source, checked 25 October 2026). |
| Production path | Open an account and configure a workflow in the Didit console. | Production apps require an Enterprise subscription obtained by contacting Hopae; some connections need additional setup. (public source, checked 25 October 2026). |
For the broader onboarding job described here, Didit provides the document route, evidence, screening and monitoring together.
Public evidence behind the recommendation
The February 2026 report on Spain’s financial sandbox records the project that tested Didit’s solution. Fifty users enrolled in the solution, and the described fraud tests used cryptographic NFC reading with facial biometrics and active liveness. The report describes printed or substituted-photo ID attacks being blocked by the NFC-based flow. Section 4.2 records SEPBLAC’s participation and positive assessment of the reinforced remote-identification measures.
The report’s findings apply to the described sandbox and laboratory exercises.
Didit’s security certification documentation separately lists SOC 2 Type 1 and Type 2 and ISO/IEC 27001.
Didit serves 4,000+ companies. Document coverage spans 220+ countries and territories and 14,000+ document types. Review public customer stories and the document-verification scope.
Inspect the product evidence

Hopae's Go Live guide, read 25 October 2026: production apps require an Enterprise subscription obtained by contacting Hopae. (public source, checked 25 October 2026).

Didit's Hopae alternative page, 25 October 2026: eID, documents, liveness, AML and KYB in one workflow, with a published price per check. (public source, checked 25 October 2026).
Put onboarding and monitoring in the same budget
For a fintech or marketplace onboarding 10,000 people in a month and checking 100,000 transactions, the selected Didit usage is straightforward to calculate.
| Selected module | Calculation | Didit usage cost |
|---|---|---|
| Core KYC | 10,000 × $0.33 | $3,300 |
| Initial AML screening | 10,000 × $0.20 | $2,000 |
| Transaction monitoring | 100,000 × $0.02 | $2,000 |
| Usage subtotal | 10,000 users and 100,000 transactions | $7,300 |
Illustrative USD list-rate budget for successful checks and the stated transaction count. Taxes, plan fees, credits, discounts, ongoing AML, database/eID services, KYB, wallet checks, Investigator and other modules are excluded. Each added module has its own price; a vendor comparison requires a quote for this same scope. Didit module prices.
Switch with an evidence-based rollout
Keep the existing journey available while you validate the replacement. Use this proposed acceptance checklist to agree the rollout with your engineering and compliance teams.
| Existing concept | Didit mapping | Acceptance check |
|---|---|---|
| Verification flow | Rebuild the selected steps and branches in a Didit workflow | Run the same supported document and country mix through both journeys. |
| Historical approval, decline and review statuses | Map source values with status_mapping in the import API | Reconcile every mapped status; investigate unknown or failed rows before expanding. |
| Historical verification records | POST /v3/session/imports/ with workflow_id and dry_run | Validate the dry run, then inspect terminal job status and created, updated, skipped and failed counts. |
| Rules, cases and webhook handlers | Configure these separately in Didit | Check event handling and review ownership. The historical-verification import does not migrate these configurations. |
Start with a small, predefined share of eligible traffic. Agree completion, manual-review and cost-per-approved-user thresholds before the pilot, comparing the same checks and population. Increase traffic only when those thresholds and the import reconciliation pass; route traffic back to the existing journey if they fail. See the import API, webhooks and workflow documentation.
Start with one flow; keep the evidence as you grow
Didit connects onboarding to screening, monitoring and case review on one account and record. Investigator reads verifications, alerts and cases and writes a cited report with a recommendation for $0.20 per reviewed item. Copilot helps build workflows, and the hosted MCP server lets your own agents connect through OAuth 2.1.
Investigator requires Growth or higher and organization enablement; it does not run in sandbox. Sanctions matches go to a person, and it never files a regulatory report. Its per-item charge is separate from plan fees.
The team can review verification evidence on the shared case record.
Watch: Reviewing Cases as a Team (Didit Academy)
Open the Didit console without a sales call and test your chosen workflow. The pricing announcement published on 2 October 2026 states that the Free plan includes $10 of credit every month from 1 November 2026.
Hopae and its marks belong to their owner; references here are nominative, for comparison only, and imply no affiliation. The Hopae alternative page has the side-by-side.