Use case · Employee and contractor onboarding
Employee and contractor onboarding
Know whoyou are hiringbefore day one.
Remote hiring means the person on the video call, the person on the ID and the person who turns up to work may be three different people. Toden verifies the hire's ID and face from a link, collects the paperwork you have to keep, and screens them where the role calls for it.
The workflow
Identity, documents and screening for new hires, sent as a link from your hiring flow. This is a starting point: add, remove or reorder any step in the workflow builder.
Step 01
Document Intelligence
Passport, licence or national ID
Step 02
Passive Liveness
A selfie with no prompts
Step 03
Facial Match
Selfie against the document photo
Step 04
Supporting Documents ×2
Two documents read against the verified name
Step 05
Questionnaire
Your own questions, such as right to work
Step 06
AML Screening ×2
Sanctions and adverse media: 2 screens
Then your rules decide
A starting rule set
- The selfie does not match the documentDecline
- A document names someone elseReview
- A screening match is foundReview
- Identity verified and documents agreeApprove
Every rule is yours to change on a visual canvas, and each result records which rule decided it. Publishing a new version needs no release.
Try the workflow builderHow it works
Send a link with the offer
Create a session for the candidate from your HR system or the console. No app and no code on their side.
They verify and upload
A government ID, a live selfie, and the documents you ask for, such as a certificate, a guarantor form or a signature.
You get one result
Identity verified or not, each document read against the verified name, and a screening result if you asked for one.
What powers it
Name each document and the details to read from it. Each one is checked against the verified identity, so a certificate in another name is flagged.
Integrate
Mount the SDK with the workflow you published, or send a hosted link and write no code. The result arrives by signed webhook, and changing the workflow never needs a release.
import { TodenVerification } from "@todenhq/sdk-react"; export function Verify({ userId }) { return ( <TodenVerification apiKey="pk_test_..." workflowId="wf_AbC123dEf456" userId={userId} onSubmit={(s) => save(s.verificationId)} /> );}{ "event": "verification.completed", "data": { "verificationId": "ver_8fk2...", "status": "verified", "assuranceLevel": "gov_db", "idType": "bvn", "country": "NG", "dataMatch": true, "facialMatch": true, "facialConfidence": 91 }}Products involved
This solution combines products you can use on their own too.
Related use cases
Frequently asked
Yes. A requested document can be a signature drawn on the phone, kept on file as a specimen.
Employee and contractor onboarding,in one workflow.
The sandbox opens when you sign up. Usage-based pricing, no sales call.