CheckFile vs Onfido: complete comparison 2026
Detailed CheckFile vs Onfido comparison for the US โ FinCEN, BSA, OFAC compliance. Which document verification solution to choose in 2026?

Summarize this article with
US businesses operating under the Bank Secrecy Act (BSA), FinCEN reporting obligations, and OFAC sanctions requirements face a compliance landscape fundamentally different from the FCA-regulated environment where Onfido was built. Choosing between CheckFile and Onfido means understanding which platform was designed with your regulatory reality in mind โ and which one was retrofitted to it.
This article is for informational purposes only and does not constitute legal, financial, or regulatory advice. Regulatory references are accurate as of the publication date. Consult a qualified professional for guidance specific to your situation.
Comparison table: CheckFile vs Onfido
| Criterion | CheckFile | Onfido |
|---|---|---|
| Document types | 3,200+ (identity + commercial + HR + legal + financial) | 3,400+ (primarily identity, 195 countries) |
| Verification speed | 4.2 seconds average | 10โ15 seconds (document + biometrics) |
| OCR accuracy | 98.7% | ~97% |
| Fraud recall | 94.8% | Not published (Atlas AI) |
| False positive rate | 3.2% | Not published |
| Pricing | ~$0.13/document (public, pay-per-use) | ~$2โ4/verification (enterprise contract) |
| Biometrics | No (document verification only) | Yes โ facial comparison + liveness detection |
| Data hosting | France (EU sovereignty) | Multi-cloud, US options available |
| Compliance certifications | ISO 27001, SOC 2 | ISO 27001, SOC 2 Type II, FCA registered |
| API integration | 2โ5 days | 4โ12 weeks |
| SLA | 99.94% | Not publicly stated |
Onfido (Entrust): biometric-first identity verification
Onfido, acquired by Entrust in 2024, built its platform around a single core proposition: confirming that a person is who they claim to be. The platform combines government-issued document analysis with facial biometrics โ a selfie comparison against the document photo โ and liveness detection to rule out spoofing attacks. Its Atlas AI engine processes these signals to produce an identity verification decision.
With coverage across 3,400+ document types from 195 countries, Onfido is a strong choice for US companies onboarding international customers at scale, particularly through mobile-first consumer applications where its native iOS and Android SDKs provide guided capture and UX optimization. FCA registration and SOC 2 Type II certification underpin its compliance posture.
The trade-offs are real. Onfido's pricing operates on enterprise contracts at approximately $2โ4 per verification, with exact pricing available only on request. Integration timelines run 4โ12 weeks. Onfido's strength is identity confirmation, not case file analysis โ it does not natively handle W-2s, paystubs, Certificates of Good Standing, or the multi-document dossiers that BSA/AML compliance typically requires.
CheckFile: broad-spectrum document verification engine
CheckFile was built for a different question: "is this case file complete, authentic, and compliant?" Rather than confirming who someone is, CheckFile verifies the integrity and consistency of entire document sets โ identity documents alongside commercial records, financial statements, HR documents, and legal filings โ across 3,200+ document types.
Hosted in France under EU data sovereignty principles, CheckFile processes a document in 4.2 seconds on average, with 98.7% OCR accuracy across its full document range. At approximately $0.13 per document on a public pay-per-use pricing grid, the economics are transparent from day one. The API integrates in 2โ5 days. CheckFile does not offer biometric verification โ that function sits with dedicated biometric providers or can be layered separately.
For US businesses subject to BSA/AML obligations, the platform's audit trail, configurable rules engine, and ISO 27001 / SOC 2 certifications align directly with the traceability and due diligence documentation requirements expected by FinCEN.
Document and geographic coverage
CheckFile covers 3,200+ document types spanning identity (US passports, state driver's licenses and state IDs, Green Cards / Employment Authorization Documents), commercial records (Certificates of Good Standing, Articles of Incorporation, state business registrations), financial documents (bank statements, tax transcripts, W-2s, 1099s), and HR/legal documents. Form I-9 employment eligibility verification is supported โ critical for employers subject to USCIS requirements.
Onfido's coverage of 3,400+ document types runs deep on government-issued identity documents across 195 countries. For US-issued documents โ the US passport, all 50 state driver's licenses and state IDs, the Green Card, the EAD โ Onfido's recognition is strong. Commercial and financial documents are outside its native scope.
The structural difference: Onfido verifies identities; CheckFile verifies case files. For CIP (Customer Identification Program) compliance under 31 CFR ยง 1020.220, you need both โ and the two solutions are architecturally compatible.
Pricing: ~$0.13 per document versus opaque enterprise contracts
CheckFile's pricing grid is public. At approximately $0.13 per document (equivalent to โฌ0.12), volume discounts apply at scale. A business processing 5,000 case files per month, each requiring three documents, pays roughly $1,950/month. There are no setup fees or onboarding surcharges.
Onfido operates on enterprise contracts. Published benchmarks place per-verification costs at $2โ4 depending on features and volume. For the same 5,000 monthly case files โ one identity verification each โ the cost reaches $10,000โ$20,000. Commercial documents are not covered, requiring additional tooling.
For organizations processing high document volumes under tight compliance budgets, the unit cost differential is material. FinCEN Form 8300 cash transaction reporting, SAR filing workflows, and CTR documentation all generate document verification volume that compounds quickly.
Regulatory compliance in the US: FinCEN, BSA, and OFAC
US businesses face a compliance framework with no direct equivalent in other markets. Understanding where each platform helps โ and where the responsibility remains yours โ is essential.
Bank Secrecy Act (BSA / 31 USC ยง5311): The BSA requires financial institutions, money services businesses (MSBs), and many regulated entities to maintain AML programs, file Currency Transaction Reports (CTRs) for cash transactions exceeding $10,000, and submit Suspicious Activity Reports (SARs) for transactions above $5,000 where laundering is suspected. The Anti-Money Laundering Act of 2020 (AMLA 2020) significantly updated BSA requirements, including enhanced whistleblower protections and new priorities for FinCEN.
FinCEN CIP Rule (31 CFR ยง 1020.220): The Customer Identification Program rule requires covered financial institutions to collect and verify specific identifying information for individual customers โ name, date of birth, address, and an identifying number (SSN or equivalent). Document verification is a primary method of satisfying CIP requirements for US citizens and non-citizens alike.
OFAC sanctions screening: The Office of Foreign Assets Control administers US sanctions programs. Covered businesses must screen customers and transactions against OFAC's Specially Designated Nationals (SDN) list and other blocked-party lists. Document verification informs sanctions screening by confirming identity data that feeds into screening workflows.
Corporate Transparency Act (CTA): The CTA, effective January 2024, requires most US companies to report beneficial ownership information to FinCEN. Verifying the identity of beneficial owners โ through passports, state driver's licenses, or state IDs โ is a core CTA obligation. CheckFile's multi-document capabilities support this verification.
Privacy: no federal law, a growing state patchwork: Unlike the EU (GDPR) or Canada (PIPEDA), the US has no comprehensive federal privacy law. Instead, a patchwork of state laws applies: California CCPA/CPRA, Virginia VCDPA, Colorado CPA, Connecticut CTDPA, and others. CheckFile's EU hosting and configurable data deletion align with these frameworks, but US organizations must conduct their own state-by-state compliance analysis. Onfido's biometric data processing implicates additional state laws including Illinois BIPA and Texas CUBI.
State-level money transmitter licenses: MSBs operating across state lines must hold state money transmitter licenses โ a patchwork of 50+ state licensing regimes. Document verification supports the customer due diligence that licensing examinations routinely audit.
Technical integration: 2 days vs 4-12 weeks
CheckFile offers a documented REST API, webhooks for asynchronous processing, and native connectors for Salesforce and HubSpot. No proprietary SDK is required: any HTTP client calls the API directly. Integration typically takes 2โ5 days for a development team familiar with REST APIs. A free 48-hour pilot lets you test with your actual documents before any commitment.
Onfido's integration model centers on its mobile SDK (iOS and Android), which encapsulates document capture, selfie collection, and the verification flow into an embeddable component. For consumer-facing mobile applications, this is a genuine advantage โ guided capture, compression optimization, and UX flow come pre-built. The trade-off is integration complexity: 4โ12 weeks is the published range, and that estimate excludes compliance review of the SDK's biometric data flows under state biometric privacy laws.
For back-office workflows โ processing documents received by email, through a portal, or from internal systems โ CheckFile's API-first architecture is more direct. For consumer mobile onboarding where biometric selfie verification is mandatory, Onfido's SDK provides a materially better user experience.
Document fraud detection
CheckFile's fraud detection engine achieves 94.8% recall on document fraud โ meaning it correctly flags 94.8% of fraudulent documents โ with a 3.2% false positive rate. Detection covers document tampering (retouching, montage), data inconsistencies across documents within a case file, format anomalies, and metadata irregularities. These metrics are published and auditable.
Onfido's Atlas AI combines documentary and biometric fraud signals. Published metrics are not available. Onfido's particular strength is identity fraud โ detecting that someone is presenting another person's authentic documents with their own face, a fraud vector that biometric liveness detection catches and that document-only analysis cannot.
The two approaches are complementary. For US businesses concerned about synthetic identity fraud (a growing BSA/AML enforcement priority), layering both documentary and biometric checks provides the most complete coverage.
When to choose CheckFile
- Your compliance obligations under BSA/AML, CIP (31 CFR ยง 1020.220), or the Corporate Transparency Act require verifying multi-document case files โ not just a single identity document
- You process US driver's licenses, state IDs, US passports, Green Cards / EADs, SSN-related documents, Certificates of Good Standing, or Form I-9 packets in bulk
- Budget predictability matters โ you need transparent, per-document pricing without enterprise contract negotiations
- Your integration timeline is measured in days, not weeks or months
- You need a configurable rules engine to apply sector-specific or client-specific validation logic
- You are subject to OFAC screening obligations and need clean, structured identity data to feed into your screening workflow
When to choose Onfido
- Your primary requirement is biometric identity verification: confirming a person's identity via selfie-to-document facial comparison and liveness detection
- You operate a consumer-facing mobile application where Onfido's native iOS/Android SDK improves the onboarding UX
- You onboard customers from many countries and need deep recognition of international government-issued identity documents (195 countries)
- Budget per verification is not a primary constraint and you are comfortable with enterprise contract pricing
- Your compliance requirements are identity-centric and do not extend to commercial document verification
Verdict
CheckFile and Onfido address different segments of the document verification problem. Onfido asks "who is this person?" โ and answers it with biometrics. CheckFile asks "is this case file complete, authentic, and consistent?" โ and answers it with comprehensive documentary analysis.
For US businesses navigating BSA/FinCEN obligations, CIP requirements, OFAC screening workflows, and the beneficial ownership reporting demands of the Corporate Transparency Act, the compliance challenge extends well beyond a single identity check. CheckFile's multi-document coverage, transparent pricing, and rapid API integration make it the more practical fit for the documentary compliance workload that US regulations actually impose.
For organizations that need both โ biometric identity confirmation and multi-document case file analysis โ the two platforms are architecturally compatible. A common pattern uses Onfido for initial selfie verification and CheckFile for the complete case file: BSA-required supporting documents, beneficial ownership records, Certificates of Good Standing, and cross-validation across the full dossier.
See also: Document Verification Guide ยท Identity Verification Solutions Comparison
Frequently Asked Questions
Does CheckFile satisfy FinCEN and BSA document verification requirements?
CheckFile's verification outputs โ structured data extraction, fraud detection flags, and a complete audit trail โ support the recordkeeping and due diligence documentation that FinCEN expects under the BSA. The platform is ISO 27001 and SOC 2 certified, and its configurable rules engine can enforce CIP (31 CFR ยง 1020.220) and CDD (31 CFR ยง 1010.230) validation logic. CheckFile does not file CTRs or SARs on your behalf โ those reporting obligations remain with the covered financial institution.
Can CheckFile and Onfido be used together in the same workflow?
Yes. Both platforms expose REST APIs and are straightforward to combine. A typical architecture uses Onfido for biometric selfie verification (document + facial comparison + liveness), then CheckFile for the supporting case file: W-2s, paystubs, bank statements, Certificates of Good Standing, and cross-validation across all documents. The combination covers both identity fraud and documentary fraud in a single workflow.
How does CheckFile handle OFAC sanctions screening?
CheckFile verifies and extracts structured identity data from documents โ name, date of birth, document number, nationality โ that feeds directly into OFAC SDN list screening. CheckFile does not perform sanctions screening natively; the structured output integrates with dedicated OFAC screening tools or your existing compliance systems. This separation of concerns is intentional: document verification and sanctions screening are distinct compliance functions.
What US document types does CheckFile support?
CheckFile supports US passports, all 50-state driver's licenses and state IDs, Green Cards (Form I-551), Employment Authorization Documents (EAD / Form I-766), and SSN-related documents. On the commercial side, Certificates of Good Standing, Articles of Incorporation, state business registrations, and Form I-9 employment eligibility packets are covered. The full catalog of 3,200+ document types is available via the CheckFile API documentation.
CheckFile processes 3,200+ document types with 98.7% OCR accuracy and a 4.2-second average verification time. ISO 27001, SOC 2 certified. Public pay-per-use pricing from ~$0.13/document.
Stay informed
Get our compliance insights and practical guides delivered to your inbox.