sequenced.ai
Articles/Data & analytics/Blueprint//8 min read

Veriff connects an identity check to the decision a marketplace makes next

Veriff combines automated identity checks and optional specialist review. A seller onboarding case shows how sessions, retries and billing fit together.

By Sequenced deskAI-assisted, source-led · how we work
Visit Veriff website ↗
SessionVerification unitOne session can contain multiple attempts.
EssentialAutomated reviewSelf-serve plan with a hosted verification page.
PlusSpecialist supportAdds human review when automation cannot decide.
WebhookDecision deliveryCarries the result to the operator’s system.
Veriff mark
Veriffveriff.com · independent research

Represent this company? Verify your work email to access its workspace, or send the desk a factual correction.

A marketplace asks a seller to verify their identity. The seller takes a photo, closes the tab and contacts support the next morning. Did they finish the check, get a decision or simply leave the flow? Those events look similar to someone staring at a browser return page. Veriff offers AI-assisted identity verification, but an operator evaluating it also needs to understand the life of a verification session and what that session entitles the marketplace to do next.

In brief
  1. 01The check Veriff offers automated identity verification. Some plans add specialist review when automation cannot decide.
  2. 02The integration A session can contain multiple attempts. The decision can be read in the portal, received through a webhook or retrieved from Veriff.
  3. 03The economics Self-serve identity verification uses per-decision pricing with minimum monthly commitments. Retry attempts are treated separately from billable decisions.

01 / ProductA verification decision inside a larger onboarding process

Veriff’s identity platform helps businesses verify people remotely. Document and biometric checks can support an onboarding flow in which an applicant supplies identity evidence and receives a result. Veriff also offers other verification and fraud services. A business comparing prices should start by naming the actual check it needs. Verifying a person during enrollment, reviewing a transaction and authenticating a returning customer answer different operational questions.

The unit that connects the user experience to the operator’s records is the session. The session creation guide describes creating a verification link and the states a session can take. A person may receive a link without starting, start without finishing, or submit material that requires another attempt. A seller who lands back on the marketplace is telling the application something about navigation. The confirmation the business needs for an identity decision comes from Veriff’s result.

The decision documentation distinguishes approval, decline, a request for resubmission, expiry and abandonment. A separate review status requires prior arrangement. An integration that sets a single box called “verification failed” for every non-approval loses information a support worker needs. A person who needs to finish a session should receive a different response from someone who completed it and received a conclusive decision.

02 / AudienceWho needs to understand both sides of the check?

For a marketplace operator, the relevant team spans seller operations, support and product engineering. Operations sets the conditions for opening a seller account. Engineering receives the verification result and connects it to the pending application. Support is the group that hears from the person who lost a link or does not understand the next step. Include all three when evaluating the flow so that the proposed handling of each result can actually be carried out.

A small team can start by examining the hosted verification page included on the Essential plan. That route gives it a way to observe how an applicant moves through the experience before committing to a more integrated interface. A larger team may need to attach the check to an existing case queue, review exception volumes, match the current account state and manage handling across several countries. Ask which documents and service routes cover the people in the intended population before drawing conclusions from a smooth demonstration by internal staff.

03 / WorkflowRun a seller case across the application and the support desk

For a proposed evaluation, create a test integration and define the seller states the marketplace can represent. Include at least an invitation, an unfinished application, a decision requiring another attempt and a completed outcome. Veriff’s integration guide explains that test sessions do not generate real verification decisions. The tester sets decisions in the portal. That makes the test useful for checking application behavior while leaving recognition performance for a separately authorized live evaluation.

Follow an invitation through the check with the seller operations lead present. Record the identifier assigned to the session and the account record it belongs to. Return to the marketplace before the result is available and ask support what it can tell the applicant. A well-designed pending screen should explain the next action without inventing an outcome. If the user closes the tab, the back office still needs the result when it arrives.

The decision webhook guide describes delivery of the result, the session data and the checks pertinent to the setup. It also documents a timing exception for an SDK flow that asks someone to resubmit on the final screen. A support team should treat a temporary gap as a state it expects. Demonstrate that an incoming decision updates the right application and that a repeated notification does not send the seller the same message twice.

Then walk through a valid request for resubmission and compare it with a final decline. The session guide explains that a resubmission uses the existing session URL. After a conclusive decline, allowing someone another opportunity requires creating a new session. Whether the marketplace offers that opportunity is its own policy decision. Keep separate records of the original result and the later action so that support can reconstruct what happened without relying on the applicant’s memory.

Close the exercise with an approved identity result for a seller who still lacks a separate business document the marketplace requires. The identity check may be complete while the seller account remains pending. Confirm the applicant sees a specific next step and that support can explain both decisions. This is a more revealing demonstration than a single successful check that happens to coincide with immediate account opening.

04 / PricingWhat the US dollar self-serve schedule charges

PlanPer verification and monthly minimumDecision support
Essential$0.80, with a $49 monthly minimumAutomated decisions and a hosted verification page.
Plus$1.39, with a $99 monthly minimumAdds access to specialist review and additional fraud signals.
Premium$1.89, with a $209 monthly minimumAdds features including session deletion by API and bulk export.
EnterpriseCustom quoteVolume pricing, product scope and dedicated support are discussed with Veriff.

Self-serve identity verification terms shown in US dollars on Veriff’s pricing and trial page, consulted 21 November 2026.

For ID verification the page bills decisions and excludes a retry attempt from that unit. The minimum matters when volume is small. At twenty billable Essential decisions, the listed unit rate produces $16 before the minimum. Under the published commitment the base monthly charge would be at least $49, before any extras or applicable taxes. At higher volumes other considerations can dominate, particularly the staff time required to resolve cases or the cost of add-on services.

The page advertises a 15-day trial, up to 50 live verifications and unlimited test verifications. It says the business must complete its own mandatory identity verification during the initial period. The trial limit, length and plan-change conditions deserve attention before introducing real applicants. Confirm the selected plan and the transition to paid use. A manual test result used to check that an email arrives belongs in a different column from an actual production verification decision.

05 / DistinctionsComparing the onboarding choice with adjacent products

Persona’s Blueprint gives a buyer another way to consider the broader orchestration of identity workflows. Start with the end state the marketplace wants to represent and trace where each product supplies evidence, exposes a decision or leaves an operator to assemble the next steps. A team already comfortable with its own onboarding logic may place a higher value on a well-documented verification result than on replacing that logic.

Socure’s Blueprint is relevant when an organization is considering additional identity or risk signals. Ask which evidence is requested from the person, which part of the process is visible to staff and what happens when signals disagree. Run comparisons on the same permitted population and capture the reasons for a referral. A difference in who was invited or what documents were accepted can overwhelm a simple comparison of completion percentages.

06 / QuestionsWho owns the record when the session is over?

A verification record can contain sensitive material. The commercial page describes plan-dependent retention, additional retention options and a Premium deletion feature. Have the team identify which record the marketplace itself needs to retain for its stated purpose, which authorized staff can open it and what is copied into its support system. Deleting a hosted session and removing an attachment someone has already exported are separate operations. Walk through both using harmless test records.

Also inspect who is left out of the success report. Count people invited, people who started, those who returned to submit again and those who obtained a decision. Limiting the denominator to completed sessions hides users who never managed to finish. Examine representative support cases alongside those totals. A high level of uncertainty about which document to present can justify changing the invitation language even when the underlying verification decisions look entirely reasonable.

07 / DecisionChoose a deployment that support can operate

01

A team launching a low-volume marketplace

Start with the hosted experience and calculate the monthly minimum at realistic volume. Check the applicant communications for pending, retry and completed states.

Give support a route for each expected result.
02

An operator comparing automated and specialist review

Confirm the eligible plan and compare review effort, completion and real support contacts on an authorized pilot population.

Report outcomes for everyone invited.
03

A platform integrating several verification products

Map each decision and retention policy to the correct check, account and case owner. Use test sessions to rehearse delivery and live sessions to evaluate the service.

Separate identity verification from the final account decision.
What should we explore next?

A business worth understanding.

Suggest your business or one you find interesting. Tell us what you want to understand about its product, positioning, design or workflows.

Suggestions are free. Selection and publication stay with the desk.

Continue reading

All in this category