W-Basic launch-gated
Published entry path
Shown only where the public pricing source supports it.
For workers who want portable trust
Carry trust signals you control
PRAMAAN gives workers a portable badge they can share across employers, societies, platforms, and households while controlling what is shared.
Worker-ownedPortable statusQR shareW-Basic launch-gatedConsent-controlledNo job guarantee
Sample preview — no real PII
Worker-owned QR badge
Name
P*** N.
Masked public displayRole
Driver · Bengaluru
Worker-controlledVerification
Identity signal current
Expiry visibleShare controls
QR/link
Consent-controlledDummy badge. No raw Aadhaar/PAN/passport/police details are public.
R2
Rollout stage
Pilot, waitlist, and target capabilities stay labelled.
Consent
Processing posture
Manual review supported
Audience stakes
Workers should own their trust profile without being promised jobs, permanent validity, or public exposure of raw documents.
The redesign makes every page explain the buyer's operational world before asking for a conversion.
Workflow pressure
Workers users need verification that fits the way they already operate.
Consent pressure
The person being verified must see the purpose and consent before processing starts.
Evidence pressure
Teams need a readable signal and audit trail without exposing more PII than required.
Specialized module
Worker ownership model
Worker-owned portable badge for employers, societies, platforms, households, and customers.
Workers teams
Operations owners
Compliance reviewers
People being verified
Who this is for
Role-based trust, not one generic buyer.
Each stakeholder gets the decision surface they need while the person being verified keeps consent and rights visible.
Worker
Ownership, deletion, correction, and sharing control
PRAMAAN view: Badge controls, validity, QR sharing, DSR and correction.
Employer or society
Current status without raw document sprawl
PRAMAAN view: Permitted signals and expiry.
Customer
Confidence before home-service booking
PRAMAAN view: Masked badge status and validity.
Workflow
Request, consent, signal, review, and audit stay connected.
The person being verified sees the purpose before checks run; the operator receives a decision-support signal and escalation path.
- Request1
Choose the purpose
The workflow starts with an explicit purpose and requester role.
- Consent2
Subject consents or declines
The person sees the purpose, support route, and sharing boundary.
- Review3
Reviewer sees permitted signals
Operational views prefer verdicts and status over raw identity documents.
Capabilities
Built around the segment's daily operating model.
Capabilities are useful only when the live/planned/target boundary is visible.
Workers workflow
A verification path shaped around this audience, not a generic form.
Consent record
Purpose, requester, timestamp, and support path are part of the result.
Role-based views
Operators see the signal they need without default access to raw documents.
Exception queue
Incomplete, disputed, or adverse signals route to manual review.
Rollout clarity
Live, supported, planned, target, and by-agreement capabilities remain marked.
Responsible use
The page explains what PRAMAAN does not replace or guarantee.
Consent and DPDP
Consent and DPDP-native workflow
Each page keeps consent, purpose, minimization, DSR, support, and grievance paths visible.
Explicit consent before checks
Purpose shown before processing
Operational views prefer signals over raw documents
DSR, correction, support, and grievance routes visible
Sample preview
Worker-owned QR badge
Every preview uses dummy, masked data and is labelled so it cannot be confused with a real report.
Sample preview — no real PII
Worker-owned QR badge
Name
P*** N.
Masked public displayRole
Driver · Bengaluru
Worker-controlledVerification
Identity signal current
Expiry visibleShare controls
QR/link
Consent-controlledDummy badge. No raw Aadhaar/PAN/passport/police details are public.
Use cases
Specific workflows a buyer can recognize.
Primary workflow
Use PRAMAAN for the highest-frequency verification path.
Less document forwarding and clearer consent.
Exception review
Route amber, incomplete, or disputed signals to a human reviewer.
Better decisions without automatic rejection.
Renewal or expiry
Refresh signals when a badge, pass, or role context becomes stale.
No reliance on old screenshots.
Responsible use
Worker dignity guardrails
The badge belongs to the worker, not the employer, platform, society, or household.
No guaranteed jobs
No raw documents on public badge
Deletion/correction/DSR routes visible
No employer, platform, society, or household owns the badge
Worker badge pricing
W-Basic launch-gated
Worker Basic launch-gated. W-Pro adds email-confirmed employer references. W-Premium adds family-share up to 6 members.
- No permanent validity claim
- Renewal and expiry remain visible
- No guaranteed jobs, callbacks, or income outcomes
Worker-owned badge
R2
Worker badge copy preserves the W-Basic launch-gated path while avoiding job, income, permanent validity, app-roadmap, network-density, or outcome guarantees.
Integration and operations
Operational model
Use dashboard and web flows first; connect APIs or webhooks only where supported by current implementation and agreement.
Hosted flow
Supported
Dashboard view
Supported
API / webhooks
Planned
Manual review
Supported
Proof and pilot clarity
Proof and worker-outcome posture
Worker workflows are R2. Names, worker counts, ratings, callback outcomes, income outcomes, app availability, kiosk network coverage, and customer stories publish only after approval.
FAQ
Workers verification FAQ
Short, specific answers with consent, visibility, pricing, rollout, and limitation boundaries.
Related journeys
Move to the nearest workflow without losing context.
Build a portable trust profile you control
Create, verify, share, renew, correct, or request deletion for your worker-owned badge.