The gig worker onboarding problem

Logistics platforms onboard hundreds or thousands of delivery partners every month. Each partner needs their driving licence, identity, and bank account verified before they can start earning. The old way — collecting photocopies at a hub, emailing them to an ops team, waiting 2–3 days — creates a bottleneck that loses partners to competitors who can onboard faster.

The new standard is sub-3-minute mobile verification. Partners tap through a flow on their phone and are cleared to start the same day. Here's how to build it.

The four checks you need

For a gig worker onboarding flow in India, you need four verifications:

  • Driving licence — vehicle class, validity, and licence number verified against the transport authority database or pulled via DigiLocker.
  • Aadhaar OTP — government identity confirmed. Name and address returned for cross-check.
  • PAN — active tax identity confirmed. Name matched against Aadhaar name automatically.
  • Bank account — payment account confirmed via penny drop before the first payout is made.

Why DigiLocker for the driving licence?

The traditional approach — asking the partner to photograph their physical licence — produces variable image quality, OCR errors, and requires manual review for 10–20% of submissions. DigiLocker eliminates this entirely. The partner authorizes a DigiLocker pull with one tap, and you receive a digitally signed XML containing the licence number, vehicle class, validity date, and holder name — directly from the transport authority database. No OCR, no manual review, no ambiguity.

Conversion note: DigiLocker pull has a ~87% first-attempt success rate. Partners who don't have DigiLocker set up (~13%) can be routed to a camera-capture fallback. Veriflow handles both paths with the same API call.

Building the mobile flow

The sequence that minimises drop-off:

  1. DPDP consent screen — explain what data is collected and why. One tap to accept. Logged with timestamp.
  2. DigiLocker driving licence — partner authorizes DigiLocker in their browser or mAadhaar app. Takes 30–60 seconds.
  3. Aadhaar OTP — partner enters Aadhaar number, receives OTP on registered mobile. 20–30 seconds.
  4. PAN entry — partner types their 10-character PAN. Verified in the background in under 600ms.
  5. Bank account — partner enters account number and IFSC. Penny drop runs in background. 1–3 seconds.
  6. Completion screen — all checks passed, partner is cleared. Total time: 2–3 minutes.

With Veriflow, steps 2–5 are triggered in a single API call. The modules run in parallel where possible, not in sequence — which is how you hit the sub-3-minute target even when individual steps take 1–2 seconds each.

Bulk onboarding for ops teams

For city launches or partner drives where you're onboarding 50–500 partners at an event, the individual mobile flow isn't practical. Veriflow supports bulk CSV upload — your ops team uploads a CSV with partner name, Aadhaar number, PAN, bank account and IFSC, and verification runs in batch. Results are returned to the same CSV with a pass/fail and match score per check. Partners who pass are auto-cleared; those who fail are flagged for manual review with the specific check that failed.

What to do with borderline matches

Name matching between Aadhaar, PAN and bank account is never 100% clean — spelling variations, initials vs full names, and translation differences are common. Veriflow returns a name_match confidence score (HIGH, MEDIUM, LOW) for each cross-check. Set your thresholds in the Veriflow dashboard — e.g. auto-clear on HIGH, send to ops review on MEDIUM, reject on LOW. Your ops team sees only the cases that genuinely need human judgment.