Masked PAN
Full PAN is not shown in sample reports.
Financial identity signalConsent requiredSandbox fixture data
Verify PAN identity signals without exposing sensitive financial identifiers.
Use PAN verification for employee, vendor, contractor, KYC, and payroll workflows with masked reporting and consent-first handling.
- Live check
- ₹99
- PAN display
- Masked
- Use case
- KYC / payroll
- Sandbox
- Fixture only
Name match support
Reviewer sees match and mismatch signals.
No credit claims
PAN verification is not a borrowing or repayment assessment.
How verification works
A consent-first path from request to reviewable result.
1
Create a purpose-led request
Choose PAN, state the reason for verification, and invite the subject or enter fixture data in sandbox.
2
Capture explicit consent
The data principal sees the requester, purpose, and check type before any live verification starts.
3
Run the verification rail
PRAMAAN evaluates document signals and match evidence while keeping sensitive values minimized.
4
Review the report
Teams receive a masked, timestamped result with consent reference, signals, and review guidance.
What PRAMAAN checks
PAN signals built for reviewer decision support.
PAN is sensitive financial identity data. PRAMAAN frames it as a verification signal, not a financial-health score.
PAN format signal
Checks whether the submitted value follows the expected PAN format.
Name match signal
Surfaces whether the name aligns with the configured verification source.
Entity-type distinction
Can help distinguish individual and business PAN contexts where supported.
DOB / incorporation date signal
Included only where your configured workflow supports it.
Masked report output
Displays PAN as a masked reference such as ABC**1234* style redaction.
Mismatch review
Invalid format, name mismatch, or entity mismatch are flagged for review.
Why this document matters
Why PAN matters in onboarding
PAN is often used wherever a person or business receives payment, but it should not be treated as proof of financial reliability.
Payroll and contractor onboarding
Vendor identity checks
KYC workflow support
Use cases
Designed for individuals, operations teams, and enterprise reviewers.
Employee onboarding
Validate financial identity signals before payroll setup.
Vendor onboarding
Compare vendor PAN details with business records.
Contractor verification
Reduce manual back-and-forth on tax identity evidence.
KYC workflows
Use as one signal in a broader consented verification stack.
Consent and DPDP guardrails
Sensitive PAN handling
PRAMAAN keeps PAN reporting bounded to verification signals and avoids claims about borrowing profile or repayment ability.
Explicit consent required
Masked PAN display
No borrowing-profile claim
Mismatch goes to review
Sample report preview
Masked, specific, and designed for human review.
Every preview uses dummy sandbox data, a consent reference, a timestamp, document-specific signals, and bounded report language.
Sample sandbox report — no real PII
PAN identity signal
- Document reference
- ABCDE****F
- Consent reference
- CNS-PAN-DEMO-2048
- Timestamp
- 24 May 2026, 10:46 IST
PAN formatValid pattern
Name matchMatched
Entity typeIndividual signal
Risk noteManual review on mismatch
Sample sandbox report — no real PII. PAN is masked and does not indicate borrowing profile.
Risk and limitation signals
Clear flags for what needs review.
Invalid PAN
Format or source mismatch should block automation until reviewed.
Name mismatch
Spelling, legal name, and entity-name differences need reviewer context.
Entity mismatch
Individual vs company PAN confusion is a common onboarding risk.
Pricing and CTA
Run one consented PAN verification.
Start with a single live check or use sandbox fixture data before wiring PAN into onboarding.
Single live verification
₹99
- Masked PAN report
- Name match signal
- Consent reference
- Manual review note
Enterprise and API
PAN checks for KYC, payroll, and vendor systems
Integrate PAN signals into HRIS, payroll, vendor management, or platform onboarding through hosted flows or APIs.
API-ready result shape
Webhook-friendly events
Audit trail export
Role-based review workflows
Related verification documents
Explore all checksCombine this check with the right adjacent signals.
Aadhaar
Household help, driver, tutor — the default identity rail in India.
GSTIN
Vendor onboarding, B2B contractor vetting, marketplace seller verification.
CIN
Large B2B contracts, marketplace KYB, investor diligence on prospective partners.
Driving Licence
Drivers, delivery workers, fleet operators — DL is the implicit job-credential.
Passport
Most senior hires, mid-management vendors, NRIs returning.
Degree Certificate
Mid-to-senior hires, tutors, professional services contractors.
FAQ
PAN verification questions.
Can PRAMAAN run a PAN check without consent?
No. Live checks require explicit consent from the data principal before processing begins.
Can I test this without real personal data?
Yes. The sandbox demo uses fixture data only and does not require real PII.
What happens on a mismatch?
PRAMAAN surfaces the mismatch as a verification signal and recommends manual review where the evidence is incomplete, stale, or inconsistent.
Is the report a legal conclusion?
No. Reports provide verification signals and consent evidence for reviewer decision support. They should not be treated as a guaranteed legal outcome.
Does PAN verification prove financial health?
No. It provides identity and tax identifier signals only.
Will the sample report show the full PAN?
No. PAN is masked in previews and should remain minimized in reviewer surfaces.
Consent-first verification
Start a PAN verification with PRAMAAN.
Use sandbox fixture data first, then run a live ₹99 verification when the requester, purpose, and consent path are ready.