Fits the stack you already run.
Verification should slot into your existing onboarding, not replace it. Every path below returns the same signed result.
Six ways in. One result shape.
Pick the path that matches your product and your timeline. You can start hosted and move to the API later without re-verifying anyone.
Hosted verification
Redirect to a TrueID-hosted flow and receive the result on return. The fastest path to live.
QR handoff
For in-branch and point-of-sale: the customer scans, approves in their wallet, and your terminal gets the result.
Webhooks
React to revocation, re-verification, and status changes without polling.
USSD gateway
Route feature-phone customers through the same verification your app uses.
Batch re-verification
Re-confirm an existing customer book against current credential status.
Server libraries for the stacks you already use.
Server SDKs are released alongside the public API. Until then, the REST endpoints are stable and documented.
Tell us what you are building.
We will tell you which integration path fits — and honestly, whether we are ready for your use case yet.