Compare the best IDnow alternatives for 2026: why teams move beyond VideoIdent, how Zyphe removes the vendor-held PII store, and how to migrate without risk.
Table of contents
- IDnow is a Munich-based identity verification provider, founded in 2014, best known for VideoIdent, its live video identification procedure, and AutoIdent, its automated product; it combined with French provider ARIADNEXT in 2021 to form a pan-European platform.
- Teams start evaluating IDnow alternatives when human-assisted video identification becomes a cost and completion bottleneck, or when they expand beyond DACH and want one automated flow across EU markets.
- Video identification is under structural pressure in Germany: the Chaos Computer Club demonstrated bypasses in 2022, gematik banned the procedure in the health telematics infrastructure, and eIDAS 2.0 puts EU Digital Identity Wallets on the map from the end of 2026.
- Most IDnow alternatives keep the incumbent architecture: the vendor verifies your users and holds the resulting identity data. Zyphe splits every record into encrypted fragments across independent nodes, and the customer holds the key.
- Migration does not require a hard cutover: a parallel run on a slice of live traffic, then a segment-by-segment switch, protects conversion while you compare real numbers.
- IDnow remains the right choice where BaFin-compliant video identification or bundled qualified electronic signatures are non-negotiable.
IDnow alternatives are identity verification providers that regulated companies evaluate instead of the Munich-based vendor behind VideoIdent and AutoIdent. Teams compare them on automation across EU markets, data architecture and residency, reusable credentials, and commercial flexibility, because strength in German video identification does not always translate into fully automated, privacy-first onboarding elsewhere.
TL;DR
IDnow earned its position in German banking with VideoIdent, the live video procedure BaFin recognises under Circular 3/2017 (GW), then broadened into automation with AutoIdent and the 2021 ARIADNEXT combination. Teams look at IDnow alternatives for three reasons: the cost and drop-off of human-assisted identification at scale, the wish for one automated flow across the EU, and a data architecture question the whole incumbent category shares, because the vendor verifies your users and keeps the resulting personal data. Zyphe answers that last point differently: records split into encrypted fragments across independent nodes, keys held by the customer, reusable credentials as standard, per-region residency for EU-first teams.
What is IDnow and what does it do well?
IDnow is an identity verification provider headquartered in Munich and founded in 2014. Its signature product is VideoIdent, a live video interview in which a trained ident specialist checks the user's identity document and face in real time. That procedure made IDnow a fixture of German financial services, because BaFin explicitly recognises video identification for institutions it supervises, subject to the detailed requirements of Circular 3/2017 (GW). Alongside it, AutoIdent covers automated, AI-supported document and biometric verification, and the platform extends into eID schemes, electronic signatures up to qualified level, and fraud signals.
In 2021 IDnow combined with ARIADNEXT, the French identity technology provider, to position itself as a pan-European platform with a strong footprint in Germany and France, and in March 2025 it announced a strategic majority investment from Corsair Capital. Credit where due: for German banking flows that depend on video identification, and for ident flows bundled with qualified electronic signatures, IDnow is one of the most proven options in Europe.
Why do teams look for IDnow alternatives?
The first trigger is operational. Human-assisted video identification is thorough, but every session needs a trained specialist, a stable video connection and a user willing to sit through an interview. At scale that shows up as queue times, abandonment and per-check economics that automated flows do not carry. Teams whose growth is outside the segments that mandate video identification end up paying a Germany-shaped premium across their whole funnel.
The second trigger is geographic. IDnow's procedures map closely to national regimes, VideoIdent for BaFin-supervised institutions being the clearest example. A company scaling from DACH into the rest of the EU often wants the opposite shape: one automated flow, tuned per market by rules rather than by procedure, which is the pitch most centralised competitors make too, as our identity verification software comparison shows.
The third trigger is the one this cluster keeps returning to: data architecture. Whichever procedure runs, the incumbent model ends with your users' documents and personal data sitting in storage the vendor operates. BaFin's circular even requires the entire video identification session to be recorded and retained in audio and video. That archive is a liability with a long tail, the theme we unpack in why your KYC vendor is your biggest data breach risk. Searches for IDnow alternatives usually start with cost, and end with the question of who holds the data.
What are the best IDnow alternatives in 2026?
The best IDnow alternatives in 2026 split into two categories: privacy-first architecture, where Zyphe currently stands alone, and credible centralised platforms, covered in depth in our KYC verification services comparison.
| Vendor | Best for | Data architecture | Notable consideration |
|---|---|---|---|
| Zyphe | EU-first teams that want automated KYC without holding PII | Records split into encrypted fragments across independent nodes; customer holds the key | Agents run verification and L1 review as a service; usage based with no minimum |
| Sumsub | Broad multi-product coverage across KYC, KYB and monitoring | Centralised, vendor-held storage | Wide toolset can exceed what a focused onboarding flow needs; see our [Sumsub alternatives guide](/resources/blog/sumsub-alternatives) |
| Onfido | Document and biometric automation for high-volume onboarding | Centralised, vendor-held storage | Evaluate roadmap and support as part of a larger group; see our [Onfido alternatives guide](/resources/blog/onfido-alternatives) |
| Veriff | Conversion-focused automated verification | Centralised, vendor-held storage | Strong on speed and pass rates; see our [Veriff alternatives guide](/resources/blog/veriff-alternatives) |
| Jumio | Enterprise programmes with global document coverage | Centralised, vendor-held storage | Enterprise-oriented commercial model; see our [Jumio and Trulioo alternatives guide](/resources/blog/jumio-trulioo-alternatives) |
Two honest notes on the table. First, the centralised vendors differ meaningfully in strengths, and for some teams one of them, not Zyphe, is the right pick among IDnow alternatives. Second, only one column separates categories rather than brands: every vendor above except Zyphe retains verified identity data in infrastructure it controls, a distinction we map in our review of privacy-first identity verification vendors.
What makes Zyphe different from IDnow?
IDnow's model, human-assisted or automated, ends with verified identity data held by the vendor. Zyphe inverts that. Every verified record is split into encrypted fragments spread across independent nodes, and the encryption key is held by the customer, not by Zyphe. There is no master key on Zyphe's side, so a breach of any store recovers scattered fragments, never whole identities. For EU-first teams, residency is handled per region, so French records can stay under French residency rules and German records under German ones, without a central vault that spans both.
The operational model differs too. Zyphe's agents run verification and L1 review as a service, so you keep the judgement layer that made human-assisted identification attractive without staffing it or queueing users through interviews. Reusable credentials come as standard: a user verified once can re-present that verification instead of resubmitting documents, via KYC Passport. API integration is targeted at around 15 minutes, and the commercial model is usage based with no minimum. The full architecture is set out on our how it works page and the KYC software product page.
What is happening to video identification in Germany?
If your attachment to IDnow is VideoIdent, the German context deserves a clear-eyed look. Video identification remains a recognised procedure for BaFin-supervised institutions under Circular 3/2017 (GW), and nothing here says otherwise. But three developments define the direction of travel.
First, security research dented confidence in the procedure itself. In August 2022 the Chaos Computer Club published research demonstrating bypasses of video identification services, and gematik, the German digital health agency, immediately banned the procedure in the health telematics infrastructure. That ban was sector-specific and did not change BaFin's rules, but it put the method's ceiling on public record. Second, the recording obligation cuts against privacy: a compliant video session is retained as an audio-visual file, which deepens the stored-data problem. Third, the EU has scheduled the successor. eIDAS 2.0 entered into force in May 2024 and obliges member states to offer EU Digital Identity Wallets by the end of 2026, while the EU AML Regulation harmonises onboarding rules from mid-2027; our eIDAS 2.0 and KYC guide covers what that means for onboarding stacks. A verification layer built around per-session video interviews sits awkwardly in that future; one built around automated checks, reusable credentials and customer-held keys sits naturally in it.
How do you migrate from IDnow without disruption?
Treat the move as a controlled experiment, not a leap. The playbook we run with teams switching to IDnow alternatives has five steps. First, parallel run: keep IDnow serving production while the new vendor handles a slice of live traffic, so you compare completion and decision quality on real users. Second, map your onboarding steps and risk rules from the old configuration to the new one, including the cases VideoIdent handled through a human specialist. Third, integrate the API; with Zyphe the integration itself is targeted at around 15 minutes, so the effort concentrates on your own routing logic. Fourth, cut over by segment or geography, starting where the evidence from the parallel run is strongest. Fifth, decommission: close the old integration and request deletion of stored personal data under your data processing agreement, which is the step teams most often forget and the one that actually ends the honeypot. The full playbook, including what to ask each vendor before you start, lives in our vendor switch hub.
When should you stay with IDnow?
An honest comparison cuts both ways, and there are cases where staying is the right call. If your legal or partner-bank requirements specifically call for BaFin-compliant video identification, IDnow is one of the most established providers of exactly that, and an alternative would still need an equivalent procedure for those flows. If your onboarding is inseparable from qualified electronic signatures, IDnow's bundling of identification and signing in one flow is a real advantage. If your volumes concentrate in Germany and France, its home-market depth, built up since 2014 and extended through ARIADNEXT, is hard to replicate. And if you have just renegotiated terms and your completion rates are healthy, the switching cost may not pay back this cycle. In those situations the better move is to benchmark quietly, as described below, and revisit when the contract or the regulation moves.
How should you run the evaluation?
Run the comparison on your traffic, not on vendor decks. Put a real slice of production volume through each candidate for two to four weeks and measure completion rate, median time to decision, manual review rate and the outcomes of those reviews. Include the awkward cohorts: older users, poor connections, documents from your hardest markets, because that is where human-assisted and automated flows diverge most. Ask each vendor the architecture questions in writing: where verified data is stored, who holds the keys, what is retained after a user is offboarded, and what deletion looks like under the DPA. Time the exercise against your renewal date so the decision is yours rather than the calendar's. Our comparison hub gives you the shortlist; a demo puts Zyphe into that bake-off in a day. Evaluations of IDnow alternatives run this way settle the debate with numbers instead of opinions.
The bottom line
IDnow solved the problem German regulation defined: identify a person remotely, on video, to a standard BaFin would accept, and it remains excellent within that frame. The frame itself is moving. Automated verification, EU Digital Identity Wallets and a harmonised AML rulebook reward architectures that verify without accumulating recordings and documents in a vendor's store. The strongest IDnow alternatives are not simply cheaper or faster versions of the same model; the one worth the migration effort changes who holds the data. Verify once, split the record into encrypted fragments, give the customer the key, and the five-year archive stops being someone else's breach headline waiting to happen.
Related resources
- Vendor switch hub
- Sumsub alternatives
- Onfido alternatives
- Veriff alternatives
- Jumio and Trulioo alternatives
- Identity verification software comparison 2026
- Why your KYC vendor is your biggest data breach risk
- Zyphe KYC software
Cited sources
- IDnow and ARIADNEXT combine to create a pan-European identity verification platform (IDnow press release, June 2021)
- IDnow announces strategic majority investment from Corsair Capital (IDnow press release, March 2025)
- BaFin Circular 3/2017 (GW): video identification procedures
- Chaos Computer Club hacks Video-Ident (CCC, August 2022)
- Regulation (EU) 2024/1183 establishing the European Digital Identity Framework (EUR-Lex)
- Regulation (EU) 2024/1624 on the prevention of the use of the financial system for money laundering (EUR-Lex)
Michelangelo Frigo (Co-Founder at Zyphe) Michelangelo Frigo is a privacy and identity infrastructure expert and co-founder of Zyphe.