Trulioo
Global identity and business verification
Trulioo provides person and business verification with watchlist screening and workflow tooling. Business verification can connect registry information and ownership checks to KYC of beneficial owners. Country, source, and field-level availability are critical: global reach does not mean identical evidence everywhere.
Our assessment
Global verification and onboarding infrastructure; pair with operational monitoring and merchant risk policy.
Best fit and limitations
A useful candidate for multi-country onboarding where both persons and legal entities need verification. Ask for a country-by-country evidence map rather than a single global coverage number.
- Registry existence does not prove the applicant is authorized to act for a business.
- Ownership discovery depth and source freshness vary by jurisdiction.
- No reviewed evidence establishes transaction fraud, AML behavioral monitoring, or complete merchant underwriting.
Tools 6
Person MatchIdentity data matching+
- Verify person information using configured sources
- Combine person checks with watchlist screening
Business VerificationLegal entity evidence+
- Verify business name and registration details
- Country and package configuration control available checks
Ownership and UBO checksBusiness-to-person linkage+
- Connect business records to owners and controllers
- Run KYC checks on relevant individuals
Watchlist ScreeningCustomer screening+
- Person and business screening options
- Run with verification or as a separate check
Workflow Studio + Workflow APIVerification orchestration+
- Configure verification steps and combined checks
- Manage workflow sessions and retrieve results
UBO DiscoveryOwnership reconstruction+
- Request AI-assisted reconstruction through the existing KYB transaction
- Return source-cited owners and ownership relationships
- Require the UBO Discovery data group in the selected package
AI capabilities
Identity intelligence + AI-assisted ownership reconstruction
Trulioo combines identity checks with UBO Discovery, which uses governed sources and LLM-assisted relationship mapping to reconstruct ownership. Unresolved evidence remains a gap for review; the reviewed scope does not establish independent compliance clearance.
What to validate
Check citations, missing owners, and conflicting records before relying on a reconstructed chain. Confirm package enablement and country-specific sources.
Implementation
Integration checklist
- Use the API generation and authentication model agreed for the contract.
- Handle country-specific fields, data-source consent, async callbacks, and ambiguous matches.
- Test business-to-owner linking and preserve which source supported each field.
Commercial scope
Quote required. Separate person checks, business searches, source fees, ownership documents, watchlists, and workflow use.
Questions for the demo
- Which registries and ownership depths are available for our actual merchant countries?
- What evidence is returned when sources disagree?
- How do ongoing business changes reach our risk system?
Engineering
- Inputs
- PackageId, CountryCode, and BusinessDataFields · Data-source consent where required · BusinessName, CountryCode, PackageId, and UBODiscovery=true; registration number improves disambiguation
- Outputs
- Business verification response; optional detailed watchlist fields · CompanyOwnershipHierarchy within the UBO Discovery datasource result
- Webhooks
- Configured KYB monitoring callbacks deliver changes for enrolled businesses.
- Decision timing
- The API accepts a synchronous timeout. The documented behavior cancels the transaction if that timeout cannot be met.
- Deployment
- Deployment options not verified.
- Dependencies
- Configured verification package and an API-enabled account · Customer Success or support must enable the UBO Discovery datasource group
Verified details 9
- Inputs
PackageId, CountryCode, and BusinessDataFields
Source Checked 2026-09-18 - Inputs
Data-source consent where required
Source Checked 2026-09-18 - Outputs
Business verification response; optional detailed watchlist fields
Source Checked 2026-09-18 - Decision timing
The API accepts a synchronous timeout. The documented behavior cancels the transaction if that timeout cannot be met.
Source Checked 2026-09-18 - Dependency
Configured verification package and an API-enabled account
Source Checked 2026-09-18 - Webhooks
Configured KYB monitoring callbacks deliver changes for enrolled businesses.
Source Checked 2026-09-18 - Inputs
BusinessName, CountryCode, PackageId, and UBODiscovery=true; registration number improves disambiguation
Source Checked 2026-09-18 - Outputs
CompanyOwnershipHierarchy within the UBO Discovery datasource result
Source Checked 2026-09-18 - Dependency
Customer Success or support must enable the UBO Discovery datasource group
Source Checked 2026-09-18
Illustrative contract
An example for your internal adapter. This is not a vendor endpoint, request, or response.
{
"contract": "internal-risk-review/v1",
"vendorId": "trulioo",
"internalCorrelationId": "example-001",
"vendorRecordId": null,
"control": "Identity data matching",
"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 sample CountryCode is not proof of complete production country coverage. Confirm the package and available fields for each jurisdiction.
- The guide supports NAPI v1 and v3. Its GB example is not a complete country-availability contract.
Sources 6
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