DPDP-native consent
Explicit consent before the EPIC rail runs.
Run a professional Voter ID / EPIC verification for workers, societies, staffing teams, platforms, and enterprises. Every live check starts with explicit consent and returns reviewable evidence.
Explicit consent before the EPIC rail runs.
Designed around source-backed Voter ID checks.
Built for clear operational onboarding queues.
Fixture data only; no real PII in demo mode.
Purpose, consent, timestamp, and result evidence.
Trust-first workflow for Indian verification needs.
PRAMAAN separates request, consent, verification, and result review so the workflow is easier for individuals and defensible for teams.
Start from a clear verification purpose, then enter the Voter ID reference or invite the person to complete the flow.
The data principal reviews the request and consents before PRAMAAN initiates the verification.
The rail evaluates EPIC validity, holder identity signals, constituency/state, and registered address signal.
The requester receives a reviewable report with status, evidence labels, timestamp, and consent reference.
Voter ID verification is strongest as a consented identity and address signal. Use it alone for low-risk checks, or combine it with other PRAMAAN rails when the workflow needs more depth.
Confirms whether the Voter ID / EPIC reference resolves as a valid verification signal.
Surfaces name and photo-match evidence for the submitted or consented profile context.
Returns the constituency and state signal associated with the EPIC record.
Provides the address signal available from the voter record for comparison with declared address.
Highlights stale, incomplete, or mismatched evidence as review required instead of overclaiming.
Links the verification result to the consent event, purpose, requester, and timestamp.
EPIC is especially useful when Aadhaar or PAN is unavailable, inappropriate for the workflow, or needs a supporting signal.
Useful when Aadhaar or PAN is unavailable and a consented fallback identity signal is needed.
Standardise onboarding evidence for recurring site access and vendor staffing.
Add EPIC as an alternate rail for distributed frontline onboarding workflows.
Move away from paper ID copies toward consented, logged verification requests.
Support candidates or workers who do not have the default document combination.
Evaluate sandbox and API flows before embedding consent-first checks into onboarding.
The Voter ID rail is designed around a simple rule: no check runs without explicit consent. PRAMAAN keeps the requester, purpose, consent event, and result evidence visible for serious verification decisions.
No check runs without explicit consent from the data principal.
The consent link states the requester, purpose, and document rail before verification.
Consent is logged with a timestamp and reference for audit review.
Sandbox demos use fixture records only and do not require real personal data.
The preview uses dummy fixture data only. Production reports should be read as verification evidence, not as a blanket legal or safety conclusion.
PRAMAAN sandbox report
Sandbox data notice
Masked EPIC, demo workspace, and fixture timestamps only.
A single live Voter ID / EPIC verification is INR 99. Teams can run a sandbox demo with fixture data before live usage.
Single Voter ID verification
₹99
Enterprise buyers can evaluate sandbox behaviour, API documentation, webhook patterns, and consent evidence before moving Voter ID checks into production workflows.
Use PRAMAAN API docs to evaluate consented verification creation and result retrieval.
ReviewTest without real PII, inspect structured responses, and prepare integration safely.
ReviewReview signed webhook patterns and delivery semantics for business integrations.
ReviewDesigned for purpose-led logs, consent evidence, and enterprise review workflows.
ReviewChoose the document mix that fits the purpose, risk level, and consented workflow.
Household help, driver, tutor — the default identity rail in India.
Tenant, vendor, employee — anyone receiving payment in India.
Drivers, delivery workers, fleet operators — DL is the implicit job-credential.
Most senior hires, mid-management vendors, NRIs returning.
Vendor onboarding, B2B contractor vetting, marketplace seller verification.
Large B2B contracts, marketplace KYB, investor diligence on prospective partners.
Clear answers for individuals, RWAs, employers, staffing teams, platforms, and compliance reviewers.
No. PRAMAAN requires explicit consent before a Voter ID / EPIC verification starts, and the consent event is logged.
The check can include EPIC validity, holder name/photo match, constituency/state, and the registered address signal returned for the record.
The full verification result is usually available under 2 minutes where the supported check can complete normally.
Yes. The sandbox demo uses fixture data only, so teams can evaluate the consent flow and report format without real PII.
Use Voter ID as a fallback or supporting identity and address signal when Aadhaar or PAN is unavailable, insufficient, or not the right proof for the workflow.
Yes. Employers, staffing teams, facilities teams, and platforms can use it as part of a consent-first onboarding workflow, especially for frontline or contractor populations.
PRAMAAN should surface the available signal and mark stale, incomplete, or mismatched evidence for review. A Voter ID result should not be treated as a guaranteed legal conclusion.
No. The sandbox demo uses fixture data only, so buyers and developers can evaluate consent, flow, and report shape without processing real personal data.
Yes. The Voter ID / EPIC verification does not run until the data principal gives explicit consent, and the consent event is logged.
Start with a single INR 99 verification, evaluate the sandbox, or speak with PRAMAAN about API and enterprise workflows.