Persona, Sumsub and Alloy can all be considered for identity-related onboarding, but a useful comparison starts with the workflow you need to operate. Your engineering team must connect collection, verification results, manual review and the product's own access rules. A list of vendor features does not settle those decisions.

This engineering comparison was checked against the linked vendor documentation on 17 November 2026. It distinguishes documented integration behaviour from questions to resolve in a pilot and contract. It does not assign an overall winner or treat a provider's marketing results as your expected outcome.

Define the onboarding decision before shortlisting vendors

Write down the applicant types, launch countries, documents or data available, channels and decision owner. Individual identity verification, business verification, screening and ongoing monitoring are related but different requirements. Have the people responsible for your compliance programme specify which checks and evidence the product needs.

Also describe what happens after a result: immediate access, restricted access, a request for more information, rejection or a reviewer queue. Decide how someone can resume an unfinished application and how support staff will investigate it. These details influence integration effort and operating cost.

Persona vs Sumsub vs Alloy: integration comparison

QuestionPersonaSumsubAlloy
How does the journey start?Hosted or embedded inquiry flows are documented. Select the method that fits your product and channel.WebSDK, MobileSDK and API integration are documented, with verification levels defining required checks.Journeys use an application object to coordinate the configured decisioning flow.
How does the backend follow progress?Webhooks report resource events; versioning, retries and out-of-order delivery need consideration.Verification webhooks expose progress and review events; workflow configuration affects when final events arrive.Synchronous responses are accompanied by webhooks for asynchronous steps and subsequent events.
What needs a deliberate implementation decision?Inquiry identity, repeat visits, resuming the flow and matching events to your customer.Applicant identity, verification level, resubmission and the complete review result.Application status, final outcome, manual review and step-up actions.
What should a pilot establish?Completion and recovery behaviour with the selected inquiry configuration.Completion and review behaviour with the selected levels, checks and channels.Whether the proposed Journey and its configured checks produce the required decisions and evidence.
What must be confirmed commercially?Included checks, plan features, usage units, minimums, support and retention options.Included checks, billable events, minimums, additional products and support.The proposed platform configuration, underlying services, commercial terms and implementation responsibilities.

Sources for this table: Persona's Hosted Flow, Embedded Flow and webhook documentation; Sumsub's User Verification overview and verification webhooks; Alloy's Journey integration guide. The pilot questions are our evaluation framework, rather than vendor performance claims.

Persona: plan inquiry identity and event handling

Persona's Hosted Flow documentation distinguishes generic template links from unique inquiry links. It notes that reopening a generic link creates another inquiry, and recommends API-created unique links for production use. Test how your application connects an inquiry to the customer record and allows an interrupted flow to resume.

The webhook guide says events may arrive in a different order from their creation and documents delivery retries. Design your result handler around recorded event identity and an explicit state transition policy. A browser redirect alone should not grant product access.

Sumsub: check the level and the complete result

Sumsub describes verification levels as the configuration selecting the checks an applicant passes. Its verification webhook guide distinguishes progress, hold, review and workflow events. With a workflow, applicantReviewed is deferred until that workflow completes.

For implementation, model pending work and requests for additional information separately from approval. Test your configured flow, rather than assuming that one completed document check establishes the overall application result. Record the external applicant identifier so an event can be reconciled with the correct product account.

Alloy: distinguish progress from a final outcome

Alloy's Journey integration guide documents both synchronous responses and asynchronous webhooks. It separates the application status from complete_outcome, which remains empty until a final decision is assigned. Your product needs a defined experience for waiting, manual review and additional information.

A concrete point to check in an implementation proposal: the current guide marks Document Verification Nodes as deprecated for new integrations and directs readers to Step Up Nodes. Confirm the supported approach with the implementation team before building against an older tutorial.

Measure a pilot with comparable inputs

Use an approved test set and a written protocol. Keep the intended countries, applicant types, supported documents and decision rules comparable. A sandbox proves integration behaviour; it does not establish production fraud-detection or conversion performance.

MeasureDefine before testingWhy it matters
CompletionCompleted attempts divided by eligible started attempts, with a fixed observation windowDistinguishes abandonment from unfinished work
Decision timeStart and end events, including whether reviewer waiting time is countedMakes results comparable
Manual reviewShare needing a reviewer and minutes per reviewed applicationConnects the flow to operational capacity
Incorrect outcomesAdjudicated examples, error definitions and sample limitationsPrevents approval rate being mistaken for accuracy
RecoveryInterrupted, repeated, expired and resumed attemptsChecks real support and retry behaviour

Inspect individual failures and the distribution of results, not just a single average. Record configuration versions and changes during the pilot. Do not compare different check sets and call the faster one universally better.

Compare the full operating cost

Ask every vendor to price the same expected workload and required checks. Clarify what is charged when a person retries, abandons, needs additional checks or enters manual review. Include implementation, internal reviewer time, support, data handling and changes to the onboarding flow.

Persona and Sumsub publish Persona pricing information and Sumsub pricing information. Use the current plan details and written proposals rather than treating headline prices as equivalent packages. Obtain an Alloy proposal for the configuration being evaluated. This article does not report a price-per-verification ranking because the required checks and billable units have not been normalised.

A useful calculation is total onboarding cost / applications reaching the intended usable outcome. Count spend on abandoned and rejected attempts too. A high approval rate is not sufficient evidence of either suitable controls or low operating cost.

Questions to settle before signing

  • Which countries, applicant types, documents and channels are in the agreed configuration?
  • Which checks require extra products, data services or commercial terms?
  • How are events authenticated, retried, reconciled and investigated?
  • Who owns manual decisions, escalations and support outside normal hours?
  • What information is retained, where is it processed, and how are deletion and access requests handled?
  • What can be exported when changing providers, and which material cannot be transferred?
  • What assumptions would change the integration estimate or monthly invoice?

Use our editable supplier comparison worksheet to record each answer and its evidence. Leave an unanswered requirement visibly unresolved instead of awarding a vendor an assumed pass.

Scope the integration as part of the product

Document the journey, backend states, permissions and operational responsibilities in your discovery brief. Our fintech security guide covers the surrounding application controls. EmphaSoft's fintech development teams can help implement the agreed flow; bring your onboarding requirements to discuss the work and its dependencies.