Identity verification for gig and staffing platforms

What gig and staffing platforms ask of identity checks

A gig or staffing platform onboards people in waves: a seasonal cohort from an agency, a thousand couriers before a launch. The person who finishes the shift should be the person who was checked, and an account that is lent or sold to someone else defeats the point. Workers come with many kinds of documents, including residence permits and visas, and they join from phones.

• Invite a whole cohort at once, with a link that works on a phone.
• Accept the documents workers actually hold.
• Match the worker to the document and confirm a live person.
• Catch the same person registered twice, and workers who were removed and return.

The flow

1. Cohort invitation. A coordinator creates single-use links, from 1 to 1,000 at once, and sends them to the cohort.
2. Questionnaire. The worker enters name, birth date, contacts and the custom fields your agency needs before the KYC starts.
3. Document. The worker photographs a passport, national ID card, driver's licence, residence permit or visa. The document is read, with the MRZ read with checksum, and checked for fraud.
4. Selfie and active liveness. The selfie is matched to the document portrait, and the worker moves the face through two ovals.
5. Duplicates and removed workers. Repeat-user search looks for the same face among earlier verified users, and your own person lists and blocklists are checked in the same flow.
6. Review. Coordinators with the right role decide doubtful cases in the dashboard.
7. Result. Your scheduling system reads the session status or receives a webhook.

Modules used

• Document verification: passports, national ID cards, driver's licences, residence permits and visas.
• Face verification and liveness.
• One-time links and QR hand-off, described on the web SDK page.
• Repeat-user search and blocklists, described on the face verification page. A returning user is compared with a stored reference face.
• Dashboard with roles, session log, export and manual decision.
• Webhooks and the REST API.

Regulatory frame

Employment law differs by country, so this block shows one example from a primary text: the guidance that GOV.UK gives to employers in the United Kingdom on checking a job applicant's right to work.

• The guidance says that an employer must check that a job applicant is allowed to work in the UK before employing them.
• It lists three routes: an online check with the applicant's share code, a check of the applicant's original documents, or an identity service provider that offers Identity Document Validation Technology.
• It adds that British and Irish citizens cannot get an online share code, so the employer checks their original documents, for example a passport or passport card, or uses an identity service provider.
• The employer checks that the documents are genuine, original and unchanged and belong to the person who has given them, that photos are the same across all documents and look like the applicant, and that dates of birth are the same across all documents.
• For applicants who are not British or Irish citizens, the check also covers whether the dates of the right to work have expired and whether the applicant has permission to do the type of work offered.

An identity check is one part of that duty. This block describes the text, not our service. For information; not legal advice.

Sources

• GOV.UK, Checking a job applicant's right to work, guidance page, fetched 27 October 2026.

Next

Try the interactive tour, see the marketplace flow or read about one-time links.