Evaluate Alloy for orchestration, Ondato for a scoped onboarding arrangement, Persona for configurable verification journeys, Trulioo for business identity and ownership evidence, and Veriff for its proposed verification package. First inventory the Sumsub products in use. Choose against case continuity, decision authority, data handling and accepted integration evidence rather than brand-level feature counts.
The case you cannot lose when changing identity providers
The applicant has uploaded the documents, a reviewer has requested one correction, and a customer-success colleague has promised to follow up. Then the platform team switches the identity integration. The new dashboard has no record of that conversation. A second verification request goes out, while the original application is still open. The supplier changed; the responsibility to the applicant did not.
A Sumsub alternatives review should start with that operational reality. Identity verification is not only a pass or fail response. It includes the evidence collected, the decisions made, the people allowed to review it, the product actions permitted afterward and the history needed when somebody asks why a decision occurred. Replacing one part without mapping the others can create more work and confusion.
Sumsub's documentation separates user verification, business verification, transaction monitoring, Travel Rule and case-management areas. Establish which products your organization actually uses. The five alternatives below are identity, business-verification and orchestration investigation paths. They should not be assumed to replace every financial-crime or transaction-risk service in a broader arrangement.
Five alternatives, alphabetically, with the role kept visible
| Alternative and primary source | Published role to investigate | A useful selection question | Boundary to resolve |
|---|---|---|---|
| Alloy | Identity and fraud workflows with data orchestration | Do we need to change how several signals are coordinated? | Source contracts, decision ownership and ongoing operating scope |
| Ondato | Individual and business verification with KYC and AML workflows | Do we need a differently scoped onboarding arrangement? | Exact modules, customer population and review responsibilities |
| Persona | Verification, inquiry, account and workflow primitives | Do we need configurable application and review journeys? | Configuration, historical evidence and business-action controls |
| Trulioo | Business verification and ownership-related data workflows | Is business identity and ownership evidence our main gap? | Data sources, entity coverage and unresolved ownership cases |
| Veriff | Identity verification with business-verification offerings listed | Which verification package fits our proposed users and workflow? | Package scope, production availability and contract terms |
This is an alphabetical shortlist, not a claim that the products are identical. The right purchasing conversation depends on the job. A company needing business ownership evidence has a different problem from an application redesigning document capture. An institution coordinating multiple data providers may need an orchestration layer rather than simply a replacement check.
Inventory the actual Sumsub arrangement
Collect the product schedules, integrations, decision rules, data-provider relationships and case queues that are in use. Ask operations to demonstrate one normal case, one incomplete case and one escalated case. Those journeys will reveal dependencies that a product menu or API-key inventory alone may miss.
Separate the commercial relationships behind each component. Sumsub's crypto-monitoring provider documentation distinguishes managed arrangements from bring-your-own-key integrations. That distinction matters when planning a transition: some underlying services may require separate contracts or credentials rather than moving automatically with the visible interface.
Do not turn that example into a claim that every product has the same provider model. Request the arrangement for the modules your organization uses. Record which supplier receives data, who maintains the contract and who owns unresolved cases. A clean product boundary helps procurement avoid buying a replacement for one function while accidentally dropping another.
A ten-criterion identity procurement scorecard
The following criteria are evidence requests, not findings that every alternative provides every function. Use them to approve the proposed workflow, with the responsible compliance, security, privacy and operational owners involved.
| Criterion | Evidence to request | Acceptance exercise |
|---|---|---|
| Population scope | Documented countries, entities and user types for the proposal | Process representative permitted and unsupported cases |
| Check composition | Exact checks, data sources and configurations | Explain which evidence supports each decision |
| Decision authority | Rules, overrides and escalation ownership | Prevent a technical response from authorizing an unrelated business action |
| Case continuity | Status history, reviewer notes and open requests | Continue a case started before transition |
| Business identity | Entity and ownership evidence requirements | Handle an unresolved ownership relationship |
| Integration safety | Authentication, event and status-retrieval contracts | Recover missed and repeated notifications |
| Access control | Roles, credentials and sensitive-data boundaries | Remove a reviewer and verify remaining access |
| Retention and privacy | Applicable agreements and deletion or retrieval procedures | Locate a retained artifact under authorized access |
| Operations and cost | Retry, review, support and source-fee definitions | Compare a representative completed-case workload |
| Exit | Export rights and successor usability | Reconstruct a decision without the incumbent dashboard |
A public capability list is the beginning of this process. It is not a substitute for the configuration, agreement and evidence relevant to your users. Keep accepted items separate from unresolved conditions. Do not average a serious privacy or authority issue into a score that looks reassuring because the user interface performed well.
Alloy: investigate orchestration as an operating decision
Alloy describes identity and fraud workflows with an orchestration engine and data ecosystem. That makes it a candidate when the buyer is reconsidering how checks and signals are coordinated, not only where an applicant uploads a document.
Ask the team to show the proposed decision path with your required sources, fallback conditions and review responsibilities. The key question is what happens when one result is missing, contradictory or late. An orchestration demonstration should make dependencies and authority clearer rather than conceal them behind a single success response.
Use the Alloy profile as an entry point, then request the exact commercial and operational arrangement. A configuration that calls several sources can create separate cost and support dependencies. Compare the proposed arrangement with your existing workload and staffing. Do not assume orchestration eliminates the need for a responsible human decision owner.
Ondato: compare the proposed onboarding scope
Ondato presents individual and business verification alongside KYC, AML and related onboarding offerings. Keep the proposal tied to the specific modules, customer population and operating model being purchased.
Give the supplier a representative case that cannot complete without review. Ask which evidence the applicant supplies, which information a reviewer sees and how a correction is requested. The useful demonstration is not only a smooth successful application. It should show how an unresolved case returns to an accountable queue without restarting the customer unnecessarily.
Ondato belongs in the investigation when the team wants a differently scoped onboarding arrangement. Request the production coverage and implementation responsibilities for the intended service. A broad product menu should not become an assumption that every check, data source or ongoing monitoring requirement is included in the same package.
Persona: test configuration and business-action boundaries
Persona's documentation describes inquiries, verifications, accounts, cases and workflows. Those are useful primitives to investigate when the buyer needs a configurable verification journey rather than a single isolated check.
Ask how the proposed journey represents a person, a verification attempt and the organization's ongoing account relationship. They should not become interchangeable identifiers. A repeated attempt should remain traceable without creating a second business account accidentally. A changed result should be assessed against the policy and product action that the organization has actually approved.
Persona is a useful evaluation path when configuration and application integration are central to the purchase. Test the configured workflow rather than infer its behavior from the existence of a building block. The buyer must still decide what evidence is sufficient, who can override a result and how an application state changes after the identity process ends.
Trulioo: make business ownership evidence concrete
Trulioo's business-verification page describes business data and ownership-related workflows. Evaluate that scope when an organization's main difficulty is establishing the identity of a business and the people connected to it.
Prepare an entity example with a clearly documented ownership relationship and another with an unresolved link. Ask the candidate to distinguish a record located in a source from a conclusion that the buyer is authorized to rely on. The reviewer should understand what was found, where it came from and what additional evidence is still needed.
Trulioo belongs in a business-verification investigation when those data and ownership questions dominate the workload. Request exact entity and jurisdiction coverage for the proposed engagement. Avoid treating a broad geographic statement as proof that a particular company structure, registry source or historical document is available.
Veriff: evaluate the actual package, including current business scope
Veriff's pricing and product page lists identity-verification packages and business verification. Do not carry forward an assumption that its scope is limited to individual document checks. Ask for the current proposed package rather than extrapolate from a remembered older product list.
Show the implementation team the full journey from applicant invitation through final application status. Include a repeated attempt, an interrupted session and a case that needs a reviewer. Confirm which functions belong in the offered package and which require a separate commercial or implementation arrangement.
Veriff is an evaluation path when its proposed verification service fits the defined user journey. The public pricing structure can help frame questions, but it does not establish an all-in price for your workload, optional services or contract. Ask how unsuccessful attempts, repeated checks, reviews and any additional products are treated before comparing costs.
Do not collapse identity, eligibility and transaction risk
A person can complete an identity process without being eligible for a particular product. A company can be identified while ownership evidence remains unresolved. A wallet can have a screening result without establishing who controls it. Maintain separate records and policy owners for those different conclusions.
For a tokenized-asset platform, an identity response should not automatically authorize an investment allocation or a transfer. The relevant product rules and accountable operators must establish eligibility and permissions. This guide does not define those legal requirements; it explains why the technical integration should preserve the distinction instead of hiding it behind a single approved flag.
Likewise, a transaction-risk service is not automatically a replacement for an identity-verification provider. If the incumbent arrangement includes wallet screening, transaction monitoring or Travel Rule functions, inventory each separately. A supplier transition should identify which components remain, which change and which require a different specialist engagement.
An illustrative three-case acceptance pack
Use fictional or properly authorized, appropriately protected records for the evaluation. Do not send genuine applicant documents to an unapproved trial environment merely because a demonstration is convenient. Agree access, handling and deletion arrangements before the responsible team supplies any sensitive evidence.
Case one is a straightforward individual application. The expected outcome includes a traceable verification record and the correct next step in the buyer's application, not just a supplier response. Capture the user-visible message, the backend state and the reference a support colleague can use later.
Case two is a business application with an unresolved ownership relationship. The expected outcome is a controlled review state with a named owner and a clear evidence request. The system should not convert missing information into a confident approval or require the applicant to guess what went wrong from a generic error.
Case three begins before transition and completes afterward. A reviewer has already asked for a correction. Preserve that request and its business reference, then demonstrate how the successor receives or retrieves the permitted evidence. The applicant should not receive conflicting invitations from two active processes simply because the organization changed suppliers.
Migration begins with case ownership
Create an inventory of open cases before planning a cutoff. Separate invited but unstarted applicants, in-progress sessions, pending reviews, correction requests, approved records and rejected or withdrawn cases. Each category can need a different transition path. Do not assume a bulk export supplies the context needed to operate every state.
For each case, name the accountable team and the system that remains authoritative until resolution. A case may appropriately stay with the incumbent while new applications begin elsewhere. That is a deliberate overlap arrangement, not a failure to migrate. Make the support route and final evidence location explicit.
Plan how the application recognizes an existing customer. A new supplier identifier should not create a duplicate account or erase the relationship to prior decisions. Maintain a controlled mapping between business identity and provider-specific attempts. That mapping should survive corrections without turning a display-name match into an authoritative identity conclusion.
Reverification should be a policy decision, not a migration accident
Changing suppliers does not by itself answer whether every person must repeat every check. Have the responsible compliance and privacy owners establish which existing evidence can be relied on, which must be refreshed and which may be transferred or retrieved under the applicable arrangements. Do not invent a universal rule for all jurisdictions or products.
Explain the reason and requested action clearly to affected users. If a new check is required, distinguish it from an application rejection or an account closure. Support should know which process the customer is in and what happens to an unfinished earlier attempt. A migration should not make the applicant responsible for reconciling the organization's supplier records.
Test a customer who uses an old invitation after new applications have moved. The application needs a controlled outcome: continue an authorized existing case, direct the person to the correct process, or explain that the invitation is no longer applicable. It should not create a hidden second workflow whose decision later overrides the intended one.
Events need authentication, ordering and retrieval
An event notification is an input to the integration, not a business decision by itself. Require the documented verification method for the proposed product, preserve the relevant event identity and retrieve authoritative status when necessary. Do not assume different providers use the same event contract because their dashboards show similar labels.
Rehearse a lost notification, a repeated notification and an older event received after a newer decision. The application should avoid duplicate actions and preserve a trace of how state changed. An identity result should not repeatedly grant access, create accounts or trigger financial actions each time a notification is retried.
Define the recovery owner and escalation path. A support agent needs enough reference information to locate the case without receiving unnecessary document access. The integration team should know when it can reconcile automatically and when an authorized reviewer must investigate. A generic retry loop is not an adequate plan for contradictory case states.
Privacy and retention shape the exit package
Inventory the information required to explain an approved decision, including source references, rules, reviewer actions and timestamps. Then distinguish what the organization must retain from what it is permitted to copy or expose. Obtain advice from the responsible privacy and legal owners instead of assuming portability means unrestricted duplication of every document.
Request sample exports and a description of any retrieval dependencies. A successor may need structured case history and stable references while some underlying evidence remains in a controlled system. The exit plan should specify access rights, retention, deletion and support for authorized later inquiries. A downloaded folder without context can be less useful than a governed evidence register.
Test access removal for staff and integrations. A former reviewer should not retain a document-download path after their case-management permission is removed. Check service accounts, exports, recovery contacts and shared operational tools together. Security boundaries should follow the sensitive evidence, not stop at the front door of the new dashboard.
Measure completion and review effort, not just attempt counts
Compare a defined cohort and record what happened to every attempt. Distinguish invited, started, abandoned, completed, reviewed and finally resolved cases. A higher volume of checks is not necessarily a better onboarding outcome. The organization needs to know whether legitimate users reach the intended product state with an appropriate decision trail.
Assess the manual workload as well. Capture the reason for escalation, time spent by role, repeat evidence requests and support contacts. Use authorized test data and an agreed evaluation method. This article does not provide vendor accuracy benchmarks or infer fraud performance from a smooth demonstration.
Watch the experience of incomplete cases carefully. Clear instructions and recoverable sessions can matter as much as the successful-path design. Keep required information proportionate to the workflow and explain what action is needed. The aim is not to remove necessary controls; it is to avoid creating unnecessary repeated work or unexplained dead ends.
Compare commercials using completed-case scenarios
Request the actual charging model for checks, attempts, retries, optional data sources, reviews, monitoring, support and retained access. Use the same representative workload for each proposal. A per-check rate, a package minimum and an orchestration arrangement can describe different purchases, so do not rank them as interchangeable headline prices.
Include implementation and policy maintenance. A configurable journey may require ongoing testing when rules, sources or business requirements change. A broader service can still leave customer responsibilities that need staffing. The relevant cost is the proposed operating arrangement, including the work the buyer retains.
Add a transition scenario with overlapping open cases and historical evidence access. Ask how later corrections or authorized inquiries are handled after new applications have moved. Costing only the new successful journey can hide the support burden attached to the old one. Tie termination and retained-access decisions to actual obligations rather than an optimistic launch date.
Ten questions before choosing a Sumsub alternative
- Which incumbent products and underlying provider relationships are actually being replaced?
- What exact users, entities and jurisdictions does the proposed package cover?
- Which checks and source records support each decision?
- Who owns policy, overrides and business actions after a verification result?
- How will incomplete and escalated cases continue through transition?
- Which existing evidence may be retained, transferred, retrieved or refreshed?
- Can the integration recover missing, repeated and out-of-order events safely?
- How are staff and service-account permissions removed across document access paths?
- What does the same completed-case and manual-review workload cost?
- Can the organization explain a historical decision after the incumbent interface is retired?
Use the answers to make a conditional decision with evidence and accountable owners. Retaining part of the incumbent arrangement can be a reasonable outcome if the alternative only addresses a narrower problem. The objective is a clearer, workable identity operation, not a migration for its own sake.
How we compare and what changed
FluidRWA reviewed the linked primary pages on November 20, 2026 for the limited product-role descriptions above. The case pack, scorecard and migration guidance are original procurement exercises, not independent accuracy tests, legal determinations or customer-specific pricing results. No supplier has been assigned an invented rating or a universal approval recommendation.
Use the KYC and AML directory alongside Sumsub vs Persona vs Chainalysis, Persona vs Alloy vs Socure, and Trulioo vs Veriff vs Ondato. Each addresses a different boundary in the identity and risk stack.
Change note, November 20, 2026: Created a role-based alternatives guide covering case continuity, business identity, evidence retention, reverification and safe integration recovery. The three-case pack is illustrative, not a reported vendor trial. Submit your requirements with the user population, current modules, review workload and unresolved operating problem to receive more relevant proposals.
FAQ
What are the best alternatives to Sumsub?
Alloy, Ondato, Persona, Trulioo and Veriff are starting points for different identity and business-verification workflows. Compare the exact modules, customer population, decision authority and case-management requirements. Do not assume each replaces every product in a broader Sumsub arrangement.
Can a wallet-risk tool replace identity verification?
Not by itself. Identity, business ownership, product eligibility and transaction risk answer different questions. Inventory the actual services and accountable decision owners before replacing a component.
Must every customer repeat KYC when providers change?
That is a policy and evidence question for the responsible compliance, privacy and legal owners. Determine which records may be retained, transferred or refreshed for the relevant service and jurisdiction. A supplier change alone does not establish one universal answer.
How should pending verification cases be migrated?
Inventory their status, prior evidence requests, provider references and accountable owner. Decide which cases stay with the incumbent and which can move under an approved process. Preserve business identifiers and avoid conflicting invitations or duplicate accounts.
What should an identity integration recovery test include?
Test an interrupted session, missed notification, duplicate event and older result arriving after a newer one. Verify event authenticity and authoritative status retrieval. Confirm that retries do not repeat account creation or business permissions.
How should buyers compare identity-provider costs?
Use the same completed-case workload, including attempts, retries, optional sources, manual review, monitoring, support and retained evidence access. Include implementation and transition overlap. Headline rates for differently scoped products are not an all-in comparison.
Build an identity-workflow shortlist
Compare providers against your user population, business verification, review queues and evidence requirements.