Entrust combines AI identity verification with configurable trust workflows

Entrust brings AI-powered identity verification into its wider identity and security portfolio. The former Onfido offer now operates as Entrust IDV, with tools for designing verification journeys, capturing customer evidence and connecting results to business decisions.

01 / ProductOne current identity for the former Onfido offer

Entrust's transition page explicitly identifies Onfido as Entrust IDV. The company also offers identity and access management, cryptographic security and issuance products; this blueprint focuses on the AI-related verification capability within that wider portfolio. Some official integration domains still contain Onfido, which is a continuity detail rather than evidence of a separate current company offer.

The IDV product page describes document, biometric and data-based verification combined with fraud signals. Workflow Studio orchestrates the journey, while Smart Capture provides the user-facing evidence collection. This separates three functions that are often confused: asking a user for information, checking that information, and deciding what the business should do with the result.

That separation matters in an AI-assisted process. Extracting a name from a document can help route the next step without proving that the document is authentic. A face capture can provide input to a check without establishing that the person matches the ID. The business needs a decision policy that explains how these pieces combine and how uncertain or contradictory evidence is handled.

02 / AudienceOrganizations that need control over verification journeys

Entrust IDV is relevant to remote customer onboarding, sensitive account changes and workforce identity proofing. It is especially worth examining when a business needs different journeys for different markets, document types or risk levels. Product teams can work on completion, while fraud and compliance teams define the evidence and escalation rules the journey must satisfy.

A team with very low volume may prefer a hosted route and manual reconciliation. A high-volume digital service is more likely to need account-linked workflows and automated result handling. Both need a clear owner for exceptions. A no-code builder reduces some implementation work, but it does not make the resulting decision policy self-explanatory or remove the need to test it.

Okta provides an adjacent comparison around workforce access and authentication. Entrust's identity proofing can be part of such a lifecycle without replacing the access system's authority. Sumsub is a more direct reference for identity and compliance orchestration. Compare specific journeys, evidence coverage and operational responsibilities rather than treating all identity tools as substitutes.

03 / WorkflowA proposed account-opening flow with a stable record

Consider a proposed customer onboarding journey using Workflow Studio. Begin with a defined market and accepted document set. Build an activated workflow that captures the required evidence, runs the chosen checks and produces explicit outcomes for acceptance, rejection or review. This is an illustrative implementation plan, not a claim that Sequenced tested Entrust in a live onboarding system.

Use the API to associate a workflow run with the correct applicant and obtain the information needed to launch capture. Entrust recommends its SDKs for media collection because direct uploads limit available products and omit capture-related quality and fraud protections. The choice of capture route therefore affects assurance, not just how the interface looks.

When the user finishes interacting, the business should wait for the verification outcome rather than interpret the return to its website as approval. Preserve the relationship between the applicant, workflow run, workflow version and account action. That record lets an investigator reconstruct which policy was applied and prevents a result from being accidentally reused for a different purpose.

The best-practices guide recommends a stable applicant mapping and checking for an existing active run before creating another. In the proposed flow, a returning user would resume the appropriate unfinished journey instead of generating duplicate attempts. Test interruptions, delayed callbacks and review cases alongside success. A realistic evaluation should show that the business can reconcile what happened even when the customer closes the browser halfway through.

04 / PricingCommercial scope follows the journey and capture route

Entrust provides a sales contact route and product demonstrations; the reviewed material does not establish a universal public IDV tariff. Describe the intended verification journey, countries, volume and capture route when requesting terms. Avoid assuming that a free trial or access to documentation establishes production entitlements or the price of all available checks.

Ask which verification methods, fraud signals, hosted features and support services are included. Clarify how the agreement treats retries, abandoned runs and manual review, without presuming any particular billing unit. An organization with many interrupted journeys can have a different cost profile from one with the same number of accepted customers but fewer attempts.

The Smart Capture Link guide distinguishes a generic no-code link from a light integration that creates an individual link for a known applicant. The generic route has no automatic matching to the buyer's own user records. That is an important cost tradeoff: less initial engineering can mean more manual reconciliation. Compare the complete operational process instead of only the effort needed to display the first verification screen.

05 / DistinctionsVersioned orchestration makes policy changes tangible

Workflow Studio records saved workflow versions and requires a valid active version for new runs. It also describes gradual rollout between variants. That gives teams a concrete way to manage changes to verification policy. The value depends on disciplined use: retain the reason for a change, define the affected population and compare outcomes before expanding a new route.

The hosted-link option can reduce SDK maintenance while retaining backend result handling in the light-integration approach. An organization may later embed capture more deeply without rebuilding every downstream step. The design question is which parts of the customer experience need direct control and which can reasonably be hosted by the verification provider.

These capabilities are useful because identity policies evolve. A new document category, a changed fraud pattern or a revised business rule may require a different journey. A controlled workflow makes that change reviewable. It should also make it possible to explain why two customers took different paths without relying on informal knowledge held by one developer or operations manager.

06 / QuestionsNo-code workflows still have consequential failure modes

Entrust's best-practices documentation warns that some branch and join arrangements can deadlock. It also advises against placing manual review between interactive applicant steps, where the user may be left waiting. These are specific operational limits, not a reason to avoid orchestration. Test every branch and ensure reviewers can act after the customer has been given a clear completion or waiting state.

Treat automatic data extraction as a distinct capability from high-assurance verification. The same guide describes Autofill as a triage and light-verification tool rather than a basis for critical decisions. If an extracted value routes a customer into a different process, test what happens when that value is missing or wrong. A convenient prefilled field can otherwise become an unnoticed policy decision.

The API reference also separates sandbox and live operation and warns against putting confidential personal data into the sandbox. Use the appropriate test process and establish retention and deletion arrangements before handling real identity evidence. Review webhook authenticity, result correlation and retry behavior as part of the integration; an accurate vendor result is not useful if the application assigns it to the wrong account.

Several public marketing pages were intermittently inaccessible during research, so this blueprint relies on the accessible product overview and detailed official guides for implementation claims. It does not assert a benchmark for fraud detection or claim that every verification option is available in every region. Confirm supported documents, account enablement and relevant SDK compatibility for the exact journey.

07 / DecisionStart with a reviewable verification policy

Entrust IDV is a strong candidate when an organization needs to combine several identity checks and evolve the journey deliberately. Begin with a policy that a fraud analyst, product owner and engineer can all explain. Then select the capture route and workflow that implement it, including what happens when evidence is incomplete, contradictory or interrupted.