Veriff

Identity verification and fraud signals

Veriff focuses on identity verification and biometric authentication, with fraud intelligence, proof of address, AML screening, and a listed KYB offering. It states that specialist partners supply adjacent checks such as database verification and screening. Confirm what is native and what is partner-delivered in your package.

Our assessment

Strong identity verification focus with adjacent checks; do not equate it with complete underwriting or AML operations.

Best fit and limitations

A relevant IDV candidate when device and session signals can improve onboarding fraud controls. Compare its KYB and AML add-ons on evidence quality and operating workflow, not only convenience.

AML screening is not an AML transaction-monitoring engine.
Partner-provided checks can carry distinct coverage, service, and licensing limits.
Verification acceptance is not a merchant credit, reserve, or settlement decision.

Tools 7

Identity VerificationIdentity proofing

Document, face match, and liveness checks
Network and device context during verification

Source 1

Fraud ProtectSession risk

DocCheck and FaceCheck for manipulation signals
DeviceCheck for device and network indicators

Source 2

Fraud IntelligenceLinked risk

Connect suspicious sessions and identities
Enrich analyst fraud decisions

Source 3

AML ScreeningCustomer risk screening

Sanctions, PEP, and adverse media checks
Ongoing monitoring of existing customers

Source 4

Biometrics, address, and KYBAdjacent verification

Authentication and address verification offerings
Business verification listed; confirm source and country coverage

Source 3

Zapier workflow integrationConnected event automation

Trigger configured external actions from verification decisions or session events
Connect to CRM and other applications through Zapier

Source 8

Metadata Database VerificationConnected identity-data checks

Validate supplied identity fields through DataZoo sources
Return field-level validation through a separately configured API integration

Source 9

AI capabilities

Verification models + fraud intelligence

Veriff uses AI and fraud analysis across documents, biometrics, devices, and session context. Screening adds separate data and matching functions.

Find document manipulationDetect face and session anomaliesLink suspicious sessions

What to validate

Evaluate attack detection and user completion together. Ask for human-review options and clear failure reasons.

Source 2

Implementation

Integration checklist

Choose web or mobile capture and manage session state and webhooks.
Test capture retries, unsupported documents, accessibility, and fallback review.
Connect identity results to the owner and merchant record without losing provenance.

Commercial scope

Public plans may be available; verify current rates and minimums directly. Enterprise scope, KYB, screening, and intelligence can change the total.

Questions for the demo

Which checks use partners, and who is accountable for incorrect or stale data?
How are deepfake, replay, and injection attacks handled?
Which KYB fields and ownership links are supported in our countries?

Engineering

Decision webhookChecked 2026-09-18 Identity document coverageChecked 2026-09-18 Webhook delivery contractChecked 2026-09-18 Webhook authenticityChecked 2026-09-18

Your systemInputs & context

VeriffChecks & signals

Your controlsDecision & review

Illustrative integration boundary. Confirm the actual interfaces and decision authority.

Inputs: Schema not verified. Request required fields and validation rules.
Outputs: Decision, verified data and checks, session and attempt identifiers, and timestamps
Webhooks: Set a Webhook decisions URL in the customer portal. Decisions are delivered after processing; SDK resubmission requests have a documented five-minute delay. Veriff documents at-least-once delivery, possible out-of-order events, HTTP 200 acknowledgment within five seconds, and retries for up to one week.
Decision timing: Notification follows the decision. The five-minute SDK resubmission delay is not a general verification SLA.
Deployment: Deployment options not verified.
Dependencies: Country scope here refers only to identity-document verification; document classes and plan restrictions vary · Idempotent receiver and correlation by verification session, not only the customer-supplied user ID · Validate x-hmac-signature using HMAC-SHA256 over the raw request body and the shared secret

Verified details 11

Outputs
Decision, verified data and checks, session and attempt identifiers, and timestamps
Source Checked 2026-09-18
Webhooks
Set a Webhook decisions URL in the customer portal. Decisions are delivered after processing; SDK resubmission requests have a documented five-minute delay.
Source Checked 2026-09-18
Decision timing
Notification follows the decision. The five-minute SDK resubmission delay is not a general verification SLA.
Source Checked 2026-09-18
Country scope
Australia
Source Checked 2026-09-18
Country scope
Canada
Source Checked 2026-09-18
Country scope
United Kingdom
Source Checked 2026-09-18
Country scope
United States
Source Checked 2026-09-18
Dependency
Country scope here refers only to identity-document verification; document classes and plan restrictions vary
Source Checked 2026-09-18
Webhooks
Veriff documents at-least-once delivery, possible out-of-order events, HTTP 200 acknowledgment within five seconds, and retries for up to one week.
Source Checked 2026-09-18
Dependency
Idempotent receiver and correlation by verification session, not only the customer-supplied user ID
Source Checked 2026-09-18
Dependency
Validate x-hmac-signature using HMAC-SHA256 over the raw request body and the shared secret
Source Checked 2026-09-18

Illustrative contract

An example for your internal adapter. This is not a vendor endpoint, request, or response.

json

{
  "contract": "internal-risk-review/v1",
  "vendorId": "veriff",
  "internalCorrelationId": "example-001",
  "vendorRecordId": null,
  "control": "Identity proofing",
  "evidence": [],
  "status": "pending",
  "decision": "review",
  "requiresHumanReview": true
}

Integration limits

Illustrative internal integration contract. This is not a vendor request, response, endpoint, or SDK example.
Empty country, deployment, or provider lists mean not verified in this review. A documented country refers to the specific product noted in its source, not universal platform coverage.
A decision callback is distinct from a user's capture-complete event. The separate webhook delivery and signature guides are included in this profile.
These are named examples from the published support matrix, not an exhaustive country list. They do not describe residency, KYB coverage, or sanction-list scope.
Signature inputs for other API endpoints differ. Do not apply the webhook signing rule to every API request.

Sources 10

Identity verification productwww.veriff.com2026-09-18 · Reviewed

Product

Fraud Protect toolswww.veriff.com2026-09-18 · Reviewed

Product

Portfolio and partner scopewww.veriff.com2026-09-18 · Reviewed

Product

AML screening and monitoringwww.veriff.com2026-09-18 · Reviewed

Product

Identity document country coveragewww.veriff.com2026-09-18 · Reviewed

Product

Webhook delivery and acknowledgmentdevdocs.veriff.com2026-09-18 · Reviewed

Documentation

Webhook signature validationdevdocs.veriff.com2026-09-18 · Reviewed

Documentation

Zapier workflow connectiondevdocs.veriff.com2026-09-18 · Reviewed

Documentation

Metadata Database Verificationdevdocs.veriff.com2026-09-18 · Reviewed

Documentation

Test and live integration limitsdevdocs.veriff.com2026-09-18 · Reviewed

Documentation

Source review dates are shown above. Product claims come from public sources. Fit, limits, and evaluation questions are our analysis. This is not a hands-on performance test. Methodology · Changelog