Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Daon?
Daon is a digital identity trust company: it sells enterprise-grade identity infrastructure that helps organizations prove who a user is and confirm they are acting with genuine intent across channels and interactions. The company positions its products around identity fraud prevention rather than general cybersecurity, with a focus on onboarding, authentication and contact-center use cases.
What Daon offers
- Identity verification (KYC): checks a person's identity at onboarding, regardless of location or device, with customization for different markets and risk rules.
- Identity authentication: multi-factor, cross-channel system access and step-up authentication, tuned to balance security against user friction.
- Identity Continuity: a Daon innovation that verifies a customer once, then authenticates them across all channels from a single customer record.
- Identity orchestration platforms: manage the customer identity lifecycle end to end, customized to the organization and its customers.
- Contact center authentication: a multi-layered approach aimed at reducing identity fraud, call times and operating costs.
- Age verification: face-scan estimation, authoritative data matching and full document verification for online proof-of-age rules.
- Deepfake defense: real-time detection of synthetic voice and images, plus additional protective layers.
- Travel document validation: guided, self-managed document checks tied to online check-in, including itinerary-based validation of required forms.
Who it is for
The primary audience is large organizations with regulated or high-fraud onboarding and service journeys: banks and financial institutions, insurers, government and travel operators, telecommunications providers and contact centers. The common thread is a business that must verify identity remotely at scale while meeting compliance expectations.
How to evaluate it
If you are comparing identity vendors, start by mapping your own journey: where do you onboard, where do you re-authenticate, and where does fraud actually occur? Daon's differentiation is the continuity idea — one verified record reused across channels — and the breadth of fraud defenses, including deepfake and contact-center coverage. The trade-off is typical of enterprise identity platforms: broad capability and customization usually mean a heavier integration and configuration effort than a narrow, self-serve tool, so it suits teams with compliance, security and engineering resources rather than a small business wanting a quick plug-in.
A practical next step is to pick one high-friction journey, such as account opening or a call-center password reset, and ask vendors to demonstrate that exact flow with your risk rules. For a second reference point on the category, compare with Okta or Onfido.
How does Daon verify identities during customer onboarding?
Daon verifies identities at onboarding by combining document and biometric checks with data matching, then reusing that verified identity for later authentication. The company describes its onboarding offering as "know your customer (KYC) at onboarding no matter where they are or how they connect," with accuracy and customization as the stated goals.
What happens during onboarding
- Identity verification: The core step, checking that a person is who they claim to be before an account is opened.
- Document and data checks: Page evidence points to authoritative data matching and full document verification as options, particularly in the age-verification context.
- Biometric matching: Daon is known for biometrics, and its age-verification range includes face-scan estimation as well as document-based checks.
- Fraud and deepfake screening: Synthetic voice and image detection are offered as layers against AI-driven fraud, which matters when onboarding happens remotely.
- Identity continuity: Once verified, the customer record is reused so the person can authenticate across channels without repeating full proofing.
A practical reader scenario
A bank wants to open accounts through a mobile app. The applicant photographs an ID document, takes a selfie, and the system compares the two, checks the document against authoritative sources, and screens for signs of synthetic media. After approval, the same verified identity can support later logins and step-up checks. A telco or travel operator could apply the same building blocks to different regulatory requirements.
How to choose
If your priority is stopping first-party fraud at sign-up, weight document verification, data matching and deepfake detection. If your priority is reducing friction after onboarding, weight identity continuity and cross-channel authentication. If you operate in a regulated market, check which verification methods satisfy your specific proofing rules, since the page presents several options rather than a single fixed flow.
For a concrete next step, ask Daon which verification methods are available in your region and channel, and whether their accuracy claims have been assessed against your own document types and user population. Industry recognition, such as the Frost & Sullivan mention on the page, is a useful signal but not a substitute for your own acceptance-rate testing.
How does Daon prevent deepfake and synthetic identity fraud?
Daon's answer is layered: it combines identity verification at onboarding, authentication at every later interaction, and dedicated deepfake detection that looks for AI-generated voice and images in real time. The company frames this as "Identity Continuity" — verify a person once, then authenticate them across channels from a single customer record, so a fraudster cannot re-enter through a weaker channel.
Where each control fits
- Identity verification (KYC) at onboarding: Document and biometric checks establish that the person enrolling is real and matches an authoritative record. Synthetic identities — fabricated combinations of real and fake data — are usually caught here, because they fail document or data-matching checks.
- Identity authentication: Multi-factor, cross-channel authentication for system access and step-up challenges. This limits account takeover after a genuine identity is enrolled.
- Deepfake defense: Real-time detection of synthetic voice and images, positioned as an added layer rather than a replacement for verification. This matters most in remote and contact-center interactions, where a convincing fake voice or face can otherwise pass a human agent.
- Contact center authentication: A multi-layered approach aimed at the phone channel, which Daon describes as a primary source of identity fraud, with the stated goals of shorter call times and less fraud.
A practical scenario
A bank onboards a customer with a selfie and passport scan, then later receives a call requesting a large transfer. Verification stops the fabricated applicant; authentication and voice-deepfake detection protect the call. The trade-off is friction and integration effort: more layers mean more checks, so organizations typically apply step-up only to higher-risk actions rather than every login.
How to decide
Ask which channel carries your worst fraud losses, then start there rather than buying every module. If onboarding fraud dominates, prioritize document and data matching. If account takeover and phone impersonation dominate, prioritize authentication and deepfake detection. Daon's own materials point to the contact center and AI-driven fraud as current pressure points, so those are reasonable first stops for a bank, insurer, or travel provider.
For independent context on the identity verification market, see Frost & Sullivan, which Daon cites for biometric innovation recognition.
How does Daon secure contact center authentication?
Daon secures contact center authentication with a multi-layered approach built on its identity infrastructure: verify the caller once, then authenticate them across channels from a single customer record. The company positions this as protecting the contact center against identity fraud — which it calls the primary source of identity fraud — while also reducing operating expenses, shortening call times and improving the customer experience.
The layers Daon describes
- Identity verification at the start. Know-your-customer checks establish who someone is at onboarding, wherever they are and however they connect.
- Authentication for system access and step-up. A suite of multi-factor, cross-channel methods that can be tuned to balance security against user friction.
- Identity Continuity. Daon's own innovation: verify once, then authenticate across all channels from a single customer record, so a caller who proved their identity in one channel isn't forced to start over in the contact center.
- Deepfake defense. Real-time detection of synthetic voice and images, with additional protective layers, aimed at AI-driven fraud.
- Identity orchestration. A platform layer that manages the customer's identity lifecycle end to end and is customized to the organization's and customers' needs.
Why voice is the hard case
A contact center agent cannot see the caller, and the traditional knowledge-based questions — account numbers, dates of birth, recent transactions — are exactly the data that leaks in breaches and gets traded. Voice is also now cheap to clone, which is why Daon pairs biometric matching with synthetic-voice and image detection rather than treating either as sufficient alone. The trade-off is familiar: stronger checks add friction, so the practical design question is which interactions need a step-up challenge and which can proceed on a lower-assurance signal.
A concrete scenario
A bank customer calls about a disputed card charge. With Identity Continuity, the identity established in the mobile app carries into the call, so the agent can skip interrogation and go straight to the dispute. If the caller instead arrives cold, the system can run verification and step-up authentication before any account detail is disclosed. Daon's own framing of this problem is set out in a discussion between its President of Strategic Initiatives, Conor White, and former Nuance and Microsoft GM of Security & Biometrics Brett Beranek, on protecting contact centers from identity fraud. Their observation is that fraud prevention and customer convenience are usually treated as opposing goals; the useful takeaway is that continuity of identity across channels is what lets an organization stop choosing between them.
How to decide
Ask three questions before buying: Can the vendor carry one verified identity across voice, chat, app and web, or does each channel re-verify from scratch? Does deepfake detection run in real time on live calls, not just on uploaded recordings? And how much of the flow can your team configure without vendor professional services? If your fraud losses are concentrated in the contact center rather than at onboarding, the contact-center and deepfake layers matter more than broad KYC breadth.
For the full solution descriptions, start at Daon. If you want to benchmark the biometric and identity-proofing market more broadly, the analyst recognition Daon cites comes from Frost & Sullivan, whose own materials are at Frost & Sullivan.
How does Daon handle age verification for online services?
Daon treats age verification as one part of its broader identity platform, not a standalone checkbox. According to its page, the options range from face scan estimation (estimating age from a selfie) to authoritative data matching (checking a user against trusted records) and full document verification (reading an ID document such as a passport or driver's licence). That spread matters because different online services face different rules and risk levels.
What each approach is good for
- Face scan estimation: Fast and low-friction. Useful when you only need to separate a child from an adult, such as restricting a social feature or an age-gated purchase. It is an estimate, so it is weaker evidence than a document check.
- Authoritative data matching: Checks the claimed age against a trusted source. Good when you need a defensible answer without asking the user to find and photograph a document.
- Full document verification: The strongest of the three. Appropriate for regulated products, high-value transactions, or anywhere an auditor may later ask how age was proven.
How it fits the wider journey
Daon's page frames these as capabilities within its identity lifecycle offering, alongside identity proofing at onboarding and authentication later on. The practical benefit is that age can be checked once and then tied to the same customer record used for future logins, rather than re-verified on every visit. Daon also lists deepfake defense and travel document validation, which are relevant if your age checks rely on selfies or passports and you are worried about synthetic media or forged documents.
Choosing an approach
Ask three questions:
- What does the regulation require? If it demands documented proof, estimation alone will not do.
- How much friction can you afford? Face estimation keeps sign-up short; document capture adds steps and failure points.
- What is the cost of a wrong answer? For a low-stakes content gate, estimation may be enough. For alcohol, gambling or financial products, the stronger methods are the safer default.
A useful next step is to map your age-gated journeys by risk, then match the lowest-friction method that still satisfies the rule. If you want to see how the pieces are packaged, start with the solutions overview on Daon.
How does Daon's Identity Continuity work across multiple channels?
Daon's Identity Continuity is described as a way to verify a customer once and then authenticate them across all channels from a single customer record. In practice, that means the heavy identity check happens at one point — typically onboarding or first enrollment — and later interactions on other channels reuse that established identity rather than starting over.
What "verify once, authenticate everywhere" means
The page frames Identity Continuity as an innovation driven by market need, providing "full customer journey identity assurance." Read literally, the model has two stages:
- Proofing stage: establish who the user is, once, and bind that to a customer record.
- Authentication stage: on each subsequent channel or interaction, confirm the person is the same individual and is acting with genuine intent.
This contrasts with siloed setups where mobile, web, contact centre and in-person each run their own checks, forcing customers to re-verify and leaving gaps fraud can move between.
Where the trade-offs show up
The appeal is less friction and fewer redundant checks. The cost is architectural: it depends on a single customer record being accurate, shared and trusted across channels, plus orchestration to route each interaction to the right assurance level. If that record is wrong or fragmented, the convenience propagates the error everywhere.
A concrete scenario: a customer completes KYC verification in a mobile app, then calls the contact centre. With continuity, the agent can authenticate against the existing record instead of running knowledge-based questions — which is also where Daon positions its contact centre authentication and deepfake defence layers.
A practical next step
Map your own customer journey and mark every point where identity is currently re-proved from scratch. Those duplicate checkpoints are the clearest candidates for continuity — and the best test of whether a single customer record can realistically serve all of them.
User reviews (0)