Veriff: identity verification, pricing and onboarding integration

Veriff supplies identity-verification and fraud-prevention technology for onboarding and related customer workflows. Its document-and-selfie process examines identification material and the person presenting it. For a broker, this provides evidence for an onboarding case; eligibility for an investment product and approval of the brokerage account remain decisions in the broker’s own process.[1]

Veriff distinguishes Full Auto from Hybrid verification. Full Auto uses automated assessment; Hybrid adds specialist review when needed and is marketed for more complex verification situations. The practical choice concerns review depth, document coverage and exception handling as well as the price of a check.[2]

Additional products include proof of address, screening and business verification. The current KYB material separates company checks against registers and business databases from screening businesses, directors and shareholders. A verified individual and an understood corporate customer therefore involve different evidence.[13][3]

The developer centre lists web, iOS and Android SDKs, API access and a Zapier integration; the self-serve offering also includes a hosted verification page. These routes allow different degrees of control over the customer journey, from a hosted flow to verification embedded within an application.[3][4]

The help article explains the minimum as base usage commitment: additional base verifications are charged after the commitment is exceeded. Extras are separate and do not count towards that minimum. At the displayed rates, 100 billable base verifications therefore imply $80 for Essential, $139 for Plus or $209 for Premium. This calculation uses the greater of the monthly minimum and 100 times the base rate; it excludes add-ons and taxes.[5][4]

The plan page differentiates such features as exports, branding and session deletion. The help text also warns that add-ons can be preselected at checkout. A comparison should use the selected combination, rather than treating the headline verification rate as the total invoice.[4][5]

A public-document conflict remains over trial usage. The pricing page describes a 15-day trial with up to 50 sessions, while the retrieved plan-description text refers to 20 free live verifications. The current account offer needs to establish the allowance before it is used for a cost projection.[4][5]

Test and live integrations serve different purposes. Veriff’s documentation says test sessions are unbilled and their decisions are triggered manually; live integrations require a working webhook and generate processed, billable sessions. Enterprise customers are directed to their Solutions Engineer to create live integrations. Self-serve access to live integration depends on completed account identity verification and an active plan or trial.[10]

The same integration guide calls for rejecting incorrect API keys and mismatched HMAC signatures and handling disrupted sessions. These requirements link a functioning screen to an operational integration: a browser returning to the broker is different from the server receiving and validating a decision. Customer mapping, incomplete cases, resubmissions and retention settings belong in acceptance work.[10]

The published terms define a session as information submitted for processing. The applicable order form determines purchased services and fees; the documented handling of retries within a session should be considered separately from creation of an additional session.[6][11]

The service terms provide standard support unless upgraded support is purchased. They also describe availability efforts, scheduled maintenance and documentation-based commitments; the applicable agreement governs the actual service undertaking.[6]

Veriff’s help guidance says verification cannot be completed by emailing documents or submitting them through support. Customers should use the secure verification flow provided by the business requesting the check, with support used for resolving process or technical problems.[12]

The Data Processing Addendum identifies the customer as controller or business for relevant personal data. It requires lawful instructions, appropriate disclosures and an adequate legal basis, including consent where applicable. The purchased verification service does not determine which laws apply to the broker or establish that its complete onboarding programme satisfies them.[7]

The DPA also addresses permitted business purposes, including service development, testing and fraud prevention, to the extent allowed by law. A buyer evaluating biometric or identity-data handling should read that scope with the retention rules and processing arrangement. This is a statement of the published contractual provisions, not a legal conclusion about a particular customer deployment.[7]

The terms identify the contracting Veriff entity through the order form, with Veriff OÜ and Veriff Brazil Ltda. named as applicable examples. The brand alone does not settle the contracting company.[6]

Veriff announced the acquisition of Vespia on 5 February 2026, with financial terms undisclosed. The announcement proposed integrating its KYB technology by mid-2026. Current product material now markets business verification, company-database checks and screening. This establishes a current product offering, while inclusion in a particular subscription remains a separate commercial question.[9][13]

Operator

Veriff group; contracting entity specified in the order form

Service scope

Identity verification, fraud prevention and related onboarding services, with separately scoped screening and business-verification products.

Customer types

Financial-services businesses; Brokerages; Fintech businesses; Marketplaces; Gaming businesses

Delivery

SaaS; Hosted; API

Pricing publication

Public and quoted pricing

Platforms

Veriff Customer Portal; Veriff Station

Pricing scope

Public self-serve base rates with monthly minimums; enterprise pricing and selected additional services require separate scope.

Implementation

Web and mobile SDKs, APIs, hosted verification and Zapier access are documented. Test and live integrations have separate processing and billing behaviour.

Support

Official support and customer help routes are published. Purchased support and service commitments follow the applicable agreement.

Permissions and regulatory scope

A verification and fraud-technology provider. The customer retains its onboarding decisions and applicable data-protection responsibilities. No financial-services permission is inferred.

Provider metadata checked 20 Oct 2026Source 1Source 3Source 4Source 10Source 6Source 7Source 13

Retention is plan- and service-specific. The retention document directs self-serve customers to their selected plan. For enterprise services outside listed exceptions, it describes 90 days of active storage followed by three years in archive, with archived customer access limited to the shorter of continued customer status or that three-year period. Biometric authentication, proof of address, KYB and backups have separate treatments.[8]

Two details materially affect an exit or retention change: the document says default retention changes generally apply to new sessions, and it separately describes permitted independent retention by Veriff where lawful. Consequently, a new setting or end of access should not be treated as proof that every historical data category and backup has been deleted.[8]

The standard renewal clause requires non-renewal notice at least 30 days before the service period expires unless the order form says otherwise. Disabling an integration and ending the contract are separate actions.[6]