TrustWix docs
Verify a person anywhere in the world, with composable checks you assemble into your own flow
TrustWix is identity verification delivered as an API and a set of hosted pages. You compose the checks you need, liveness, face match, document, age and AML, into a named flow, then run real people through it from your backend, a hosted link, or an embedded flow inside your own product. A full KYC onboarding is one preset. A liveness-only anti-cheat check is another. You decide.
Every verification produces one clear result: a verdict, a set of reason codes when something goes wrong, and a lifecycle status your systems can reconcile against. Results arrive by webhook so you never poll, and the sandbox lets you force any outcome before a single real face is involved.
Start here
Most teams move fastest in this order. The Quickstart gets you to your first verdict end to end. Authentication covers how secret keys work and where each one belongs. Flows is where you compose the exact checks your product needs into one named verification. Handling results shows you how to read the status, the verdict and the webhooks you act on.
Quickstart
From a test key to a verdict, end to end
Authentication
Secret keys, environments and client tokens
Flows
Compose the checks your product needs
Handling results
Statuses, verdicts and webhooks
How it fits together
You create a flow once. For each user, your backend creates a verification against that flow. The user completes the steps through a hosted link or an embedded flow. We run the checks, roll them up into a single verdict, and deliver it to your webhook endpoint. You reconcile by the verification id you stored.
Two ways to integrate
The hosted flow is the fastest path. Create a verification, send the user to the returned link, and handle the webhook. There is no front-end code to write. The embedded path puts the same flow inside your own product using the short-lived client token returned on create, and it supports full white-label, your domain and your styling, in every language including right-to-left.
Built for testing
Test and live are separate worlds, selected by the key you authenticate with rather than by a different host or a header. In the sandbox you force any outcome with a magic applicant value, so you can build and ship your result handling long before you go live.