Skip to main content

Product Guides

Choose the right verification product for your use case.

Individual Verification​

Client-Only Verification​

Use Case: Quick screening when consumer is not in the flow

Perform lite screening checks without consumer interaction. The client provides all subject data, and the check completes within seconds.

Key Features:

  • AML screening (sanctions/PEP)
  • Optional address verification
  • Optional CCJ/Insolvency check (UK)
  • Optional ongoing monitoring
  • No consumer interaction required

Best For:

  • Quick screening of clients or counterparties
  • Batch processing of existing client data
  • Situations where consumer cannot access mobile app

View Guide →

Identity Verification​

Use Case: Full identity verification with consumer in the flow

Comprehensive identity verification with document checks and liveness detection. The consumer completes verification tasks via the Thirdfort mobile app.

Key Features:

  • Document capture (passport, driving license, ID card)
  • Liveness detection (selfie video)
  • AML screening (sanctions/PEP)
  • Optional address verification
  • Optional CCJ/Insolvency check (UK)
  • Optional ongoing monitoring

Best For:

  • Full identity verification with document checks
  • Onboarding new clients
  • Regulatory compliance requiring document verification

View Guide →

(PREVIEW) Source of Funds​

Use Case: Verify source of funds for transactions

Verify where funds are coming from for a specific transaction. The consumer provides supporting documents via the Thirdfort mobile app.

Key Features:

  • Consumer uploads supporting documents
  • Document analysis and verification
  • AML screening (sanctions/PEP)
  • Optional ongoing monitoring

Best For:

  • Verifying source of funds for property transactions
  • AML compliance for large transactions
  • Standalone SOF verification without full identity check

View Guide →

(PREVIEW) Identity Document Verification​

Use Case: Verify documents provided by the client

Verify identity documents when the client has already collected them and needs verification without involving the consumer.

Key Features:

  • Client uploads document images via API
  • Document verification and analysis
  • AML screening (sanctions/PEP)
  • No consumer interaction required

Best For:

  • Verifying documents already collected by the client
  • Batch processing of existing document images
  • Integration with existing document collection systems

View Guide →

Business Verification​

(PREVIEW) KYB Verification (Know Your Business)​

Use Case: Verify businesses and companies

Verify companies and businesses for KYB compliance. Includes company registry checks, beneficial ownership verification, and AML screening.

Key Features:

  • Company registry verification
  • Beneficial ownership identification
  • AML screening of company and officers
  • Financial checks and credit reports
  • Adverse media screening

Best For:

  • Onboarding business clients
  • Verifying companies for B2B transactions
  • KYB compliance requirements
  • Due diligence on business entities

View Guide →

Comparison Table​

ProductConsumer InteractionDocumentsCompletion TimeSubject Type
Client-Only Verification (stable ✅)NoNoSecondsIndividual
Identity Verification (stable ✅)Yes (mobile app)Yes (consumer captures)5-15 minutesIndividual
Source of Funds (preview ⚠️)Yes (mobile app)Yes (consumer uploads)10-30 minutesIndividual
Identity Document Verification (preview ⚠️)NoYes (client uploads)Seconds-MinutesIndividual
KYB Verification (preview ⚠️)NoNoMinutes-HoursCompany

Getting Started​

  1. Choose your product based on your use case
  2. Review the product guide for detailed API documentation
  3. Test in nonproduction environment
  4. Contact support for production credentials and package configuration

Common Patterns​

All Products Support​

  • OAuth 2.0 authentication - Client credentials flow
  • Webhooks - Real-time notifications (contact support to enable)
  • PDF reports - Full and summary reports available
  • Findings - Detailed issue information when anomalies detected
  • Ongoing monitoring - Continuous sanctions monitoring (requires package support)

API Consistency​

All products follow the same API patterns:

  • CreateCheck: POST /v1/{parent}/checks (or POST /v1alpha2/{parent}/checks for preview types)
  • GetCheck: GET /v1/{check_name} (or GET /v1alpha2/{check_name} for preview types)
  • GetCheckSummary: GET /v1/{check_name}/checkSummary (or GET /v1alpha2/{check_name}/checkSummary for preview types)
  • ListFindings: GET /v1/{check_name}/findings (or GET /v1alpha2/{check_name}/findings for preview types)

Need Help?​