Entrust Identity Verification

Entrust presents the former Onfido identity verification technology under the Entrust Identity Verification name. Buyers researching Onfido verification therefore need the current product documentation alongside their existing integration records, especially when planning mobile SDK changes or renewing a supplier contract.

The current developer documentation includes migration guidance for previous Onfido capture integrations. A technical review should inventory deployed SDKs, supported applications, workflow configurations and stored identifiers before estimating migration effort. A product name change alone does not specify technical requirements for individual deployed applications.

Document verification examines submitted identity documents and returns structured findings about the evidence. Facial similarity checks assess whether a captured face matches the photograph on the document, with the available capture methods determining which additional liveness checks apply.

The official facial similarity documentation explains the differences between supported report types. Financial teams should test the configured combination against their actual document mix, accessibility requirements and customer channels, because a successful capture alone does not establish an approved customer relationship.

Entrust combines document and biometric checks with fraud detection capabilities for digital identity journeys. These capabilities address risks including manipulated identity evidence, presentation attacks and suspicious activity signals, while the selected workflow determines how individual results influence the next step.

A lender still needs an explicit process for inconclusive evidence, customer retries and cases requiring staff review. A useful evaluation compares false rejections, unresolved cases and review time alongside detected fraud, using representative applicants and recording acceptance rates within that wider operational context.

The Workflow Studio product connects verification steps through configurable journeys and conditional logic. Teams can adapt a journey to geography, customer risk or available evidence, while keeping the connection between an application and its verification outcome.

For financial businesses, this raises questions about who can change a workflow and how changes are approved before release. The broader discipline of identity orchestration in finance also covers routing between methods, continuity during provider failures and consistent evidence across customer channels.

The Entrust Identity Verification API supports creating applicants, starting workflow runs and retrieving results. Capture SDKs provide the customer interface, while backend services manage credentials, connect verification records with account applications and process asynchronous updates.

Implementation planning should cover duplicate submissions, interrupted capture, delayed results and secure handling of callbacks. Teams also need a clear separation between the customer finishing an interface and the institution accepting the verification outcome, with integration tests covering both routine approvals and exception paths.

An identity verification result supports a defined part of financial customer due diligence. The institution still determines the permitted identification method, the required evidence and the remaining checks for its product, customer type and operating markets.

Procurement should examine document coverage, data processing terms, retention controls, manual review arrangements and access to verification evidence. Providers such as IDnow offer other identification approaches, while the profile of WebID explains its own methods; comparing them requires matching the same customer journey and evidence requirements.

Entrust now markets the former Onfido identity verification technology as Entrust Identity Verification. Existing implementations can still contain earlier naming, so teams should use the current migration guidance and their specific contractual documentation when reviewing deployed integrations.

Identity verification addresses the evidence needed to establish who an applicant is within a configured process. Financial businesses still assess the other due diligence requirements relevant to their services, and reusable KYC involves additional questions about evidence sharing, freshness and responsibility.