Didit vs Hopae: the full verification stack, not an eID add-on

Last reviewed: 25 October 2026 · Not legal advice

Teams looking at Hopae usually want to accept national eIDs and EUDI Wallets at onboarding. Hopae's own customer pages describe the buyer: IDV providers, eSignature providers and financial services such as banks, payment providers, lenders and trading platforms.^[8][10] For them the eID step is one piece of the job. The user still needs a document and selfie check when no eID is at hand, a sanctions screen, often a business check, and monitoring once money moves.

Hopae sells an API hub that lets businesses accept national eIDs and digital wallets that hold identity credentials.^[8] We build Didit, so read this as our side. Every Hopae fact below comes from Hopae's public pages and docs, read on 25 October 2026, and is cited.

Didit vs Hopae at a glance

Hopae column: hopae.com and docs.hopae.com. Didit column: docs.didit.me. "Not documented" means not found on the pages we read, not unavailable.

An eID layer or the whole verification stack

Hopae's own product and IDV-provider pages pitch Connect as a way to complement your existing IDV services by accepting national eIDs.^[1][2] Some eID providers are contract providers, which need an agreement arranged with Hopae before you can use them.^[7]

The rest of the onboarding stack is a different question. Photo document capture and Hopae's own liveness check are not documented on Hopae's public pages (checked 2026-10-25), and neither are AML screening or business verification as Hopae products.^{[5][6][8][10]} If a user has no eID, or your policy wants a document and a face, check how each of those steps would be covered before you sign.

Didit runs that stack in one account. A full KYC check covers ID verification, passive liveness, face match, and device and IP analysis for $0.33, and Didit supports 14,000+ document types.^[11] AML, KYB, transaction monitoring and wallet screening sit in the same account and API, each with its own list price.

One onboarding flow in one Didit account, priced per step.^[11][20][26]

Evidence you can read on every check

Every Didit session decision returns each check's result, the extracted fields, the capture images and videos, and the warnings behind the decision, through one API call.^[12]

Hopae returns the user's attributes, a provenance block (who vouched, how it was presented, when) and, for match-capable providers, a match outcome. Its docs say evidence is included when the credential provides it, relayed from the upstream token with provider-specific key names.^[5]

Native government database checks

Didit's catalog documents government and authoritative database checks in 45 countries plus a Global group: a government register in most countries, and a credit-bureau, financial-services, utility or residential file in some. Each entry lists the inputs it needs, the fields it returns and its prerequisites.^[20] Most of these checks run inside the same workflow and API as the document and selfie; a few, such as Nigeria BVN, are documented as their own database validation API call rather than a workflow-builder step, so check each service's page. Some also need a prerequisite, such as South Africa's Home Affairs photo lookup, which requires the user's recorded consent.^[32] The user needs no eID for the register to confirm them. Where the national register holds a photo, as in Argentina, Nigeria, Panama and South Africa, Didit matches the user's selfie against it.^[21]

Register lookups without the user presenting an eID are not documented on Hopae's public pages (checked 2026-10-25), beyond its match-capable providers.^[4]

Compliance after the identity step

AML screening, business verification, transaction monitoring and crypto wallet screening are not documented as Hopae products on Hopae's public pages (checked 2026-10-25).^[8][10] On Didit they are modules in the same account.

Hopae column checked on Hopae's public pages, 25 October 2026.

Transaction monitoring. Didit scores every fiat or crypto transaction against real-time rules and opens alerts and cases in the same console as the KYC record.^[11][13] It ships over 150 preset rules, and you can backtest a rule against your own history before you switch it on.^[15][16] When a rule flags a transaction, Didit can hold it and ask the user for one selfie, matched against the face they already verified.^[17] Didit drafts SAR, STR and other FIU reports from the case and exports them as goAML XML and PDF for your filing.^[18]

Crypto wallet screening. Screen any crypto wallet address on demand for $0.15 per check, with a signed PDF report.^[11][14] Wallet screening runs on blockchain-analytics providers, and you order it, read it and pay for it in your Didit account. At Hopae, "wallet" means a wallet for identity credentials, such as the EUDI Wallet; crypto address risk is a different job.

KYB with a KYC for every owner. Didit checks the company in registries across 220+ countries and territories, and you choose per country how much registry data you buy: company profile, shareholders, or ultimate beneficial owners. Business verification is priced from $2.00 per business.^[11][25] Didit checks each declared owner and officer against the company's own documents, then screens them and sends each one a linked KYC.^[19]

Agents that do the review work

Didit is agentic: it automates fraud and compliance work that usually needs another analyst. The Investigator agent reads each verification, transaction alert or case waiting for review, writes a report with a recommendation and cites every piece of evidence it used. It decides on its own only within the policy and autonomy level your team sets, it never files a regulatory report, and every decision is logged.^[26] It runs on Didit's Growth plan and above, Didit enables it per organization, it is not available in sandbox, and it costs $0.20 per reviewed item. A support agent answers your users' support conversations from $0.02 per message.

Didit Copilot works inside the Business Console. Describe the verification flow you need and it builds a validated draft workflow, citing the documentation it used; it also creates questionnaires and database validation steps.^[28] Publishing requires your confirmation, and when it edits a workflow, a change card lists what changed and Undo reverts it.^[27]

Your own agents connect through Didit's hosted MCP server at mcp.didit.me, over OAuth 2.1 with Log in with Didit, so there is no API key to paste.^[23] Your AI agent can create, backtest and install transaction-monitoring rules through the Didit MCP, then hand them to you in test mode. Ask why a session was declined and the Didit MCP traces the warning, status rule or reviewer override behind it.^[24] An MCP server or AI-agent tooling is not documented on Hopae's public pages (checked 2026-10-25); Hopae's docs index has no MCP entry.^[9]

A decline explained by your own agent through the Didit MCP.^[24]

Workflows you build and price yourself

Didit's workflow builder shows each step's price while you build, and branches can merge back into one path. The editor flags a branch that contradicts the outcome it routes to, before you publish.^[29] On mobile, Didit's native SDKs ship in modular variants, so you add only the modules your app uses.^[30]

Pricing and going live

Didit publishes a list price for each module and charges a session only for the checks it runs. Open an account at business.didit.me, build in the sandbox and go live on prepaid credits, with no quote to request.

No price list is documented on Hopae's public pages (checked 2026-10-25).^[8] Hopae's go-live guide says production apps require an Enterprise subscription and that you contact Hopae to upgrade.^[3] Its FAQ adds that registration providers get a review before production and contract providers go live after an onboarding call.^[4] Production testing is billable, because it uses real credentials and real provider traffic.^[4]

Switching from Hopae to Didit

• List the onboarding journeys and countries you run through Hopae, and the term of your Enterprise subscription.
• Rebuild the flow in Didit's workflow builder or with Copilot, adding the checks you buy elsewhere today.
• Map your current outcomes to Didit's Approved, Declined and In Review in your backend and webhooks.
• Route a share of new sign-ups to Didit and compare completion, fraud caught and total cost on your own users.

1. Day 1Open an accountSandbox and console, no quote to request.
2. Week 1Build and testWorkflow, webhooks, your own documents.
3. PilotRun in parallelA share of traffic on each setup.
4. RenewalConsolidateWhen your current agreements allow.

A staged switch. Timing depends on your volumes and your current contracts.

How Didit helps teams switching from Hopae

See the Hopae alternative page for the side-by-side, the pricing page to price your flow, or the MCP guide to connect your agents.

Frequently asked questions

Sources

1. Hopae Connect, Hopae, read 25 October 2026.
2. For IDV providers, Hopae, read 25 October 2026.
3. Go live, Hopae docs, read 25 October 2026.
4. FAQ, Hopae docs, read 25 October 2026.
5. Return data model, Hopae docs, read 25 October 2026.
6. Digital ID types, Hopae docs, read 25 October 2026.
7. Providers and credentials, Hopae docs, read 25 October 2026.
8. Home page, Hopae, read 25 October 2026.
9. Docs index (llms.txt), Hopae docs, read 25 October 2026.
10. For financial services, Hopae, read 25 October 2026.
11. Pricing, Didit docs, read 25 October 2026.
12. Retrieve session, Didit docs.
13. Transaction monitoring overview, Didit docs.
14. Wallet screening, Didit docs.
15. Transaction rules API and backtesting, Didit docs.
16. Rules library, Didit docs.
17. SDK transaction submission and step-up, Didit docs.
18. FIU reports, Didit docs.
19. Key people, Didit docs.
20. Database validation supported countries, Didit docs.
21. Non-document lookup and registry photo match, Didit docs.
22. Nigeria BVN, Didit docs.
23. MCP server overview, Didit docs.
24. MCP tools, Didit docs.
25. KYB supported countries and data tiers, Didit docs.
26. Investigator agent, Didit docs.
27. September 2026 changelog, Didit docs.
28. August 2026 changelog, Didit docs.
29. Workflows, Didit docs.
30. Native SDKs overview, Didit docs.
31. New pricing from 1 November 2026, Didit blog.
32. South Africa DHA photo retrieval, Didit docs.

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.