Masked passport ref
Sensitive document numbers stay minimized in previews.
Extract and review passport number, holder identity, DOB, nationality, issue/expiry, and MRZ-style document signals without implying immigration, visa, or criminal clearance.
Sensitive document numbers stay minimized in previews.
Expired documents are highlighted as risk signals.
Passport verification does not confirm visa or immigration status.
Choose Passport, state the reason for verification, and invite the subject or enter fixture data in sandbox.
The data principal sees the requester, purpose, and check type before any live verification starts.
PRAMAAN evaluates document signals and match evidence while keeping sensitive values minimized.
Teams receive a masked, timestamped result with consent reference, signals, and review guidance.
Passport verification supports high-assurance identity workflows but should not be confused with immigration or criminal clearance.
Extracts and masks the document reference in reports.
Compares identity fields with the submitted profile.
Surfaces nationality as visible on the document where extracted.
Flags expired, near-expiry, or inconsistent date signals.
Included only where supported by the workflow and document quality.
Unreadable MRZ, date mismatch, or suspected edits are routed to review.
A passport is a strong identity document, but verification does not prove travel permission, border clearance, or criminal-history status.
International onboarding
NRI/expat workflows
High-assurance identity checks
Support identity review for globally mobile employees.
Verify document signals for travel-support workflows.
Use passport evidence as part of identity review.
Combine with PAN, Aadhaar, or address checks where appropriate.
Support document organization without claiming clearance.
PRAMAAN should present passport document signals only and avoid claims about travel permissions, border clearance, or criminal history.
Every preview uses dummy sandbox data, a consent reference, a timestamp, document-specific signals, and bounded report language.
Sample sandbox report — no real PII
Sample sandbox report — no real PII. Passport verification does not confirm visa, immigration, or criminal status.
Expired documents should be flagged and reviewed.
Low-quality scans or MRZ issues reduce confidence.
Field mismatches should trigger manual review.
Use passport verification as an identity-document signal in high-assurance workflows.
Single live verification
₹99
Integrate passport document review into HR, vendor, and cross-border onboarding systems.
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.
High-trust hires — drivers, nannies, security staff, anyone with home-access.
Mid-to-senior hires, tutors, professional services contractors.
Fallback identity and address verification for workers, tenants, vendors, staffing candidates, and platform users.
No. Live checks require explicit consent from the data principal before processing begins.
Yes. The sandbox demo uses fixture data only and does not require real PII.
PRAMAAN surfaces the mismatch as a verification signal and recommends manual review where the evidence is incomplete, stale, or inconsistent.
No. Reports provide verification signals and consent evidence for reviewer decision support. They should not be treated as a guaranteed legal outcome.
No. It does not confirm visas, border decisions, or travel eligibility.
No. Passport verification is separate from PCC or background-document workflows.
Use sandbox fixture data first, then run a live ₹99 verification when the requester, purpose, and consent path are ready.